Customer Journey Mapping: What to Measure at Each Touchpoint

The customer does not see your departments

Customer journey mapping helps when each team reports a healthy process and the buyer still has a difficult experience. Marketing sees a completed enquiry. Sales sees an assigned lead. Service sees a new request. The customer may see repeated questions, unexplained delays and no clear next step. Mapping a specific journey makes those handovers visible so the business can decide what to change.

Choose one actor and a real scenario

NN/g describes a journey map as a visual account of the process a person follows to accomplish a goal, built around an actor and scenario.¹ Define both before starting. “All customers, from awareness to loyalty” is usually too broad for useful investigation. A first-time buyer evaluating a technical product has a different journey from an existing customer seeking a replacement.

Specify the starting circumstance and the end condition. An industrial RFQ journey might begin when an engineer needs a suitable component and end when a valid quotation is received. A customer support journey might begin with a problem and end with resolution. The scope should include the relevant channels and handovers, even when they sit outside the website. The real task provides the boundary, not the organisation chart. Our guide to RACE framework covers the next question.

Gather evidence beyond the workshop

Bring together customer interviews, observation, service records, sales notes and digital event data appropriate to the task. Ask people to describe recent experiences. Where suitable, observe the work or collect diary accounts. A team workshop can assemble existing knowledge and hypotheses, but it should not be presented as a researched customer journey if no customer evidence supports it.

Keep the distinction between observed and assumed steps. Mark gaps plainly. The available analytics may show a form submission without revealing an earlier distributor call. A support record may explain a complaint but miss customers who quietly leave. The map can accommodate those limits. It becomes more useful when it identifies the missing evidence than when it supplies a confident emotion for every stage.

Map actions questions and handovers

For each phase, record what the person does, what they need to know and where friction appears. Include relevant thoughts or feelings only when research supports them. A buyer may feel uncertain because compatibility is unclear; the useful design response is then clearer suitability evidence, not a decorative reassurance banner. Connect the finding to an accountable change.

Customer journey mapping should also expose handovers. Who receives the enquiry? What information arrives? Does the customer know what will happen next? Which team owns exceptions? A service blueprint can extend the work into backstage processes when that detail is needed. Keep the customer-facing journey readable, and do not bury its main finding under every internal administrative step. If that is your next question, read our guide to jobs to be done framework.

Choose metrics for the actual task

Measure stage completion, drop-off, elapsed time, repeat contacts and task success where relevant. Define eligible cases and starting events. Pair operational measures with comprehension or customer feedback when the question requires it. A quicker process is not necessarily better if the buyer receives an incomplete or inaccurate answer.

• Stage completion uses eligible cases that reach a defined end event divided by eligible cases entering that stage. Keep timestamps and cohort rules consistent.
• Drop-off identifies a missing later action within a defined window. Investigate context before assuming that every absence indicates confusion or dissatisfaction.
• Task success should state the goal, eligibility, assistance rules and conditions. Small usability samples reveal issues rather than universal performance rates.
• Elapsed time needs a clear clock and handling of weekends or working hours. Report the rule rather than comparing incompatible service measures.
• Repeat contacts and customer effort can expose broken handovers. Pair those signals with resolution quality and direct feedback before deciding what to change.

Use the map to change the page and process together

Website copy can explain requirements and the next step, while the operational process ensures the promise is kept. If the enquiry form asks for technical details, explain why they are needed. If documents can be supplied later, say so. Keep essential instructions visible and accessible. Do not make a customer open several accordions to understand how to obtain help.

Assign the handover changes to the people who own the systems and work. Marketing can improve the page, but it cannot solve an unowned CRM queue through copy alone. Agree the confirmation message, routing logic, response responsibilities and exception path. Test the complete journey with realistic cases before publishing the new invitation. Include mobile and assisted routes where customers actually use them.

Review a journey after the changes run

Follow the defined cohort long enough to observe the relevant outcome. Check whether missing-information cases declined, whether tasks became easier and whether the next stage improved. Talk to customers and staff about new friction. A form can become shorter while creating more follow-up work; a stricter form can improve data completeness while blocking suitable buyers. The outcome needs context.

Keep the map dated and owned. Update material changes in the service, channel or customer task. There is no need to redraw the entire journey every week, but an old map can become misleading when the product, buying route or support process changes. Use it as a practical decision record: what was difficult, what the business changed and what evidence now shows. CAC payback period is explained in a separate guide.

Questions people ask

Discuss the work your team needs next

Bring Quiamo the handover customers repeatedly complain about, along with the page, form and internal process involved. A customer journey mapping engagement can examine the actual task, clarify the evidence and connect content changes with operational responsibilities. Begin with one scenario whose outcome matters. A focused map that improves a real experience is more valuable than a comprehensive mural that leaves every team working as before. Explore our brand strategy engagement to discuss the scope and deliverables.

Sources

1. NN/g Journey Mapping 101Journey maps focus on an actor scenario phases actions thoughts and emotions.

Worked examples on this page are fictional and labelled. Search phrases and figures from external sources are cited; nothing here describes a Quiamo client result.