clearer finance. more control. for everyone
“Make it bigger.”
That is often where the thinking starts when people talk about designing digital finance for older users.
Bigger text. Bigger buttons. Fewer options.
Useful? Sometimes.
Enough? Not even close.
Older users are not a single audience with a single set of needs. Someone in their 60s who has used online banking for twenty years may be far more digitally confident than someone half their age who rarely touches an app.
The real design challenge is not designing for age.
It is designing for confidence, comprehension and control without making the experience feel simplistic or patronising.
familiarity beats cleverness
Financial products are full of patterns that change over time.
Navigation moves around.
Buttons change position.
Filters behave differently.
New authentication methods appear.
A designer may see a cleaner interface.
A user may see a completely different product.
That matters when someone is already comfortable with the old experience.
Consistency is not about keeping every pixel frozen forever. It is about making changes understandable.
If an interaction has changed, make the new behaviour obvious.
If a familiar label has moved, retain enough context to help people find it.
If a process is new, guide people through it rather than assuming they will immediately understand the pattern.
clarity matters more than density
Financial interfaces often have a lot to say.
That does not mean everything needs to be visible at once.
A crowded screen creates a different kind of accessibility problem. Users have to scan more, compare more and remember more.
For someone who is less confident digitally, that can quickly become tiring.
Good hierarchy helps.
Put the most important information first.
Make the primary action obvious.
Keep supporting detail available without forcing it into the main path.
This is not “designing down”.
It is simply making the interface easier for everyone.
do not hide the detail people actually need
There is a balancing act here.
Simplification can go too far.
Someone reviewing a pension or investment portfolio may genuinely want to understand valuations, performance, transactions or tax information.
Replacing all of that with:
Your investments are doing well
is not a better experience.
It is less useful.
The answer is progressive disclosure.
Give people the headline first.
Let them move into the detail when they need it.
A strong summary can make a complex financial product feel manageable without removing the complexity underneath.
authentication is a confidence issue too
There is a good example in login and security.
Two-step verification is sensible.
It can also feel like a completely unnecessary obstacle when the user is already struggling to understand what is happening.
“Enter the code from your authenticator app” assumes quite a lot.
Where did the code come from?
Which app?
Why do I need it?
What happens if I cannot find it?
Clear supporting copy can remove much of that anxiety.
The same principle applies to biometrics, passcodes, trusted devices and recovery journeys.
Security should feel reassuring.
Not mysterious.
error messages should never make the user feel stupid
Nobody gets every interaction right.
That is particularly important in finance because users may already feel slightly nervous about making a mistake.
“Invalid input” is technically informative.
It is not particularly helpful.
“Enter the date in DD/MM/YYYY format” gives the user somewhere to go.
The difference is small.
The effect is not.
Good error handling tells people what went wrong and what to do next without implying they have done something ridiculous.
support the user without taking control away
There is also a danger in overcompensating.
Make everything too simple and you can end up removing useful control.
Add too much guidance and the product starts to feel patronising.
Neither is particularly good UX.
A better approach is to provide confidence without dependency.
Show people what is happening.
Explain unfamiliar terminology.
Provide help where it is relevant.
Make important actions reversible where possible.
Then let people get on with it.
The goal is not to hold someone's hand through every screen.
It is to make sure they know what their hand is doing.
design for real-world conditions
There are practical considerations too.
Someone may use the product on a small phone with large text enabled.
They may be reading in bright sunlight.
They may be distracted.
They may have reduced dexterity.
They may simply be tired.
None of these are exclusively “older user” problems.
They are human problems.
Which is why the strongest solutions often make the experience better for everyone.
Readable typography.
Clear focus states.
Adequate touch targets.
Good contrast.
Plain language.
Predictable navigation.
Strong feedback.
These are not special features for one demographic. They are signs of a well-designed product.
do not confuse confidence with expertise
This is probably the most important distinction.
A user can be completely capable of managing their finances and still dislike a confusing interface.
They can be experienced with investments and still want a clearer explanation.
They can be digitally confident and still appreciate larger controls.
Age does not tell you how someone behaves.
The interface should not make assumptions on their behalf.
Instead, design for the conditions that create confidence:
I know where I am.
I understand what I am looking at.
I know what happens next.
I can recover if I make a mistake.
That is a much better brief than “make it easier for older people”.
a useful checklist
When reviewing a financial experience, ask:
Can users understand the hierarchy without having to decode the screen?
Are unfamiliar interactions explained at the point of need?
Can people access detail without being overwhelmed by it?
Do security and error states feel reassuring rather than intimidating?
Are changes to familiar journeys clearly signposted?
Can users complete important tasks without unnecessary precision or complexity?
Does the experience provide confidence without taking control away?
Designing for older users should not mean designing a different, watered-down version of finance.
It should mean designing an experience that respects people's experience, gives them clarity and does not make them feel as though the product has decided they cannot cope with complexity.
Because most people do not want less control as they get older.
They want more confidence that they are in control.