tile-matches.jpg

Family Finder Matches

Family Finder Matches

 
 

Overview

Family Finder Matches is a web-based app that allows users to identify potential genetic matches for genealogical research. With a rapidly increasing database of over 2 million users, the app is an invaluable tool for discovering unknown biological relatives and confirming suspected relationships.

The Problem

The layout and design of the app are outdated, and there is limited functionality and a lack of system feedback, which makes it difficult for users to navigate and find the information they need.

 

THE TEAM
Chris P - Product Manager
Meagan P - Product Owner
Doug K - Engineering Lead
James G - Engineer
Buddy T - Engineer Back End
Jon M - Quality Assurance Lead (QA)

MY ROLE
Lead Designer, Research, User Interface, User Experience, User Testing, and Front-End Support

TOOLS USED
Google Forms, Jira, Adobe XD, GitHub, Zoho Surveys.

 
 

🕵️‍♂️ Research


UX audit

To gain a comprehensive understanding of the current user experience, I performed an audit that involved analyzing various aspects such as hierarchies, accessibility, functionality, and system feedback. In addition, I utilized heatmap analysis to delve deeper into how users were interacting with the application.

 
 
 

Stakeholder interviews

I conducted 10+ stakeholder interviews. Additionally, I reviewed hundreds of comments from HelpSpot, an internal tool primarily used by the Customer Service Team, and the International Society of Genetic Genealogy (ISOGG)

 
 
 
 
 

Competitive analysis

I decided to research the functionality and benefits provided by other matching apps that offer similar features. By comparing important features, I identified areas where the Family Finder Matches experience could be enhanced.

I found that the leaders in the genetic genealogy industry are ahead of the game in terms of presenting information in a way that is easy to understand, excelling in usability, and making the experience user-friendly across platforms.

 
 
 

🖼️ Conceptualization


Based on the research, I found that current users are familiar with the existing experience and have developed certain habits and preferences around it. we decided to keep the most utilized features, including the structure, and focus on adding new functionalities.

 
 
 

⚙️ Usability Testing


Feedback & Iteration

Two types of testing were performed - a prototype test with 15 users and a beta test with 50 users.

The prototype test was conducted with a smaller group to evaluate the initial design, while the beta test was performed with a larger group to assess the overall functionality and user experience of the product before its release.

Feedback

  • Include labels to Detailed and Table view toggle.

  • Onboarding tutorial highlighting main CTA’s.

  • Provide resources to support ongoing learning.

  • Include tooltips to provide additional information.

  • Introduce new features and make hidden options obvious that they exist.

  • Inform when data is not available.

 
 
 

🎯 Results


 
 
 

Onboarding

The onboarding tutorial highlights key areas to improve user engagement, product adoption, and retention while reducing frustration and support costs.

 
 
 
 

Advanced filters

Users can narrow down results based on specific criteria, such as top surnames, family tree types, match date, and tests taken.

 
 
 

General filters

Users now can easily and quickly filter content by relationship range, search using different criteria, and sort information, reducing the time and effort required to search through large amounts of data.

 
 
 

Help (resources) panel

Users can now quickly access resources to learn more about DNA topics, quickly access the Help Center, and send feedback.

 
 
 
 

First time loading

Skeleton screens give users the impression that the app is loading faster by providing a visual indication that content is on the way. This can help reduce frustration and improve overall satisfaction with the product.

 
 
 
 

🗒️ Conclusion


Although the release brought several complaints, mainly due to loading and timeout issues that were solved after a couple of months, I found this project challenging because it demanded time and project management skills, as well as the ability to adapt to new requirements and feature scopes. Additionally, it provided an exciting opportunity to explore new product features, components, and layout designs.