Customer journey map template for B2B, with an evidence row that admits the guesses
A copyable B2B customer journey map template with an evidence row for every guess, a filled-in example, and the interview questions that fill each cell.
A customer journey map template is a grid, and the row that earns its place is one we added: where each cell's evidence came from. Stages run across the top; rows record what the customer does, thinks and feels, where they touch your company, and what you will change. Copy it into a spreadsheet, fill it from interviews, and keep one map per type of customer and scenario.
For the research process behind it, including whom to interview and how to test a draft, see customer journey mapping.
The blank template
Replace the stage names with the ones your customers actually go through. These are a common start for a B2B purchase.
| Row | Problem noticed | Options explored | Decision | Rollout | Renewal or expansion |
|---|---|---|---|---|---|
| Actions | |||||
| Questions and thoughts | |||||
| Feelings (high, neutral, low) | |||||
| Touchpoints with us | |||||
| Other people involved | |||||
| Evidence | |||||
| Opportunities | |||||
| Owner |
Above the table, write three lines:
- Actor: the one type of person whose journey this is.
- Scenario: the situation and goal, such as "replace a paper work-order process before the next budget is set."
- Expectations: what the actor expects the experience to be.
Most rows come from NN/g; two are ours
The rows follow the elements Nielsen Norman Group lists in Journey Mapping 101: an actor, a scenario with expectations, journey phases, the actor's actions, mindsets and emotions in each phase, and opportunities, with ownership and metrics as added context. NN/g recommends one point of view per map, so two roles with different journeys get two maps. Its example phases for a business-to-business scenario such as rolling out an internal tool are purchase, adoption, retention, expansion and advocacy.
NN/g's article on when and how to create journey maps adds touchpoints and channels, and insights and ownership, as key elements. It also says maps should be based on truth: built from qualitative research, because quantitative data alone cannot build the story.
We added two rows. Other people involved, because B2B purchases pass through several hands and the journey often stalls waiting on someone. Evidence, so the team can see which cells rest on interviews and which are guesses.
A filled-in example: a facilities team replacing paper work orders
Here is a made-up example. The actor is a facilities manager at a company with several office buildings. The scenario: replace paper and email work orders with software before next year's budget is set.
| Row | Problem noticed | Options explored | Decision | Rollout | Renewal |
|---|---|---|---|---|---|
| Actions | Loses track of a leaking-roof request; a tenant complains to the CFO | Asks two peers what they use; watches three demos | Writes a one-page case; waits for an IT security review | Loads buildings and equipment; trains technicians | Pulls response times for the annual review |
| Questions and thoughts | "How many other requests are stuck in my inbox?" | "Will my technicians actually use a phone app?" | "Can I get this approved before the budget closes?" | "Who enters all the old equipment data?" | "Can I show this was worth it?" |
| Feelings | Low | Neutral | Low (waiting) | Low, then rising | High |
| Touchpoints with us | None | Website, demo call | Security questionnaire, quote | Onboarding calls, help articles | Account review |
| Other people involved | CFO | Peers at other companies | IT security, finance | Technicians | CFO |
| Evidence | 4 of 5 interviews | 5 of 5 | 3 of 5; security step from sales notes | 2 of 5; rest is a guess | 1 of 5; guess |
| Opportunities | Content about tracking missed requests | Show a technician using the app in the demo | Send security documents before being asked | Offer to import equipment lists | Build the response-time report into the product |
| Owner | Marketing | Sales | Sales | Customer success | Product |
The evidence row shows the weak spots. Rollout and renewal rest on one or two interviews, so the next round should recruit customers who have been live for about a year.
Fill each row with questions about one real purchase
Ask each interviewee to walk through one recent purchase, stage by stage. GOV.UK's interview guidance recommends focusing on stories and real examples and following up with simple questions like "can you tell me more about...?"
- Actions: "What did you do next? Who did you talk to?"
- Questions and thoughts: "What were you trying to find out at that point?"
- Feelings: "How did that week go? What was frustrating?"
- Touchpoints: "Where did you come across us? What did you read or watch?"
- Other people: "Who else had to agree? What did they ask for?"
NN/g suggests mindsets should ideally be customer quotes, so write exact words in the thoughts row.
Three ways the template goes wrong
- Filling it in from memory. A map the team writes alone is a hypothesis. Label it and test it.
- Leaving the owner row blank. An opportunity with no owner rarely gets done.
- Polishing too early. NN/g warns against jumping to visualization before synthesis is complete. A spreadsheet the team keeps updating beats a designed poster nobody changes (or can find after the offsite).
Write "guess" first, then replace the guesses
Fill in the blank template with what you believe today, writing "guess" in the evidence row wherever you have no interview. Then book interviews for the stages with the most guesses. For people outside your customer list, Instant Expert can find people who match a description such as "facilities managers who moved from paper work orders to software in the last year." You review who it finds, it sends your invitations, and you pay for each call that gets booked. The directory page for operations professionals in facilities management is one place to start.