Customer journey: mapping what actually happens, not what should

A customer journey is the sequence somebody actually passes through from first hearing of you to buying again — and the gap between that sequence and the one described in an internal diagram is where most lost business sits. The useful version is built from evidence rather than from a workshop, because what a team believes happens and what the records show are rarely the same thing.

What a customer journey map shows

• The real stages, named for what the customer is doing rather than for what your team calls it internally.
• What triggers each move forward, which is usually something you did or failed to do rather than a decision they made alone.
• How long each stage takes in practice, taken from dates rather than from impressions.
• Where people drop out, which is the most valuable part and the part most maps omit.
• Who inside your organisation owns each stage, because the handovers between owners are where enquiries die.
• What the customer is trying to achieve at each point, which is not the same as what you want them to do next.

Building it from evidence

1. Take the last thirty customers and write down what actually happened, in order, with dates.
2. Do the same for ten enquiries that went nowhere, since the journey that failed is more instructive than the one that worked.
3. Mark every point where somebody waited on you, and how long.
4. Ask five recent customers what nearly stopped them buying; the answer is reliably something nobody internally considered a stage.
5. Draw it only after that, and keep it to one page.

The gaps matter more than the stages

Most journey work decorates the boxes and ignores the arrows. But customers are not lost during a stage, they are lost between stages — in the four days before a quote arrived, in the silence after a demo, in the week nobody followed up because the person who owned it was away. Measuring the gaps is less satisfying than describing the stages and almost always identifies the one change worth making, which is usually a shorter wait rather than a better page.

Be suspicious of any map where the stages all take similar time and nothing goes wrong. That is a description of policy, not of what happens — a real journey has one stage that takes three weeks for no good reason, and finding it is the whole point of the exercise.

Using it rather than framing it

A journey map earns its place only if something changes because of it: a response time shortened, a handover assigned, a step removed. Pick the single worst gap, fix that, and redraw in six months. Maps that get laminated and hung up are a sign the exercise became a deliverable instead of a diagnosis, and the second version is the one that matters because it can be compared with the first.

Ettex CRM holds the dates that make this measurable — when an enquiry arrived, when it was answered, when it moved on — so the gaps can be counted rather than estimated. Who owns each stage belongs beside those dates, since an unowned stage is where the waiting happens.