#stub
New users do not yet have the vocabulary to understand the appNew users do not yet have the vocabulary to understand the app
Imagine that you are in a foreign country where you don't speak the language. You're hungry and you need to ask someone on the street where to buy some food. You don’t have the words to say it, but you can probably rub your stomach and people will know where to point you.
If the app has sufficiently unique features or design, then encountering those will be like hearing words from a foreign language. If the features or design are familiar carryovers from other products that people are used t.... A big mistake that many people make when they try out a new app is that they’ll try to understand features in a very abstract sense. They will try to understand what it is without knowing what it is for. When people make this mistake, AdoptionAdoption
This page is simply to collect pages that link to it. Use this to jump to other locations.
goes down. Projects allow the app to Speak to the user with a shared vocabularySpeak to the user with a shared vocabulary
New users do not yet have the vocabulary to understand the app. They understand the product through the lens of their own goals and what's familiar to them. The company will generally have its own goals, like increasing the frequency of engagement. However, we can't just tell people to use the app every day. The user needs to have a reason to do so, articulated in terms of the user's own goals.
When working with clients, I often Use a badging system as a method of actionable user research to.... They put functionalities into context, closing the feedback loop on learning the usefulness of said features.
This is exactly what happened with Francesco D’Alessio from Keep Productive (sorry for the roast buddy but this is what happened 🙂️) when he tried to do a “first impressions” video on Roam, having made 10 dummy pages that weren’t useful towards any project. He tried understanding a novel app without context, so the app wasn't able to effectively communicate its value. No wonder he didn't get it!
In order to have a successful onboarding experience, you don’t need to learn every feature. The user should learn enough of the app’s functionality to accomplish a goalThe user should learn enough of the app’s functionality to accomplish a goal
If you are able to accomplish one of your User Goals within an app, then the app has done its first step towards gaining your Retention. One of the first steps to Satisfy the social contract between the user and the app is for the user to accomplish a goal.
This is the first step towards creating the virtuous cycle of User Involvement. Apps with continued user involvement enable the user to accomplish multiple goals, so over time the user will learn how they can accomplish more and more goal.... However, it’s still helpful to be aware of what features you have available to you so you can recognize the situations where you’ll need to learn it. Help the user to recognize situations for functionality usageHelp the user to recognize situations for functionality usage
User goals change over time as User skill level increases over time so being aware of the situations in which features are useful means you know when you need to learn how to use them.
Due to principles of Difficulty Matching, we know that if we ask a user to learn something too advanced early in, they will likely get frustrated and give up. This is a common problem with Notion and Roam users: they see people using the applications in advanced ways near the beginning of their experience and ....