Omni Core · Object

Customer Journey Mapping

The whole relationship as the customer experiences it — including the parts after the purchase, where most of it happens and least of it is designed.

The term

What it is

The Market Core covers the journey to a purchase. This object covers the journey the customer actually lives in: onboarding, use, support, renewal and departure. The second is longer, less designed and more predictive of whether they stay.

A map is only useful if it is drawn from the customer’s side. An internal process map with customer labels attached describes what the organisation does, which is a different and much better-understood thing.

Most experiences are not designed at all. They are the accumulated consequence of decisions made in separate functions, each reasonable, none of which considered the sequence a customer passes through.

Why it earns a place

What goes wrong without it

01

The experience is assembled from decisions nobody coordinated

Marketing sets an expectation, sales makes a commitment, operations delivers, support repairs. Each is competent and the sequence is nobody’s.

02

A few moments carry disproportionate weight

Research on how experiences are remembered is consistent: the peak and the end dominate. Spreading effort evenly across a journey wastes most of it.

03

The handovers are where it breaks

Within a function the experience is usually fine. Between functions the customer repeats themselves, and that is where the memorable failures occur.

One level in

The modules within customer journey mapping

Four working areas. The first draws what actually happens, the second finds where it matters, the third addresses where it breaks, and the fourth changes it.

  1. Mapping the journey

    What the customer actually experiences, in order, from their side — including the waiting, the repetition and the parts the organisation never sees.

    Learn
  2. Moments that matter

    The few points that disproportionately determine how the whole is remembered, identified rather than assumed.

    Learn
  3. Channel handovers

    What happens when a customer moves between channels or functions, which is where context is lost and where the experience most often fails.

    Learn
  4. Redesign

    Changing the journey deliberately, with the internal changes that requires. The half that makes mapping worth doing.

    Learn

Across the framework

What it touches

  • Market CoreThe journey to purchase is mapped there; this object begins where that one ends.
  • Business CoreMost journey failures are process failures, and the process belongs to whoever runs it.
  • Brand CoreThe promise is kept or broken here, at the touchpoints rather than in the wording.
  • Data CoreJourney measurement requires instrumentation designed for it rather than assembled afterwards.

Beyond the framework

Models worth knowing here

The Omnigoal says where this belongs and what it touches. It does not tell you how to think about it — other people have done that, and done it well. These are theirs.

  1. The service blueprint

    G. Lynn Shostack · 1984

    Map what the customer experiences and everything behind the counter that has to happen for it, on the same diagram.

    A line of visibility separates what the customer sees from the work that supports it, with support processes below that again. Its diagnostic power comes from that line: most service failures are not failures of the visible step but of something underneath it that nobody had drawn.

    Reach for it when
    When a journey map records feelings and touchpoints but nothing about what produces them.
    Where it stops
    It is detailed and slow to produce, and it describes the service as designed. What is actually done in the branch on a Friday afternoon is frequently something else.

    G. Lynn Shostack, “Designing Services That Deliver”, Harvard Business Review, 1984.

  2. Moments of truth

    Jan Carlzon · 1987

    A company is judged in the brief encounters between a customer and a member of staff, and nowhere else.

    Written from the turnaround of an airline, it argued that the impression of a company is created in millions of small interactions, none of which a manager attends. The management conclusion follows directly: authority has to sit with the person in the encounter, because the encounter is over long before anyone can be asked.

    Reach for it when
    When mapping a journey and deciding which points deserve real investment, and when frontline staff have responsibility without authority.
    Where it stops
    It comes from a high-contact service in the 1980s. Where most encounters are with software rather than people, the moments still exist but the conclusion about authority has to be rebuilt.

    Jan Carlzon, Moments of Truth, Ballinger, 1987.

These are other people’s models, named here so you can go to the source and use them properly. The Omnigoal is not affiliated with their authors and is not endorsed by them; nothing of theirs is reproduced here — no canvas, no diagram, no wording. Each is described in our own words, with the originator credited, because the framework is a place to put thinking, not a replacement for the people who did it. Model names and trademarks belong to their respective owners and are used here only to refer to the work itself.

Every model in the framework, and where each one belongs

Draw the map from the customer’s side. An internal process map with customer labels describes something else entirely.