Helping Singaporeans plan for life, on their own terms
PLAN WITH CPF
Jan 2025 - present
We brought 8 planning tools into one place, organising them around how people think about their lives. Along the way, research proved two of our assumptions wrong, and we pivoted. The resulting patterns now form a UX playbook for future hub-and-module products.
8
planning tools unified
80%
CSAT
1:15
designer to product team
Company
Central Provident Fund Board
Role
Sole product designer
Contribution
Product strategy, research, UX design, prototyping, facilitation
Team
1 product designer, 10 product owners, 5 developers
The problem
Members want to plan, but are intimidated
CPF exists to help Singaporeans achieve a secure retirement, including a lifelong income in their later years.
While CPF offers a range of financial planning tools, they sit on different pages, and assume some knowledge of policy. Someone wondering “Will I be okay in retirement?” first has to work out which tool to use and what the jargon means. Many want to plan, but are intimidated and give up.
The hypothesis
If members are empowered to decide what matters to them, planning will be easier
Our working assumption was that if members could decide what to focus on, planning would feel less overwhelming.
As such, we organised planning around life areas instead of tools: retirement income, home ownership, health insurance, legacy planning, and growing liquidity. This meant funnelling 8 existing tools under these areas, which became PLAN with CPF (PLAN).
PLAN's experience follows a loop: see where you stand, see the gap to your goal, take guided action, then recalibrate as life changes. Goals change, planning shouldn't be one-off.
But how do we make members feel empowered?
Attempt #1
We showed members what good looks like. They felt judged
Early dashboard explorations used a checklist with a "100% complete" state, on the assumption that a sense of progress would make the product engaging, and engagement would make it useful.

Some of the team's initial explorations for the dashboard, using a "100% complete" state
Usability testing showed the opposite. Members have different financial priorities, so an incomplete checklist felt like being marked down for skipping things that weren't relevant to them.

You are rating me when I didn't ask for it, what gives you the right?
Pivot #1
So we laid out the planning areas and let members decide what's important
We replaced completeness with five planning areas, each showing whether there’s something worth acting on. This went live as part of PLAN’s first go-to-market milestone.

The implemented design presents the five planning areas, allowing citizens to decide how to act without enforcing completion.

Explorations for the individual status indicators — this was fun!
This addressed how members get an overview of the planning they can do for their lives. The next question was regarding what happens if they start acting on them.
Attempt #2
We broke planning areas into modules, but moving across each one confused members
The Retirement Payout Planner used a straight-through flow that required members to finish their planning in one sitting. Many dropped off along the way, and the data couldn’t tell us why: members were either giving up midway, or getting what they needed and leaving.

Indicative user funnel of the Retirement Payout Planner. Most members did not get to task #3.
Since we couldn’t tell which, we bet on a design that would work either way: a central Hub with standalone modules. Members could pick their starting point, and once done they're strongly pushed towards the next task.

A hub with standalone modules, so members choose where to start.
But in research interviews with citizens, back-to-back calculations with overlapping inputs left people disoriented, especially those unfamiliar with CPF policy. Yet, when sessions ended back at the Hub, almost all had a moment of clarity:

I didn't know what was going on. But this page is the most useful, at one glance I know already. This is the saving grace, I feel happier now.

Observing a participant as she interacted with the prototype during usability testing. (Photo taken and used with permission, masked for privacy.)
PIVOT #2
So we learnt to always present each module as part of a whole, and let members choose what's next from there
The Hub, it turned out, was what grounded people. So the version we shipped brings members back to the Hub at the end of every task. There, they can make sense of what they just calculated and decide for themselves what to do next.

The version we shipped. Members are always brought back to the Hub.
What makes the Hub work is that the relations between calculations become clear through visual design: where a member’s savings are headed, what they actually need, and the gap between the two.
Recommended Hub design, with illustrative figures. $555 projected against $845 needed leaves a $290 monthly shortfall. The launched version differs in copy and some details, following refinements during implementation.
Outcome
Planning now sits in one place, and we've connected with a wider audience
When PLAN launched in July 2025, it was the first time CPF’s planning services appeared together as one suite. Since then, unique users across the planning tools have grown significantly, reaching members who hadn’t used these services before. In addition, a high returning rate and 80% CSAT suggest they found it worth coming back to.
Beyond the product itself, the research clarified how members want to engage with CPF on financial planning, and set UX guidelines that future hub-and-module products can build on.
The Straits Times: CPF members can make housing, retirement and health insurance plans with new digital platform

How I worked
As the only designer, I kept members in the room for every decision
I was the only designer, split between an existing squad and this new product team. To manage my bandwidth while ensuring that member experience was not compromised, I coached the team on weighing simpler UX trade-offs themselves, and kept research findings in front of every conversation.
I also facilitated a workshop with 16 colleagues across product, tech and operations — asking what a citizen would value decades from now, and why. Five benefits came out of it:

The five benefits gave us a shared lens for subsequent roadmap decisions: which member benefit would this serve, and for whom?


Facilitating the workshop with 16 participants across PLAN and its sister team
Takeaways
What I'd carry into the next product
Test the premise, not just the design. Engagement and usefulness are different things.
Context makes numbers useful. More calculations won't help if people don't know why they matter.
Always ask why. Anyone can produce screens, even AI. Craft is knowing what problem deserves one.