Skip to section:

• Discovery
• Solution
• The end

The problem

The client has pointed out that there is a low install to registration ratio. One of their requirements was that the onboarding process needs to be optimised to engage the users more before registering, and the other hypothesis was that there is a problem with the registration process itself.

Understanding phase

My first steps was to get the app, make sure I click everything to understand it, map it as a user flow on a Miro board and present my first thoughts about registration and onboarding to the team.

After this, I asked Saima, our analyst, to give me the exact screen names, event names and on a collaborative session, we saw a few numbers from analytics to get an idea on how to move next.

Plan and hypothesise

Plan and approach:

1. Review data from analytics to identify areas with low conversion rates and create hypothesis based on data aroundregistration & onboarding.
2. Create updated versions that need testing to validate our hypothesis and test these updates with clickable prototypes.
3. Analyse results & share recommendations for any optimisations that will improve conversion through the onboarding &registration flows.

What we see:

• •An average of 12% of the users use the skip button at some stage during the tour
• •A total of 12% drop in conversion by the end of the onboarding

5th of July to 1st of August

What we see:

• •A total of 41.5% drop in conversion by the end of registration.
• •A loss of 17 users during e-mailregistration when prompted to e-mail verification screen.
• •A total of 119 users return viathe social log-in (loss of 124 users during the social log-in accountverification).

5th of July to 1st of August

Hypothesis:

1. Users would prefer to register first and be offered an ”onboarding process” afterwards.
2. Users would be more likely to complete registration after having abetter/non- intrusive intro of app.
3. Users would prefer a tailored onboarding process, based on their specific need state.
4. Users find some steps within the flow to be repetitive, which puts them off.
5. Users would be more likely to complete registration if we ask about their dog first.
6. Alternative CTAs would increase the likelihood of registration.
   Ex. let them know that what to expect on the next screen.

Preparing for testing

We then went into Miro again and after a few collaborative sessions with the team, brainstorming on what we are going to be testing and how we will test our hypothesis.

The journeys to be tested:

1. Straight into the app (logged outmode). Ask for registration when the user attempts to add a dog or create a report.
2. Simplified registration process with prompts to complete onboarding once logged in.
3. Ask about their need state and then guide them to a tailored onboarding & registration.
4. Alternative CTAs for “register”and “create account” (within the current flow).

Testinng

The prototype:

Results

Extracting all the results from the testing sessions and sorting them out to find all the useful comments that will help us move forward.

• People expect, and prefer, to register right away.
  ‍
  • It feels more natural to register before everything, however it shouldn’t come at the expense of knowing what I’m registering for (so have a quick intro).
  
  • They believe that it makes more sense to register before putting the dog's info first (we tested that first and it didn’t work).
• We can simplify, or move onboarding entirely, but providing guidance is still useful.
  ‍
  • We don’t need to force onboarding, but it’s important to still guide people through the process (even if simplified).
• We don’t need a revolution. We’re starting from a position of strength.
  ‍
  • What NOSEiD does is still clear to people, and exciting!
  
  • The interface continues to receive very positive feedback.
  
  • The process we give them is what they are expecting to happen.

After this, the direction was quite clear, and we moved on to produce some ideas for solutions.

Solution ideas

Loads of brainstorming sessions, collaborative remote sessions and Miro board frames / canvases later.

The onboarding tour should be optional

There were lots of positive comments around the push notifications for an app walkthrough. Respondents appreciated the idea of being given the chance to get to know the app more, and this did not appear disrupt their journey.

The early introduction to the app

We also saw a few comments that made it clear to us, some people want to see what the app is about, before deciding to give their details away. This is why we delivered with a better copy explaining exactly what we do, with a link to an overlay video for a quick introduction to how the product works.

See your password instead of entering it twice

We also saw a few comments that made it clear to us, some people want to see what the app is about, before deciding to give their details away. This is why we delivered with a better copy explaining exactly what we do, with a link to an overlay video for a quick introduction to how the product works.

Sign-posting the fact that you’ll get an email verification

We also saw a few comments that made it clear to us, some people want to see what the app is about, before deciding to give their details away. This is why we delivered with a better copy explaining exactly what we do, with a link to an overlay video for a quick introduction to how the product works.

Thank you!

LinkedInDribblevaggosdesign@gmail.com

©Evangelos Angelis ️