Examples are illustrative unless otherwise attributed.
What is first value?
First value is the earliest useful result a customer recognizes from your product. Define it for one audience and task, map the steps to reach it, and distinguish necessary setup from the outcome itself. The definition should be checked with customers, not chosen only because an event is easy to track.
Start with the win—not the welcome email
A person arrives with a job in mind. They might need to prepare a report, organize a client project, or send a proposal. Your team sees a new account. The person sees a task that still needs doing.
That difference is where I would start an onboarding review. A completed registration can tell you that someone entered the experience. It cannot, by itself, tell you whether the experience delivered on its promise. Before choosing a campaign, define the first useful result in language the customer would recognize.
For the hypothetical project-planning product used throughout this guide, a candidate first win is: “I have a usable plan for my next client project.” Creating an account, choosing an avatar, and inviting colleagues might support that result. None is automatically the result itself.
This is an illustrative working example, not a client case study. The map and proposed changes below are prompts for investigation. They are not evidence of a conversion increase.
The goal isn’t just to get the signup. It’s to help someone get their first win.
Choose one person, one situation, one promise
A map labeled “all new customers” can hide the decisions you need to make. An invited teammate and the person who purchased the tool may enter with different permissions, expectations, and levels of knowledge. Give each meaningfully different situation its own path.
For this example, choose a solo consultant starting a new client project. They have arrived from a page promising a simpler project plan. They have no workspace, no imported data, and no colleague available to help them set up.
Write the promise beside the scenario. A later step may be easy to use yet still disappoint if it produces something different from what the arrival page suggested. Review the promise and destination together.
NN/G’s journey-mapping guide is useful background on specifying an actor, scenario, phases, and opportunities. Our exercise applies that idea to a narrowly defined first-use journey; it is not a reproduction of their template.
Walk the journey that actually exists
Use a safe test account with the permissions of the person you are studying. Start at the actual acquisition page. Follow its call to action, the confirmation message, the first session, any required setup, and the first output. Include errors and recovery paths, not just the version that works perfectly.
Record what you can directly observe. “The first screen asks for a team invitation before showing a project example” is an observation. “Customers are unmotivated” is an interpretation—and not a useful specification for a fix.
For each transition, note what the person knows, what they need, what the business asks of them, and what happens if they cannot comply. Where research is missing, write “unknown” instead of supplying an emotion on their behalf.
| Customer moment | Question to investigate | Possible support |
|---|---|---|
| Arrives from a promise | Does the next screen preserve that promise? | A specific explanation of the first useful task. |
| Reaches an empty workspace | Is the first action recognizable? | A sample project or task-focused starting point. |
| Meets a prerequisite | Do they have the access or information required? | An explanation, safe alternative, or recovery route. |
| Creates the first output | Can they judge whether it is useful? | A clear review and editing step. |
| Returns later | Can they continue from their actual state? | A direct link to unfinished work—not a generic dashboard. |
Mark the gap between evidence and a guess
An event report might show where people stop. A session observation might reveal what someone tried. A support message might explain a constraint. Each contributes a different kind of evidence; none should quietly stand in for the others.
Keep a simple record beside the map: what was observed, which source supports it, when it happened, and what remains uncertain. Do not use a participant’s comment to claim that every customer behaves the same way.
Suppose a participant pauses on the empty workspace. An unclear starting point is one explanation. Missing project information, lack of permission, or uncertainty about whether the tool fits could also explain the pause. The next step is to distinguish those possibilities—not to announce that the welcome sequence is broken.
A visible usability issue can still be worth addressing before a large analytics project is complete. Be clear about the basis for that decision. “We clarified the first action and tested comprehension” is a different claim from “we increased activation.”
Design the message and its destination together
For the example consultant, a useful message might say: “Your project space is ready. Start with a simple client plan, then change the tasks to fit your work.” Its destination should make that action possible with the person’s current permissions.
Before implementing, specify eligibility, the triggering condition, the relevant delay, and the stop conditions. A person who has already made the plan should not keep receiving instructions to make the first one. A person who cannot proceed needs help with the obstacle—not a more enthusiastic reminder.
Test late events, repeat events, returning users, and someone who completes the task while a message is queued. Also check the experience after an expired session or on a small screen. These are proposed QA cases; the precise rules depend on the system you use.
Use the Lifecycle Message Brief to document the logic before asking someone to build it. The automation diagram should explain the customer decision, not just the order of sends.
Choose one change you can explain
Imagine replacing a generic “Welcome to your workspace” panel with a project example and a clearly labeled starting action. Keep the proposed change small enough that you can explain what it addresses and identify anything else that changed at the same time.
Define the candidate observation before launch: eligible new accounts producing the agreed usable project output within a specified window. Decide whether the unit is a person or an account. Identify the event, denominator, exclusions, and where the event is only an imperfect proxy for usefulness.
For illustration only, 12 completions among 60 eligible accounts is 20%. A later rate does not prove that your intervention caused the difference. Traffic, eligibility, product releases, and observation windows could all differ. Keep the underlying counts and those caveats visible.
Choose guardrails as well: errors, confusion, support workload, and people producing an output they do not understand. A faster setup is not an improvement if it takes control away or creates another problem downstream.
Leave with a decision, an owner, and a review point
The map is not the final deliverable. The useful output is an agreement about what to do next. Write the decision, the evidence behind it, the person responsible, the implementation boundary, and when the team will review what happened.
That next step may be a prototype, an event-tracking correction, a short customer conversation, or a targeted interface change. It does not have to be a complete new onboarding program. Sometimes the most responsible decision is to gather a missing piece of evidence first.
Start with the companion First-Value Journey Worksheet. Fill in what you know, mark what you do not, and choose one useful question for your team. For an example of the same thinking applied to a screen, open The empty dashboard that asks too much.
A signup begins the relationship. Your next job is to make the promise useful.
Sources & further reading
Nielsen Norman Group — Journey Mapping 101 ↗Background references are distinguished from our original examples and proposed exercises.


