Onboarding is the process of guiding the user through all necessary steps for them to open an account. Since Revolut is a bank, we need to meet several legal requirements which, depending on the market, can mean up to 25 different steps. Still, we make the experience as seamless as possible by focusing on each step at a time and optimizing the journey for each market. This way the user can fully enjoy Revolut in just a few minutes.
For most of my time working at Revolut (2022-2024) I was the owner of the design of the retail onboarding. I worked with the POs Mariya Ollin and Alexander Grishchenko.
There are five main types of onboarding improvements I've worked on. Here I'll present one example for each category.
FIX KNOWN ISSUES
Key problem
Solution
Add a confirmation pop up to reduce typing errors, wrong numbers and wrong number codes
OPTIMISE JOURNEY
Key problem
Solution
ADD VALUE
Key problem
Solution
Support multiple country profiles for a single user
Why?
User want local accounts to get a local IBAN, receive their salary, provide proof when renting an apartment and get access to local benefits
Areas covered
This project was highly complex because it affects most areas of the app, including:
Sending and receiving money
Comms, notifications & suggested for you
Campaigns & Inbox
To-dos
Cards
Closing account
MONETIZE
Key problem
Solution
Improved assign logic
PREVIOUS
4 characters from the first name + 4 random characters
@nikoaw9f
NEW
The top 3 still available options will be visible for the user to choose from
@nikola
@nikbabic92
@nikola.b
@nikolababic
@n.babic
@nikola00
@nikola2000
@nikolababic2000
@nikola.us
@nikola.aw9f
BEFORE
AFTER
OPTIMISE WORKFLOW
Key problem
Solution
I took initiative to optimise the team's workflow with other projects that made collaboration easier and new projects easier to tackle
🩹
Standardized remediation flow
Around 50% of the Onboarding team's efforts go towards designing and developing flows to collect input from the user post sign-up. This is what we call remediation flows. The information collected in these flows is critical, since it's needed to fully onboard a user. Both design and development is treated case-by-case, resulting in a lot of additional work that could be streamlined.
I created a standardized formula to be used in all current and future cases, reducing the workload of the whole team significantly.
🧩
Figma library
Many of the 25 onboarding steps are used by other teams. For example, when a user edits their phone number they see the same flow as when they inputted it for the first time. This edit flow is owned by another team. Reusing onboarding steps across the company makes it difficult to keep up to date.
This is why I created an onboarding steps library. Designers across the company can take a whole block, consisting of all parts of a step (like collecting phone number) and all its variations (local variant, errors and success). This library was a big task, but it resulted in guaranteed up-to-date onbaording steps in all Figmas and improved team collaboration.