Where's the Goal Tracker?

Redesigning Goal Tracker for Budget Master

Role

UX Researcher (Team of 3)

Skills

Persona Development, Usability Testing, Think-Aloud Protocol, Wireframing

Timeline

3 Weeks, Research — Wireframe Delivery

Scope

Simulated client engagement (bootcamp project)

Overview

Budget Master is a personal finance app with a newly launched "Goal Tracker" feature that lets users set savings goals, track debt payoff, and monitor progress over time. But early user feedback and app analytics told a troubling story: users found Goal Tracker confusing and hard to use, leading to low engagement and abandoned goals. Through persona-driven usability testing with 40 participants across four user segments, I identified 7 critical usability issues — including a Goal Tracker that users couldn't even find — and delivered redesigned wireframes that simplified goal setup, improved discoverability, and introduced a shared goal feature.

Who Are We Designing For?

Before designing the usability test, we needed to understand who was using Goal Tracker and why. We analyzed existing user data and identified four distinct personas:

32%

Short-Term Saver

Achievement-oriented users under 35 saving for events like weddings. Struggle with milestone-based expenses that require money at different points.

36%

Debt Payer

College students or recent graduates paying off credit cards or student loans. Disengage when the tracker doesn't match reality.

14%

Emergency Fund Builder

Dual-income couples where one partner manages the tracking. Disengage when tracking requires constant manual effort.

8%

Retirement Saver

Mid-career professionals juggling tuition, mortgage, and retirement savings simultaneously.

Testing With Real Tasks, Real Frustration

40 participants completed 8 core tasks using a think-aloud protocol via Discuss.io. Each session followed a 4-phase structure:

1~5 min

Pre-Test Interview

Explored participants' prior experience with Goal Tracker and expectations.

2~30 min

Task Scenarios

8 tasks with think-aloud protocol, each rated on a 1–7 ease scale.

3~5 min

Post-Test Survey

Five Likert-scale questions covering usage frequency, ease, and NPS.

4~10 min

Post-Test Interview

Open-ended debrief exploring confusion points and unmet expectations.

Recruitment Strategy

We designed a stratified recruitment plan: drew a random sample of ~5,000 active users weighted toward savings/debt feature users, deployed a 2-minute in-app screener survey, placed respondents into persona-based quota slots with secondary controls for age and gender, and scheduled 45–60 minute remote sessions with $100 gift card incentive. We built in bias mitigations: independent quotas per group, exclusion of recent bug reporters, database-only recruitment, and a phone-call option for 56+ age band.

3.8/7

Overall ease-of-use

2.0/7

Lowest: Shared Goal setup

5.7/7

Highest: Pause/Stop

4.7

NPS average

Critical Product Question

Why can't users find, create, or edit a simple savings goal?

Key Findings

High Priority

P1

Goal Tracker is not discoverable

Buried at the bottom of the home screen, below the fold. Multiple participants mistook it for a promotional banner. Recommendation: promote to a dedicated navigation tab.

P2

Goal setup requires too many prerequisites

Users had to link a bank sub-account and assign a budget category before entering any amount. The confirm button was greyed out with no explanation. Recommendation: let users enter goal amount and target date immediately.

P3

"Target Amount" was consistently misread

Users read it as a monthly contribution target rather than the total goal. One participant set $500 instead of $18,000. Recommendation: rename to "Total Goal Amount" with microcopy.

P4

Goal editing was hidden

No visible Edit button on the goal detail page. Only accessible via a long-press gesture no participant discovered. Recommendation: add a visible "Edit Goal" button.

Lower Priority

P5

No direct path to log a contribution

General Income, Expense, and Transfer options did not update Goal Tracker. Recommended: add a prominent "Log Contribution" button inside the goal detail screen.

P6

Debt payoff goals visualized like savings goals

Progress bar moved backward after a loan statement auto-synced, causing confusion. Recommended: distinct "shrinking balance" visualization for debt goals.

P7

Shared goals required partner to independently change settings

Contributions couldn't be tracked until partner manually updated their own settings. Recommended: guided invite flow with a direct consent screen.

Design Shift — Redesigned Wireframes

1

Standalone navigation tab

Goal Tracker elevated to its own dedicated tab at the same level as Transactions and Budgets.

2

Streamlined "Add Goal" workflow

Enter amount and date first, everything else optional. Reduced from 5+ steps to 2.

3

Descriptive subtext

Microcopy explaining what each field means, preventing the "Target Amount" misread.

4

Visible "Edit Goal" button

Prominent edit action on the goal detail screen, no hidden gestures.

5

In-context "Log Contribution" flow

Direct contribution logging from within the goal, no detour through general transactions.

6

Guided goal sharing

Invite flow with direct consent screen, eliminating the need for partners to independently configure settings.

Outcome

Before

2.0/7

Shared Goal ease

3.8/7

Overall ease

Hidden

Goal Tracker discoverability

5+ steps

To create a goal

After

Standalone tab

Always visible in navigation

2 steps

To create a goal

Visible edit

Prominent button on detail page

Guided sharing

One-tap invite flow

Reflection

The most valuable lesson from this project was about the relationship between personas and test design. By building personas before the usability test — rather than treating them as an afterthought — we could design tasks that mirrored each user group's actual goals. This meant our findings weren't just "users had trouble with X" but "users saving for weddings had trouble with X because of Y, while debt payers had trouble with Z for a completely different reason." The challenge of recruiting low-frequency user segments (retirement savers at just 8%) taught me that sampling plans need to account not just for statistical representation, but for the practical difficulty of reaching underrepresented groups.