01Overview
Overview
Financial interfaces are often designed around the people administering an account. But beneficiaries experience the system very differently. For them, the central questions are usually much more immediate: How much money do I have? What happened to my account? Where is my payment? What am I allowed to do? Who do I contact if something looks wrong?
My work on the True Link beneficiary experience focused on making important financial information easier to understand and reducing the amount of interpretation required to use the platform.
02Understanding the Audience
Not a single uniform user group
Beneficiaries were not a single uniform user group. People had different levels of financial knowledge, technical confidence, ability, and familiarity with trusts. That meant we could not assume that terminology commonly used by administrators would make sense to the person receiving the benefit.
Financial products also carry emotional weight. Confusion in a social application is annoying. Confusion about money can be frightening. That made clarity particularly important.
03Redesigning the Beneficiary Page
Hierarchy before navigation
The beneficiary experience needed to establish hierarchy immediately. The page had to help someone understand their account before asking them to navigate deeper into the product. We worked through the organization and presentation of beneficiary information so that important information was easier to identify without exposing every possible piece of financial data at the same visual priority.
04Designing for Clarity
Reducing the translation users have to perform
A major design goal was reducing the translation users had to perform in their heads. That meant examining financial terminology, labels, status information, account organization, navigation, actions available to beneficiaries, and error and recovery experiences.
Whenever possible, the interface needed to communicate what was happening rather than simply expose an internal system state.
05Working Within Constraints
Requirements vs. inherited complexity
Financial design involves regulatory and operational constraints that cannot simply be redesigned away. Some information has to exist. Some actions require additional verification. Some workflows cannot be made instant. My job was often to work inside those constraints and make the experience as understandable as possible.
That meant collaborating closely with product and operational partners to understand which parts of the workflow were requirements and which parts were simply inherited from how the system had always worked. That distinction created room for design.
06Responsive Experience
Hierarchy has to survive the transition
The beneficiary experience also needed to work across web and mobile contexts. Financial information changes dramatically when the available screen space shrinks. The solution cannot simply be to make the desktop interface narrower.
Hierarchy had to survive the transition. Primary information needed to remain primary. Secondary information needed to remain discoverable without taking over the entire screen.
07Trust Through Interface Design
Predictability builds confidence
Trust in a financial product is affected by more than branding. It comes from predictability. Users need to understand what happened, why it happened, and what they can do next.
A vague status, unexpected change, or unclear action can undermine confidence very quickly. That made small pieces of UX writing and interaction behavior just as important as larger page layouts.
08What I Learned
Complexity can stay in the system
Designing for beneficiaries reinforced that complicated systems do not require complicated interfaces. The complexity can stay in the system. The user should not have to carry all of it.
The designer's job is often deciding which complexity is necessary for the user to understand and which complexity the product should absorb on their behalf.