Buyer journey

Published: 2026-09-12 · Last reviewed: 2026-09-12 · Reading edit: 2026-09-12

Your contact likes the product, but the purchase is stuck. They may still need to persuade a manager, check an integration, or work out who will run it. Mapping the buyer journey helps you see that work from their side and offer the right help at the right moment.

Map a real buying situation

Use this guide when people consume content but stall before a decision, or when a new customer repeats questions already answered during sales. Choose one situation and one account type. A first purchase, replacement and expansion can have different obstacles; do not average them into a single happy path.

Reconstruct the progression

1. Interview participants about a recent decision. Ask for the first sign of a problem, what changed, what they tried, who became involved and what delayed progress. Seek specific events and artifacts, not a tidy retrospective funnel.
2. Separate the business work from your touchpoints. “Agree a security requirement” is buyer work; “read our security page” is one possible touchpoint. The buyer may do that work through a peer or incumbent instead.
3. Add participants and disagreements. A champion may want speed while finance needs an economic case. Record who must resolve each issue and what proof they can accept.
4. Mark loops and exits. A failed evaluation can send the group back to requirements. A budget freeze can pause the purchase without making the product a poor fit. Show adoption and first value after signature.
5. Attach useful support to each obstacle. This might be a comparison, trial task, deployment guide or forwardable summary. An asset needs a specific question to answer and an owner responsible for accuracy.
6. Validate the map with another recent buyer and with customer success. Label assumptions and missing voices. Use the map to prioritize one repair, then observe whether people actually progress.

Worked example

A fictional security tool gets many successful technical trials but few purchase approvals. Interviews show that the operator can prove detection quality while the finance sponsor cannot explain what existing spend will change. Another demo does not solve that problem.

The team creates a cost-and-scope worksheet with explicit assumptions and a migration responsibility checklist. It watches whether evaluation groups reach a documented budget decision. A faster signature is welcome, but it does not by itself prove the worksheet caused the change.

Map one obstacle

Buying situation and account:
Participant and task to complete:
Trigger and current alternative:
Evidence of the obstacle, with date:
Question that must be answered:
Acceptable proof and decision owner:
Support we will provide:
Observable next step / pause / exit:
Post-purchase dependency:

Evaluate usefulness

A good map explains why a buyer is stuck and what could help. Review time spent unresolved, missing participants and repeated questions. Avoid treating a content download as agreement, or an internal CRM stage as the buyer’s actual state. Keep the previous version when the map changes so teams can distinguish learning from a renamed process.

Try it with your own work

Pick one live conversation. Ask your contact, “What needs to happen inside your team before you can decide?” Draw the steps they describe and mark the one that needs help.

Sources and scope

• Nielsen Norman Group: Journey Mapping 101 describes journey maps around an actor, scenario, phases, actions and opportunities. This guide adapts that approach to multi-participant B2B decisions.

The example is fictional; any numbers illustrate the method rather than a benchmark. Adapt the worksheet to your own situation.

What to read next

Identify the buying committee and connect the map to lifecycle stages.

Chapter guide · All playbooks

---

Copyright © 2026 Ivan Xu. All rights reserved. See the copyright and reuse terms.

Canonical source: github.com/weilun88313/B2B-Playbook