CASE STUDY · H365 SUITE

H365 Suite

I worked on several research tracks across HPB's H365 suite. Here are my two most recent: Special Challenges and Badges.

Pick a track to read its case study

TRACK 01 · SPECIAL CHALLENGES

More Than Just a Goal

Understanding what makes physical activity challenges feel achievable, meaningful and worth participating in.

Two iPhones showing the Healthy 365 My Progress screen with daily and weekly challenges and the Programmes list, beside the Healthy 365 and Health Promotion Board logos

CLIENT

Health Promotion Board (HPB)

PROJECT

Healthy 365 Special Challenges

MY ROLE

UX Researcher (Supporting Role)

TIMELINE

2026

METHODS

Two rounds of moderated usability testing

The challenge

How do you motivate someone to be more active without making the goal feel overwhelming?

Healthy 365 is a health and wellness app developed by Singapore's Health Promotion Board (HPB), encouraging healthier lifestyles through activity tracking, challenges and rewards. The Special Challenges initiative explored how personalised activity goals could motivate users with lower recorded physical activity levels to become more active.

But setting a goal doesn't necessarily mean someone will feel motivated to achieve it. Our research focused on understanding whether users could discover, comprehend and feel confident participating in these challenges.

THE QUESTION WE HAD TO ANSWER

What makes a challenge feel achievable rather than another target someone might struggle to meet?

What I did

01

Research planning

Helped develop the plan for round 2

02

Participant recruitment

Helped develop the screening questionnaire

03

Notetaking

Took notes during the sessions

04

Synthesis

Supported synthesis of the sessions

Understanding what motivates people

We needed to look beyond whether participants could navigate the interface.

Our research involved two rounds of moderated usability testing with existing Healthy 365 users. Our research included:

01

Round 1 Usability Testing

Evaluating challenge discoverability, comprehension, motivation and the overall participation journey.

02

Round 2 Usability Testing

Evaluating refined interactions, challenge structures, progress tracking and engagement.

03

Participant Screening & Recruitment

Identifying participants with relevant activity levels and Healthy 365 usage habits.

04

Research Synthesis

Identifying behavioural patterns and usability challenges to inform improvements.

WHERE I CAME IN

I supported research planning, recruitment, moderation and synthesis, including developing the screening questionnaire and discussion guide for the second round.

Beyond usability, I was particularly interested in understanding what made participants want to join a challenge and what might discourage them from following through.

Finding the right people was a challenge of its own

Sometimes, the hardest part of research happens before the first session even begins.

One of my biggest challenges was recruiting participants who genuinely matched our research criteria. We needed Healthy 365 users with lower recorded moderate-to-vigorous physical activity (MVPA) levels. However, some respondents described themselves as inactive despite exercising regularly, while others claimed to track their MVPA without owning a fitness tracker.

I realised that self-reported activity levels weren't enough to determine participant eligibility. To address this, I personally called prospective participants to verify their exercise habits and how they tracked their activity. I also updated our screener to request screenshots of their recorded MVPA.

These additional checks helped us make more informed recruitment decisions, while recognising that recorded activity might not fully reflect someone's actual effort.

WHAT IT TAUGHT ME

It taught me that good recruitment isn't just about filling participant slots. It's about making sure we're speaking to the right people.

Standing up for the demographic questions

A small question in a recruitment survey turned into a decision that shaped who we heard from.

HPB felt demographic questions weren't needed in the recruitment survey for our usability tests. I disagreed and made the case for keeping them, and with my manager's recommendations alongside mine, HPB agreed.

WHY I PUSHED FOR THEM

A usability test only shows us the people in the room. Demographic questions let us check who those people were.

They helped us recruit a deliberately varied group, and gave us the context to read what we observed later. If participants struggled with wording, navigation or motivation cues, we could tell whether that was widespread or limited to certain kinds of users. It also reduced the risk of designing for only a narrow slice of people.

It came up in our second round. Most of the selected participants were university graduates, as fewer non-graduates applied or were suitable. That may reflect barriers to taking part, such as schedule constraints or the effort of completing the survey, and it may also have shaped how people responded. Without the demographic information, we couldn't have noticed this, or asked whether a more varied mix would have told us something different.

WHAT IT TAUGHT ME

It taught me that demographic questions help us see whether our insights are broadly representative or shaped by the people we happened to speak to.

Core discoveries

What usability testing showed about motivation, and what I took from it.

When the numbers don't tell the whole story

Being less active on paper doesn't necessarily mean being less active in real life.

Interestingly, our recruitment challenges reflected something we later explored during usability testing. Some participants exercised regularly, but their recorded activity didn't always reflect their actual effort. This raised an important question.

AN IMPORTANT QUESTION

If someone's activity data doesn't accurately reflect their effort, how might that affect their motivation to participate?

It made me think more carefully about the relationship between data and the people it represents. A system might use recorded information to personalise an experience, but that doesn't automatically mean it will feel personal or fair to the user.

WHAT I TOOK FROM IT

Personalisation isn't just about using someone's data. It's about making sure the experience feels relevant to their reality.

Understanding a goal isn't the same as knowing how to achieve it

Sometimes, people don't need more encouragement. They need to understand what they're working towards.

Another interesting area of our research was how participants interpreted activity targets and progress indicators. Even when participants understood that they needed to achieve a goal, they weren't always sure what that meant in practical terms.

THE DISTINCTION

Knowing that you need to increase your activity is different from knowing which activities could help you get there.

This reinforced the importance of asking participants to explain their understanding in their own words, rather than assuming successful navigation meant successful comprehension.

WHAT THIS REINFORCED

Completing a task doesn't always mean understanding it, and understanding a goal doesn't necessarily mean feeling capable of achieving it.

Learning through iteration

The second round of testing wasn't simply about checking whether the design had improved.

Our first round surfaced questions around comprehension, navigation and motivation. For the second round, I helped translate these findings into a more focused research plan and discussion guide. We needed to distinguish between different types of difficulties.

POSSIBILITY 01

Finding it

Was someone struggling because they couldn't find the challenge?

POSSIBILITY 02

Understanding it

Because they misunderstood how it worked?

POSSIBILITY 03

Wanting to do it

Or because they understood it perfectly well but didn't feel motivated to participate?

Each situation suggested a different problem. This influenced how I approached moderation, encouraging me to probe participants' reasoning rather than relying on whether they said something was clear or motivating.

WHAT I LEARNT

Researching motivation isn't about convincing someone that an experience is motivating. It's about understanding what genuinely influences their decisions.

WHEN A DECISION WENT ANOTHER WAY

Research doesn't win every decision. At one point, the client removed a feature that our research had found useful for helping people pace their week.

Looking back

Good research starts long before the first question is asked.

One of my biggest takeaways from Healthy 365 came from the recruitment process. What initially seemed like a straightforward screening exercise taught me to question self-reported information and take additional steps to verify participant eligibility. The usability sessions also challenged me to think beyond whether someone could successfully use an interface.

ONE PARTICIPANT

A participant might understand the experience but feel little motivation to participate.

ANOTHER PARTICIPANT

Another might genuinely want to become more active but feel discouraged when their recorded progress doesn't reflect their effort.

These experiences made me more conscious of how usability, motivation, trust and personal circumstances are connected.

MY BIGGEST LESSON

My biggest lesson was that good research isn't just about asking the right questions. It's also about making sure we're asking them to the right people and understanding the context behind their answers.

Now read Track 02: Badges

NEXT PROJECT

The Last Hour