Onboarding and Activation

I was one of two mobile designers on the growth team. I introduced and led our team to use Lottie, a framework of scaling animations on different devices launched by AirBnB.

When I joined the growth team, we were in the habit of adding lots of animation, delightful moments in order to encourage people to onboard into our app. At the time, we were using primarily GIFs for animations which has compression issues (up to 256 colors only), and did not scale for different devices.

I worked with engineering to launch Lottie into our day-to-day workflow. After setting Lottie up on After Effects with Bodymovin’ plug-in, I taught two of our designers how to use AE and export animations into .json files for the engineering team. We continued to use Lottie for animations after I left the team. I worked with engineers to optimize speed.

 
 

Evernote is the perfect company to think about growth. Growth for the most part is misunderstood. Usually, when people think of the growth funnel, they think of the marketing funnel, which is the top 2 segments in this upside triangle. Growth touches on all aspects of the funnel. As a designer on this team, every single stage is a user touchpoint. We don’t just care about discovery, but we also care about activation, retention, revenue, and referral. We have to understand the product in a holistic way, because only then can we guide the users to see the value in it.

We start out with an experience map where we look at the actions and mindset that a user might have when they are researching a productivity app. What makes Evernote unique from all other productivity apps out there? From there, we can discover moments in a user's journey where they might feel convinced (or, not convinced) and find opportunities to retain them through the onboarding process. It's important to recognize that onboarding is not just the first experience.

That's where retention comes in. We care a lot about NAU (Newly Active Users), which is a metric we use to measure retention.

A user is considered newly active if they create 1-2 notes in their first session, as well as come back for a 2nd session within their first week.

We've discovered that users who are in this data point tend to come back and become long-term users, and many of these users will be retained and end up converting. Although, it's not a total loss if they do not end up converting because we have also learned Newly Active Users do end up converting at some point in their journey, especially if they find value in our product. At the end of the day, users will pay for a product that they find value in. The problem isn’t getting users to pay us, it’s to get users to find the value so that they are willing to pay us.

 
 

Experiment A

 
 

We ran an experiment where we asked users about their use case and then showed them relevant note types based on their answers. We introduced a checklist experience that will guide them through their entire onboarding journey, including the first launch experience throughout their entire life cycle with Evernote.

We learned from this experiment that it lifted metrics we didn’t even personalize. People felt like they were getting a personalized experience, and so they decided to proceed and come back.

The result was a 3% activation (NAU) lift across the board, and we saw users coming back the second and third week. We learned from this experiment that it lifted metrics we didn't even personalize. People felt like they were getting a personalized experience, and so they decided to proceed and come back.

Although our checklist experience did not lift retention, it drove a lift in the usage of features. It drove a 60% lift for web clipper (one of our features), and 8% for attachments. 30-40% of users who came through the onboarding engaged with the checklist. We found that users who selected the student use case engaged the most with the checklist.

 
 
 

Experiment B

 
 

In onboarding, a lot of the times the flow cannot be too long because of the drop-off problem. Logic says longer flow equates to higher drop off rates. While this is true, because users were engaged from the get-go and saw value in answering all questions, there was very little drop-off despite a longer flow.

For a second experiment, we added 3 questions on top of version one. We expanded and personalized the checklist.

From this experiment, we saw a 5% lift on newly active users, a 3% lift on users coming back the second week, and a 7% lift in week 2 and week 3 in note creates.

It improved engagement across the board and personalizing the checklist led to 7% more users using it. In onboarding, a lot of the time the flow cannot be too long because of drop-off. However, in this case, users were engaged from the get-go and saw the value in answering all of the questions. There was very little drop-off despite a longer flow.

 
 

 

Mobile Experience

 
 

With these learnings under our belt, how do we repackage web learnings for a mobile app experience? Some questions we asked were:

How can we keep the mobile experience compact and short?

Which mobile-specific features should we highlight?

How do we design education for features that are still in flux?

How do we simplify the complexity of Evernote and deliver the 'ah-ha!' moment fast?

How do we ensure users understand the relationship between first session onboarding, with extended onboarding in the mobile space?

How do we best fulfill best practice requirements? Such as asking for permissions, free trial interstitials, etc.

Access the trade-offs in which we have had positive impacts on key features in the past, so we want to make sure those come through in the new experience.

We made some key decisions as a team:

Keep personalization questions (use case and note types for mobile).

Make it quick and easy to understand to get through (less text, more interaction).

Requirements: show a permission screen, and showcasing templates.

Made decisions about education around editor menus (insert, formatting, lists).

Translate the desktop checklist into a mobile checklist from a UI standpoint.

Made decisions about which mobile-only features to show, with extended onboarding.

 
 
 

Process for Mobile Designs

 
 

We implemented the first flow in a prototype, and ran a user test. From the research, we found out there were general themes that stood out:

Choosing 1 use case made people feel boxed in.

There was an ‘ah-ha’ moment when we first introduced the insert menu. Meaning that people saw the value in Evernote when we revealed this to them. Someone said, “I didn’t know Evernote offered this many options in their editor. It seems pretty powerful and unique. I don’t think I’ve seen other apps offer this.

Furthermore, it validated that the checklist was clear in form and function. The order needed to be re-arranged though, the value wasn’t immediately clear. There is value in being able to minimize and dismiss the checklist.

Users had a specific mental model of templates when we showed it at the beginning of the flow. They thought this was how you were supposed to start a note every time. Whether or not that is a good or bad thing is up for debate, but users kept trying to find the same micro template interaction again and expected it whenever they would create a new note.

We answered some questions through research, but other questions popped up from this research:

Should the editor tutorial be re-playable?

What do we do about the microtemplate mental model?

Should we add an extra question to narrow down personalization?

How do we make sure users understand the value from a checklist interaction, is there is a strong connection between onboarding and extended onboarding?

Although not part of the scope, the free trial interstitial at the beginning came up a lot during user research. Did we want to test more on this or save it for a future test?

Do we want to surface installing Evernote on other devices?

We had a ton of learnings from this experience, and made our best guess while the final designs. We worked with developers to ship this out the now, and I’m proud to say that the experiment is live and doing well. We plan on pushing this as the control experience.

Final conclusions:

Onboarding means working on that crucial moment of users making a decision: Is this is the right app for me? Is it doing what I want it to do? And even more…

During our time of designing this, our company was going through a large shift in changing clients. Lots of UI elements and pieces were still in flux. It was difficult keeping up with all of the changes that had to change again, as is the nature of tech.

This provided us a nice framework for future education around new features that will be released and allows us to experiment even more with user education.