Reducing drop-off rate at a specific point in the onboarding flow
MY ROLE
MY ROLE
TOOLS USED
TOOLS USED
THE TEAM
TIMELINE
PLATFORM
What is craggle?
Tired of seeing people jump through hoops to get a home loan, Craggle has made the application process easy and fast.
Tired of seeing people jump through hoops to get a home loan, Craggle has made the application process easy and fast.
what does success look like?

Peter Hudson
peter hudson
Peter works full-time as a manager in a multinational company. He makes decent money, but he and his wife can only save small amounts. Peters’ wife also works full-time. They bought a 4 bedroom house 3 years ago and have felt the pinch with the latest bank interest rises. They are about to refinance their mortgage.
Peter works full-time as a manager in a multinational company. He makes decent money, but he and his wife can only save small amounts. Peters’ wife also works full-time. They bought a 4 bedroom house 3 years ago and have felt the pinch with the latest bank interest rises. They are about to refinance their mortgage.
“We had no choice but to upgrade our home. Our kids needed more space, and now we have a mortgage beyond our means”
“Banks are so old and stuffy. I would jump at the chance to work with a younger company who actually gives a sh*t about me!”
HOW PERSONA SHAPES CRAGGLE’S UI
HOW PERSONA SHAPES CRAGGLE’S UI
Fun, personable and simple. Craggle speaks to its users, in a tone of voice they can connect with.
Yes - green means money. The additions of blue, turquoise and red give Craggle a colour palette that feels trustworthy, fresh and fun.
Simple designs paired with cute friendly illustrations. This allows Craggle to be both serious and personal.

After being live for 48 hrs - The engineers noticed that a large percentage of users submitted ‘about me’ info but nothing beyond that. Dropping off at the next screen (bank login).
Craggle was in its very first live ‘event’. The aim of this urgent project was to reduce drop-off rate at this specific pain point.
After being live for 48 hrs - The engineers noticed that a large percentage of users submitted ‘about me’ info but nothing beyond that. Dropping off at the next screen (bank login).
Craggle was in its very first live ‘event’. The aim of this urgent project was to reduce drop-off rate at this specific pain point.
THE PROBLEM
our HYPOTHESIS
Conversion Optimisation
So what we can see here is ...
By using Craggle, a user makes the initial steps of re-mortgaging a lot easier for themselves.
The power of the crowd: Craggle has done the hard work to build relationships with banks so the user doesn’t need to. Saving a lot of time and pain in the process.
By using Craggle, a user makes the initial steps of re-mortgaging a lot easier for themselves.
The power of the crowd: Craggle has done the hard work to build relationships with banks so the user doesn’t need to. Saving a lot of time and pain in the process.
By using Craggle, a user makes the initial steps of re-mortgaging a lot easier for themselves.
The power of the crowd: Craggle has done the hard work to build relationships with banks so the user doesn’t need to. Saving a lot of time and pain in the process.
By using Craggle, a user makes the initial steps of re-mortgaging a lot easier for themselves.
The power of the crowd: Craggle has done the hard work to build relationships with banks so the user doesn’t need to. Saving a lot of time and pain in the process.
This high-level data was collated via Microsoft Clarity. URL parameters are used to track popular pages and locate user drop-offs during the first 48 hours of being live.
This high-level data was collated via Microsoft Clarity. URL parameters are used to track popular pages and locate user drop-offs during the first 48 hours of being live.
From this visualisation I can see ...
It is clear that item no. 2 is the most urgent so my next step was to observe user videos in Microsoft Clarity.
It is clear that item no. 2 is the most urgent so my next step was to observe user videos in Microsoft Clarity.
Confidentiality barrier
Confidentiality barrier
Confidentiality barrier
In 2023, users don’t give personal information to anyone, let alone a new app they are signing up to. Asking users to sign in via their bank login, is unexpected and users are clearly weary.
In 2023, users don’t give personal information to anyone, let alone a new app they are signing up to. Asking users to sign in via their bank login, is unexpected and users are clearly weary.
In 2023, users don’t give personal information to anyone, let alone a new app they are signing up to. Asking users to sign in via their bank login, is unexpected and users are clearly weary.
Confusion / trust with flow
Confusion/trust with flow
50% of users in Group 1 go ‘backwards’ and forwards in the flow from the bank login onwards. Something about the bank login seems confusing or untrustworthy.
50% of users in Group 1 go ‘backwards’ and forwards in the flow from the bank login onwards. Something about the bank login seems confusing or untrustworthy.
50% of users in Group 1 go ‘backwards’ and forwards in the flow from the bank login onwards. Something about the bank login seems confusing or untrustworthy.
50% of users in Group 1 go ‘backwards’ and forwards in the flow from the bank login onwards. Something about the bank login seems confusing or untrustworthy.
Issues with Information architecture & UI design
Issues with Information architecture & UI design
Users don't easily know there is a manual input button hidden at the bottom of the page. This needs to be improved.
Users don't easily know there is a manual input button hidden at the bottom of the page. This needs to be improved.
Users don't easily know there is a manual input button hidden at the bottom of the page. This needs to be improved.
Users don't easily know there is a manual input button hidden at the bottom of the page. This needs to be improved.
Users don't easily know there is a manual input button hidden at the bottom of the page. This needs to be improved.
After tracking a group of users, it was clear from my observations, there is a problem with the bank login screen.
This data, alongside my higher-level analysis above, confirm that this change would likely be a positive move. This testing also helped identify other issues within the flow for future adaptations.
After tracking a group of users, it was clear from my observations, there is a problem with the bank login screen.
This data, alongside my higher-level analysis above, confirm that this change would likely be a positive move. This testing also helped identify other issues within the flow for future adaptations.

