Optimizing an Onboarding Journey
Fixing a lose-lose-lose scenario to make sure users stick around.
This is the 2 min summary!
Optimizing an Onboarding Journey
Fixing a lose-lose-lose scenario to make sure users stick around.
This is the 2 min summary!
Skills demonstrated
The problem: Potential new users were struggling during the onboarding phase.
I had to do something about the onboarding journey, as the customer success rate was not too satisfactory.
Based on the information I was given, the users we were attracting were:
While we looked for potential test participants to test our current onboarding journey, I was also formulating a test methodology.
I had prepared a plan to test the entire onboarding journey, including:
Within a few days, we had gathered 6 participants.
I scheduled and conducted tests with each participant. I made sure to record each test.
I had 6 documents with detailed information about how each participant fared throughout their onboarding journey. I scoured through these documents to find, and organize, an affinity map of all the trends and patterns.
At this point, it was time to make the actual journey map. The "columns" are in chronological order of the journey, and each row breaks down what the user may be doing, thinking and feeling at each step.
There were various issues throughout the journey, but none as prominent as what I called the "Valley Of Despair" (the prominently red area in the "Feeling" row).
When I was presenting the findings to my company, I called the red area the "lose-lose-lose" scenario.
There were some other issues regarding window placements etc. as well.
As mentioned, most of the issues were not about what we were offering, but lack of clarity.
Most of these issues could simply be solved with well placed copy.
I was able to annotate every part of the site which was proving to be problematic:
Using this plan, I then created mockups of the various pages which implemented solutions from findings.
These changes were very quickly made by the webdev team.
Some website performance issues were handled by our developers as well.
We had made the necessary changes to improve the onboarding journey for our users.
Some of these changes were:
We conducted another onboarding journey test a few months later, and the result spoke for themselves:
Overall the users flew through the journey and had no issues with discovering the site, browsing, downloading and running the app.