Stop blaming users for bad financial products
Archil Vardidze4 min read·Just now--
Financial literacy is not your user’s job
We like to believe that users come to financial products prepared!
We assume:
- They understand interest rates.
- They can compare options.
- They can reason about long-term impact.
Reality is simpler — They don’t.
And more importantly, they shouldn’t have to.
The myth we keep repeating
Somewhere along the way, “Financial literacy” became a convenient assumption.
If users don’t understand something:
- They are not educated enough
- They need to learn more
- They should read before acting
It sounds reasonable — It’s also wrong.
Because what we call “Financial literacy” is not a stable baseline.
It’s a spectrum. Contextual. Emotional. Often inconsistent even within the same person.
A user might understand loans in one situation and make irrational decisions in another — under pressure, time constraints, or cognitive overload.
So when a product relies on literacy, it is not being sophisticated. It is offloading responsibility.
What financial literacy actually is
Organizations like the OECD define financial literacy as a mix of:
- Knowledge (concepts like interest, inflation)
- Skills (budgeting, comparing options)
- Behavior (saving, planning)
- Attitudes (risk awareness)
Clean definition. Useful for policy. Almost useless for designing a product.
Why?
Because none of this guarantees that a user, in a specific moment, will:
- Understand what’s on your screen
- Interpret your numbers correctly
- Make a good decision
The real problem
Financial products don’t fail because users lack knowledge.
They fail because:
- They expose raw data instead of meaning
- They expect interpretation instead of providing answers
- They show structure instead of outcomes
In other words, they make users solve puzzles.
What users actually care about
Not APR.
Not loan structure.
Not product types.
They care about questions like:
- “How much will I actually pay?”
- “Can I afford this monthly?”
- “Is this a bad decision?”
- “What happens if I do nothing?”
If your interface doesn’t answer these directly, the user is forced to simulate the outcome in their head.
That’s where mistakes happen!
Insight layer is not a feature
It’s the product.
An insight layer translates financial complexity into decisions.
Not dashboards. Not charts. Not more data.
Decisions.
Examples:
- Instead of showing interest rate → show total cost in real money
- Instead of showing balance → show time-to-zero based on behavior
- Instead of showing multiple options → highlight the best one and explain why
- Instead of showing rejection → explain what to change to get approved
This is not “Nice UX” — This is removing cognitive load.
Stop educating, start translating
There’s a common instinct to “Educate the user”.
Tooltips. Articles. Financial tips.
Most of it doesn’t work!
Because education requires:
- Time
- Motivation
- Cognitive effort
Users don’t open a banking app to learn, they open it to act.
Your job is not to increase their literacy.
Your job is to replace the need for it in the moment of decision.
A better model
Old thinking:
user should be financially literate
Better thinking:
product should be financially intelligent
This means:
- Anticipating intent
- Calculating outcomes
- Guiding decisions
- Reducing ambiguity
Not explaining how things work, just making sure the user doesn’t need to.
The uncomfortable conclusion
If a user makes a bad financial decision in your product, it’s rarely because they are not smart enough, it’s because the product made them think too much.
The bar going forward
The best financial products won’t win by offering more features.
They will win by:
- Answering questions before users ask
- Removing interpretation entirely
- Turning complex systems into obvious choices
Financial literacy will still matter, just not as a prerequisite!
