UX Designer

The Family History Guide

Defining the right problem to solve while working with many constraints. #KISSbeliever

“keep it simple stupid”

Project - The Family History Guide, Phase 1

Location: Mostly Remote

Volunteer UX Research & Design

My Role: UX Research + Design Specialist

Client: Family History Guide thefhguide.com

Main Contacts: Bob Taylor & Bob Ives

Timeframe: 3 weeks in July 2018

Quick Summary

The Family History Guide’s mission is to make family history easier, more efficient, and more enjoyable. I used this business statement as a backbone piece to guide my research and communicate with my stakeholders.

For this first project our goal was to find the part of the site to work on that would provide the most impact to the entire site. From there I would analyze the biggest UX pain points, access and conclude with possible solutions.

In the middle of this project I had a lot of fun thinking futuristically with a comparative analysis and designing for the future, but when it came right down to it I had to narrow my focus. I needed to find the most realistic solution that would be the easiest for the team to accomplish, that would make the biggest difference for their current struggles.

High-Level Findings & First Step Solution

After looking at the data I discovered the first key problem - over 60% bounce rate starting at the homepage.

The good news - a lot of people were finding the site.

The bad news - they were VERY often leaving before even looking into it which tells us the users weren’t finding what they needed on the home page the most important entry point of the site.

After more analysis, user interviews and usability testing, I highly recommended the team use the “Get Started Page” and turn it into the homepage entirely. This would be exactly what we wanted - a first step easy solution that would take the least amount of effort, and have the biggest effect.

Phase 1 - Quick Solution Recommendation

1. It is simpler and easier to navigate.

2. It gets down to the bottom of “what they are coming to do” from what we currently understand.

3. This can be a first step. We can watch and observe user behavior and alter the page according to their needs based on the observations.