Incorta is a business analytics tool which allows users to upload data, create and share insights and dashboards.
The follwing is the path that the company hope users would follow after logging in for the first time
- Connect to database
- Create new schema
- Load tables in schema
- Create a dashboard
- Build charts in dashboard
After analyzing the onboarding process of Duolingo, Salesforce, and Zendesk, we noticed that some common techniques are applied:
- Tooltips are embedded in the system & takes users through a series of steps
- Interactive elements are included
- Sample data is given for users to 'explore'
We were told that our target users are salespeople who will be testing out the product before deciding whether or not to purchase the full version.
Our persona Omar is a first generation Iranian-American who was born and raised in the Bay Area. He is familar with using Salesforce, but has no technical background.
Based on test results from the paper prototypes, we decided that the onboarding flow should consist of
step-by-step tooltips which guide users to upload data, followed by going through an example using the sample data.
We proceeded to create high-fidelity wireframes in Sketch and to build an interactive prototype on Marvel with this flow.
Testing with the hi-fi prototype revealed some major areas to improve on:
“It’s too long!”
Users were overwhelmed by the length of the onboarding and the amount of information that is presented to them. We realized that we need to reduce the length of the text and to cut out/merge some of the steps.
“What’s a schema?”
Many users were confused by the technical terms used in the onboarding flow. So we decided to add informative tool tips to help users to understand the vocabulary used by the system
“Where am I?”
Users lost track of where they were in the onboarding process after certain transitional screens. From this, we learned that users want to always see their progress and to estimate how much more effort is needed.
At this point, we had many questions about how to proceed.
We decided to go to our mentor at Google Ventures to get a different perspective on the problem. With the help of a UX designer at GV, we were able to arrive at our final solution:
Instead of embedding the tooltips into the system, and forcing the users to go down a path through a series of steps, create a tutorial which includes a series of annotated screenshots & allows users to access it from the system via the support section.
This solution is straightforward and easy for the engineers to implement.