Turning an Ignored Analytics Section Into Insights Users Actually Want
Transforming the Analytics section from a data graveyard into a proactive financial companion people actually want to use.
Team
2 Designer
My role
UX Designer
Type
Concept project
Timeline
3 weeks
01- Introduction
Today, Revolut is more than a card. It has become a financial hub, used by over 65 million people. But despite being feature-rich, one part of the platform stayed behind: Analytics.
02- Problem discovery
Growth created frustration instead of empowerment. User feedback on Trustpilot and Reddit showed this clearly: many users don't even know the Analytics section exists, and the ones who find it say it's barely usable and hard to understand. What users really need is personalization and control over their data. For Revolut as a business, this is a trust problem. Every bit of frustration works against the trust they need from their users.
How might we?
How might we redesign Analytics so users feel empowered, not overwhelmed, when engaging with their financial data?
Understanding the Fear
We talked to 12 users, one on one. We wanted to understand how they think, not just what they click. One thing became clear fast: users avoid Analytics to protect themselves from stress. They don't want more data. They want data that makes sense.
Testing the Interface
So we ran a heuristic evaluation. We also checked the interface ourselves. We found three problems. The navigation was confusing. People couldn't find what they needed. Some words were hard to understand. And users had no control over their own data.
Learning from others
We also looked at how other apps solve this. Wise uses simple tooltips to explain hard terms. Other apps show what's left, not what's spent. That feels calmer for users.
But we noticed something too. Most competitors have the same problem. They overload users with information, just like Revolut.
Not Everyone Looks the Same
We noticed users have two types of horizon. Some track their money lightly, in the short term. Others track it deeply, over a longer period.
Qick-check Sarah
She uses Revolut every day for small payments. She only checks her balance when something feels off. Analytics feels like extra effort, too many numbers for no real reason. She just wants one number she can trust, enough to know she's okay for the rest of the month.
Planner Jeff
He compares his spending month to month, looking for patterns. But when expenses and deposits show up in different places, or a category is wrong, he stops trusting the numbers. He needs one clear view he can rely on to make real decisions.
Users avoid Analytics to protect themselves from stress
They don't want more numbers. They just want one answer: am I okay this month?
Analytics isn't part of daily habit
It feels hidden. It's not connected to what people do every day.
Users want insights, not just records
They want to know what's coming next, not just what already happened.
04- Constraints
Every design has real limits like this project.
Sensitive data
Financial data is very sensitive, which doubles the user's fear and anxiety.
No access to live data
We had to design the solution without having access to live data.
Small screen, dense data
Displaying dense financial data on a narrow mobile screen significantly increases the user's cognitive load.
05- Solution Mapping
Building User Trust Through Insight
We explored many ideas using an Impact/Effort matrix. This solution rose to the top.
Giving users the right insight, at the right moment, in the right place. This reduces friction and builds trust over time.
We approached this through two models. To prevent cognitive overload on a narrow screen, we layered the information. We wanted users to reach their financial data differently: not through numbers first, but through trust built by insight.
Periodic & Gamified Insights
Insights are delivered in a gamified and story-based format to make financial reflection simple and engaging.
Give more control
Proactive AI Insights
AI Aira provides smart, proactive insights to guide users before they feel confused or overwhelmed.
Design decision 01
Not every user wants to dig through data. So the home screen shows quick, insight-driven banners first, while the full Analytics page stays there for anyone who wants more.
Overview shows budget status for today, this week, and this month, along with a short banner, like a spending update or a wrap-up.
Full view is the same detailed page from before. Nothing removed, just moved one tap away.
Design decision 02
Awareness Questions
A Guess, Not a Report
The first version failed in testing. 70% of users didn't understand why it existed. So instead of fighting that reaction, we leaned into it. The screen became a guessing game about the user's own money.
Users pick where they think most of their money went. Selecting an option expands into a short preview, so they can confirm their guess first.
The question isn't hidden inside Analytics. It shows up as a small widget on the home screen, at different times.
Design decision 03
A Season,
Not a Statement
A flat end-of-month total feels cold, and research showed it makes users disengage. So the wrap-up borrows a familiar format, a season recap, built from real moments instead of raw numbers.
It highlights real moments, like a trip or a spending streak, not just a total.
Tapping in still leads straight to the full Analytics page, for anyone who wants more.
Design decision 04
An AI That Explains, Not Reports
Users don't want more charts. They want one honest answer. So Aira lets users ask a direct question and get a plain answer back, using only their own data.
A designed personality. Like any agent, Aira has its own persona and behavior profile, so it responds based on what the user actually needs.
Clear, compliant copy. The wording follows the AI Act. Users always know they're talking to AI, what task it's doing, and that their data is protected. This builds a real sense of control.
06- What I learned
Every project has real limits. I don't see that as something to fix once. It's just part of doing this work, always.
Trust turned out to be emotional, not informational. Adding more features doesn't fix distrust. Users need to feel confident in what they're looking at, first. That's also why Aira came late in the process, not early. AI should follow a real problem, not lead the design.
And even in fintech, the biggest wins didn't come from more data. They came from understanding how people actually feel about their money.
07- Looking ahead
How I'll Track Success
If shipped, three numbers would tell us if this worked:
View Switching Rate
% of users who move from Overview to Full view. Validates whether progressive disclosure actually reduces overwhelm, not just whether it looks simpler.
Return Rate.
Return Rate. Do users come back to Analytics more than once over a few weeks? This separates real habit from a one-time curiosity click.
Downstream Financial Action
Downstream Financial Action. After seeing an insight, do users act on it? For example, setting a budget, opening a savings vault, or fixing a wrong category. This shows real financial awareness, not just screen time.
More Works
