There is a specific kind of meeting where a team walks through their own onboarding, agrees it is clear, and ships it. Two weeks later activation has not moved and nobody can say why.
The reason is boring: you cannot un-know your own product. Once you know the account has to be created before the workspace, every screen that says so feels redundant. To a new user, it is the only thing holding the flow together.
The curse of knowledge, in practice
Designers and developers do not just know more than the new user. They know a different shape of the product. They think in objects — workspace, project, member. New users think in intentions — "I want to see if this thing can do X before I invite my boss."
When those two models disagree, the interface usually wins the argument and the user leaves.
What a useful first-run test looks like
- Recruit people who match the buyer, not the budget. A friend from another department is convenient and worthless. They already trust you.
- Give a goal, not a script. "Get to the point where you would know if this is worth paying for." Then stop talking.
- Watch where they stop talking. Silence and re-reading are the signal. People rarely announce confusion; they just slow down.
- Test the empty state. Most onboarding demos run on seeded data. Real accounts open with nothing in them, and that screen is doing more persuasion than any tour.
If you have to explain the flow before the test starts, you have already found the problem.
One habit worth stealing
We ask every new hire to sign up for the client product on their first day, alone, while recording their screen. They will never be that ignorant again, and that ignorance is the most valuable thing they own for about forty minutes.
Those recordings have caught more onboarding problems than any workshop we have run.