← Back to projects

HabitHero: personalising goals to make progress understandable

A research-led redesign of onboarding, daily guidance and weekly review.

Individual academic project · UX researcher and designer · October 2025–April 2026

I owned discovery, journey design, prototyping and usability testing. Delivered: a refined Figma prototype; longer-term habit formation remains unproven.

Final HabitHero dashboard showing daily status and remaining steps.
Delivered prototype · daily guidance

Discover

I investigated what people needed from fitness tracking.

The brief asked for better progress tracking. I interviewed people about how they tracked activity and what helped or discouraged them.

Original HabitHero Activity insight screen with four equally weighted rings for steps, distance, heart rate and calories.
Original experience

Which metrics matter?

When have I done enough?

Questions guiding discovery
See the original brief and discovery approach

Starting point

Help people track activity and understand their progress towards a goal.

I conducted five discovery interviews, then synthesised the findings into a persona, journey and design priorities.

Interviews showed that tracking could add pressure.

People described arbitrary targets, limited time and the pressure of tracking more information.

What the research changed

I concluded that progress feedback should explain what to do without adding pressure. I focused on helping people choose a realistic starting goal, understand daily progress and restart after missed days.

Research persona · synthesised from discovery

Ella, the time-poor parent

Original discovery drawing: Ella considering information on her phone and laptop. Original discovery drawing: Ella planning with her phone. Original discovery drawing: Ella stretching beside her laptop.

Making sense of conflicting information.

Key pain
Conflicting advice makes it hard to know what matters.
Key motivation
Clear guidance she can trust.
Read the interview quotes and synthesis

Pressure

“I'm not ready to track my sleep yet. It's another thing to get stressed about.”
Eleni · discovery interview

Arbitrary targets

“At the moment, 10,000 steps a day is just some arbitrary number, but I still kind of go with that.”
Alicia · discovery interview

Limited time

“I don't have five minutes to spare for anything. So my fitness mainly happens on weekdays when I'm at work.”
Gareth · discovery interview

Excerpts from discovery interviews, reproduced in the discovery presentation script.

Pull right or tap to reveal.

5 of 5 interviews
Decision cost and prioritisation; confusion about progression.
4 of 5 interviews
Fragile motivation.
3 of 5 interviews
Uncertainty about when an activity or goal was complete.

Define

I made goal setting the starting point for understanding progress.

A goal based on recent activity would give people a starting point for judging their progress. I used this as the reference point for daily status and weekly review.

Patterns across five discovery interviews

Design priority

Make the next action understandable.

Counts describe these five interviews, not the wider population.

See the assessment and planned measures

From findings to priorities

I used the persona and journey to bring the interview findings together, then compared opportunities by their expected impact and effort.

Scope boundaries

Cross-app aggregation was deprioritised. Redesigning the rewards system sat outside this scope, although testing later exposed its limitations.

Follow a finding into the brief

Research finding

Decision cost and prioritisation appeared across five discovery interviews.

Design priority

Reduce cognitive load: make the next action understandable.

These priorities reflect my interpretation of the research. Their effect on behaviour was not measured.

How I compared opportunities

The assessment favoured showing when a day was complete and what to do next.

Selected rows from the original assessment. Scores are design estimates on a 1–5 scale.
Opportunity Impact Effort
Clear daily completion state 5 2
One suggested next action 5 3
Restart flow with a small goal 4 2
Default starter-goal bundle 4 3

Opportunity names are shortened for readability. Ratings reproduce the original document; they are not measured product outcomes.

View the original assessment

What success would mean

Measure whether people accept the starter goal and complete setup, interpret their status correctly, and understand the weekly outcome. Longer-term evaluation would examine continued activity after goal adjustment.

Planned measures from the project’s goals–signals–metrics work, not achieved results.

What the design needed to do

  • Make the next action understandable.
  • Make completion clear.
  • Support restarting without shame.

Develop

I designed onboarding around a personalised, adjustable goal.

I compared three ways to accept or change a suggested goal, then explained the recommendation during onboarding.

First goal wireframe, with separate acceptance and manual creation routes.
A · Accept or create

A clear choice: accept the suggestion or start a manual goal.

The trade-off
Changing the recommendation means leaving this route.

Second goal wireframe, with adjustment alongside the recommendation.
B · Adjust in placeCarried forward

The explanation, goal and adjustment sit together.

The trade-off
The stepper must make the size of each change clear.

Third goal wireframe, with easier, same and harder options.
C · Relative adjustment

Everyday labels offer a direction without asking for a number first.

The trade-off
The result of each choice still needs explaining.

