Define the journey boundary
Choose a buying situation rather than “the entire customer experience.” You might map a first purchase of a technical service from the triggering incident to an agreed pilot. A renewal or replacement decision may follow a different path and deserve its own map.
State whose perspective the map represents. A user and a procurement team can encounter different steps, even within the same account. Nielsen Norman Group recommends customer research and observation to avoid a journey that reflects how the organization wishes buyers behaved.
Map decisions, not only touchpoints
| Stage of the situation | Buyer decision | Evidence need | Possible obstacle |
|---|---|---|---|
| Problem recognition | Is this worth addressing? | Consequences and current workaround | Other priorities |
| Investigation | Which approaches are credible? | Alternatives and practical tradeoffs | Unclear terminology |
| Evaluation | Can this work here? | Fit, risk and implementation detail | Missing stakeholder |
| Approval | Is the commitment justified? | Commercial and operational case | Budget or authority |
| Adoption | Can we make the change succeed? | Ownership and operating instructions | Capacity or handoff |
These are illustrative stages. Buyers can return to earlier questions, pause or involve new stakeholders. Do not force evidence into a linear funnel when the actual process is iterative.
Combine sources carefully
Use interviews to reconstruct the sequence, records to identify observed interactions, and direct observation where possible to understand workarounds. A web analytics event confirms an instrumented action; it does not by itself establish the buyer’s motivation. Label inferred motivations and seek corroboration.
Preserve disagreements between roles. If sales believes pricing is the obstacle but buyers describe uncertainty about implementation, that is a research question. Do not resolve it by selecting the version that is easiest to address.
Choose one improvement
For each friction point, identify an owner and a testable change. A hypothetical team might replace a generic demo invitation with a technical readiness discussion when buyers cannot assess integration effort. Specify what would count as a useful result, such as more complete evaluations or fewer unresolved implementation questions.
Keep the map operational
Add links to the evidence and assets used at each stage. Record a preparation date and review trigger. A map becomes stale when product capabilities, buying roles or approval requirements change. Its value lies in helping people improve the next interaction, not in producing a more elaborate diagram.