After tracking Group 2, it was clear we had made positive changes to Craggle’s final sign-up numbers.
After tracking Group 2, it was clear we had made positive changes to Craggle’s final sign-up numbers.
group 2: observing Clear results
Our initial goal for this project was to see a 30% uplift in sign-ups. The 51% improvement was 21% higher than we had hoped, so the project was a success!
This change remained consistent in the data observed over the coming days in the live web app.
Our initial goal for this project was to see a 30% uplift in sign-ups. The 51% improvement was 21% higher than we had hoped, so the project was a success!
This change remained consistent in the data observed over the coming days in the live web app.
Our initial goal for this project was to see a 30% uplift in sign-ups. The 51% improvement was 21% higher than we had hoped, so the project was a success!
This change remained consistent in the data observed over the coming days in the live web app.
Our initial goal for this project was to see a 30% uplift in sign-ups. The 51% improvement was 21% higher than we had hoped, so the project was a success!
This change remained consistent in the data observed over the coming days in the live web app.
Suggestions for future iterations
Split test x2 bank login screen designs:
a. Manual input up higher / more obvious
b. Redesigned bank login screen to build more trust.
Sign Up: With a 23% drop off rate at this point, data suggests users don’t feel comfortable signing up so early in the flow. We could explore different ways of presenting this with the UI, and also by placing towards the end of flow to test.
With the drop off rate at 20% on the final submission screen, there are issues we could look into. Because this is deep into the flow, I recommend pausing work on this section. Changes that take place earlier will now impact this part of the flow . We are likely to see a natural uplift once earlier issues are resolved.
Split test x2 bank login screen designs:
a. Manual input up higher / more obvious
b. Redesigned bank login screen to build more trust.
Sign Up: With a 23% drop off rate at this point, data suggests users don’t feel comfortable signing up so early in the flow. We could explore different ways of presenting this with the UI, and also by placing towards the end of flow to test.
With the drop off rate at 20% on the final submission screen, there are issues we could look into. Because this is deep into the flow, I recommend pausing work on this section. Changes that take place earlier will now impact this part of the flow . We are likely to see a natural uplift once earlier issues are resolved.
Split test x2 bank login screen designs:
a. Manual input up higher / more obvious
b. Redesigned bank login screen to build more trust.
Sign Up: With a 23% drop off rate at this point, data suggests users don’t feel comfortable signing up so early in the flow. We could explore different ways of presenting this with the UI, and also by placing towards the end of flow to test.
With the drop off rate at 20% on the final submission screen, there are issues we could look into. Because this is deep into the flow, I recommend pausing work on this section. Changes that take place earlier will now impact this part of the flow . We are likely to see a natural uplift once earlier issues are resolved.
Thorough user testing in advance of launch would have allowed us time to see these issues sooner. This would have allowed us to adapt our flow and UI designs with a greater user conversion at launch.
Cross-checking high-level with granular data is a very important part of this project. I was able to identify problems, confirm predictions and clearly understand decisions.
From start to finish it was an interesting project to be a part of. The urgent scenario allowed me to see the impact of one specific change in a user flow.
Thorough user testing in advance of launch would have allowed us time to see these issues sooner. This would have allowed us to adapt our flow and UI designs with a greater user conversion at launch.
Cross-checking high-level with granular data is a very important part of this project. I was able to identify problems, confirm predictions and clearly understand decisions.
From start to finish it was an interesting project to be a part of. The urgent scenario allowed me to see the impact of one specific change in a user flow.
Thorough user testing in advance of launch would have allowed us time to see these issues sooner. This would have allowed us to adapt our flow and UI designs with a greater user conversion at launch.
Cross-checking high-level with granular data is a very important part of this project. I was able to identify problems, confirm predictions and clearly understand decisions.
From start to finish it was an interesting project to be a part of. The urgent scenario allowed me to see the impact of one specific change in a user flow.