I carried forward adjustment in place to keep the explanation, suggested goal and controls together. Onboarding explained how recent activity informed the goal before people accepted or changed it.

Original low-fidelity explorations. Captions explain the visible trade-offs retrospectively; no comparative test result is claimed.

Explore the goal-setting screensClose the goal-setting screens
  1. Recent activity
  2. Suggested goal
  3. Your adjustment

How could people change the recommendation?

Three explorations

Turn to compare, or choose a name.

Explored: separate routes

Accept or create

Original low-fidelity Goal 1: recommended goal, information control, separate acceptance and manual creation buttons.
Acceptance and manual creation are separate.

The difference
A clear choice: accept the suggestion or start a manual goal.

The trade-off
Changing the recommendation means leaving this route.

View original in Figma
Carried forward: a suggested goal people can adjust

Adjust in place

Original low-fidelity Goal 2: goal explanation, optional more information, horizontal stepper, acceptance and manual creation.
Adjustment becomes part of reviewing the goal.

The difference
The explanation, goal and adjustment sit together.

The trade-off
The stepper must make the size of each change clear.

View original in Figma
Explored: relative adjustment

Easier / same / harder

Original low-fidelity Goal 3: goal explanation, context label and easier, same and harder choices.
Relative choices offer another way to adjust.

The difference
Everyday labels offer a direction without asking for a number first.

The trade-off
The result of each choice still needs explaining.

View original in Figma

The goal-setting design

Final personalised-goal screen with a recent-activity explanation, adjustment dial and acceptance controls.
Recommend a starting goal, with adjustment and a separate manual route.
Why this goal screen explaining the seven-day activity basis and how the goal adapts.
Make the basis of the recommendation available when people need it.

Final prototype screens.

I designed daily guidance and explained how weekly goals worked.

The dashboard shows daily status and remaining steps. The weekly review explains how active days count towards the goal.

Final daily dashboard, showing On track and remaining steps.
Final daily dashboard

A clear daily status.

Remaining effort made visible.

See the daily and weekly screens
Final daily dashboard showing On track, 2,502 of 5,000 steps and remaining steps.
Lead with daily status and remaining effort.
Final weekly explanation: five successful days need not be consecutive.
Explain weekly success without requiring consecutive days.
Explore the final screens in Figma

I tested whether people understood the goals, feedback and controls.

Seven people tested goal setup, daily status, weekly rules and goal adjustment in moderated sessions.

Five of seven sessions exposed confusion about how daily status was calculated. Four highlighted insufficient notification control.

Tested weekly screen with wording about five days and a streak.
Mid-fidelity version tested
6 of 7

found the weekly criteria unclear.

Illustration of the issue found in testing.

Tested weekly screen using the phrase string together five days and streak.
Tested wording · “streak” suggested consecutive days.

6 of 7 found the weekly criteria unclear.

The weekly rule allowed two missed days. The word “streak” suggested otherwise.

The response
State the five-day rule directly and explain that the days need not be consecutive.

The revision is documented. Improved comprehension after this change has not been established.

Revised weekly screen explaining that five active days do not need to be in a row.
Revised wording · comprehension still needs retesting.
Read participants’ responses to the prototype

What people found useful

Goals that adapt to recent activity received positive responses in six of seven sessions. Notifications and quick check-ins were useful for recovery across all seven.

Outcome

I clarified the wording and controls, then delivered the final prototype.

I explained active times during onboarding, added notification controls and documented the final screens for handover.

Delivered personalised-goal screen.
Set a starting goal
Delivered daily dashboard.
Understand today
Delivered weekly progress screen.
Review the week

Delivered Figma prototype · behavioural impact not yet validated.

Still unresolved

I tested comprehension and reactions to a prototype. These sessions did not establish improved retention or lasting exercise habits.

Permissions remained outstanding. Suitability of the adaptive goal logic still needs specialist validation. Retesting of the revised prototype has not been established. The next validation would check comprehension of the revised rules and controls before investigating longer-term behaviour.

Compare the documented revisions

Five active days, without a streak.

Tested version: string together five days and you are on a streak. Wording revised: five days this week; they do not need to be in a row. Final design: reach your personal goal on five days this week; they need not be consecutive.
Mid-fidelity screen recorded in the refinement page.

Tested version

“String together 5 days this week and you’re on a streak” mixed a consecutive-day term with a rule that allowed missed days.

Testing finding

Five of seven sessions revealed confusion about how daily status was calculated.

Design revision

Added explanations of active times during onboarding and routes to review those times.

The refinement record also documents larger radio-button hit areas, clearer goal-setting labels and more consistent primary buttons.

View the documented refinements