04.02 · Concept
Designing the First-Value Journey
Map the shortest path from a new account to first value, and cut every setup step that does not sit on it.
First value is the first meaningful result a new user came to get, not a completed setup checklist. Treat onboarding like a request path: identify the critical route from account creation to that result, then remove, postpone, prefill, automate, or hide any step that does not speed it up.
What this lesson answers
- how to define first value for onboarding
- what setup steps should be removed from onboarding
- how to shorten the path to activation
Notes
A first-value journey is the shortest path from “I just created an account” to “I got the thing I came for.” For a developer tool, that might be seeing a first successful API call. For a project management app, it might be inviting a teammate and completing one shared task. The important point is that first value is defined from the user’s point of view, not from the company’s setup checklist.
The mental model is a production request path. Every screen, form field, email verification, integration, empty dashboard, permission prompt, and tutorial is a hop before the user gets a useful response.
Common questions
- What is a first-value journey?
- A first-value journey is the shortest route from a new account to a useful outcome the user recognises. For a developer tool, that could be a successful API call. For a collaboration product, it could be completing shared work with a teammate. The definition must come from the user’s goal, not the company’s internal checklist.
- How do I decide what to cut from onboarding?
- List every action, screen, prompt, verification, integration and configuration step before the user reaches value. For each one, ask whether it helps that value happen sooner. If it does not, remove it, move it later, fill it automatically, or keep it out of the user’s way until it is actually needed.
- Why is teaching the whole product during onboarding a mistake?
- New users are not trying to learn the full system yet. They are deciding whether the product deserves more attention. Tours, profile completion, optional preferences and broad feature education often create delay before proof. Onboarding should get the user to a concrete result first, then introduce more capability when it becomes relevant.
Short definition: what is Designing the First-Value Journey?