Customer Journey Map and brand touchpoints

What to optimize first: prioritization instead of evenly distributed attention

The standard mistake is to distribute resources equally among all touchpoints: slightly improve the website, slightly — email, slightly — packaging. This is a waste of budget. Any customer journey has points with disproportionate influence on emotions and decisions — they are called moments of truth. This is not the same as a regular touchpoint. A standard touchpoint — viewing a product card or opening an email — influences the path linearly. A moment of truth — canceling an order, denying a return, payment failure — influences non-linearly: one bad interaction here outweighs ten good ones elsewhere.

A practical example — the story of Birkenstock. Analysis of behavior showed that customers were leaving the site in mass not because of price or design, but because of misunderstanding the sizing chart. Formally, this is a routine touchpoint — a page with a sizing table. In fact, it was a critical moment where a significant portion of conversions was lost. The insight was incorporated into the map not as 'improve the sizing page,' but as a priority task with measurable impact on revenue.

To distinguish critical points from routine ones, it's worth evaluating each based on three parameters:

• Frequency — how often a client passes through this point;
• Emotional spread — how much the experience here can be either good or bad (neutral points are not prioritized);
• Business weight — does the point directly affect churn, repeat purchase, or NPS, rather than indirectly.

Points with high emotional spread and high business weight receive resources first, even if they are infrequent in terms of frequency.

Blind spots on the map: backstage processes and non-standard scenarios

Most maps are built on the 'happy path' — the customer comes in, chooses, pays, and receives the product. The reality is different: a significant part of the emotional contact occurs in scenarios that the team consciously or unconsciously excludes — return, complaint, cancellation of subscription, delivery delay. These are backstage processes: what happens inside the company (logistics, support service, billing) and what the customer sees only through the result — a long response, a non-working return form, refusal without explanation. These scenarios fall out of the map for a banal reason: they are difficult and unpleasant to research. The team readily draws the path to purchase and almost never — the path after a complaint. But it is precisely return or cancellation that often becomes that moment of truth that decides whether the customer will return or leave to a competitor forever.

Such scenarios need to be considered in a separate track of the map, not as a footnote to the main path. Practically, this means: building a separate branch of CJM for the 'complaint path' and 'return path', linking each backstage point to a specific internal process and owner, not just the customer's emotion.

Touchpoint, channel and device: confusion that breaks maps

The most accurate definition used by the industry: touchpoint = channel + device + task. These are not synonyms, and mixing these concepts is the reason why maps turn out incomplete.

Why this is important in practice: the 'website' channel and the 'mobile app' channel are different touchpoints, even if the task is the same (placing an order), because the experience and barriers differ. Ignoring the device, the team often fixes the desktop version of the site, while the problem actually exists only on the mobile version. Ignoring the task (task), the team confuses 'visiting the website' with a specific point of contact — and without specifying the task, it is impossible to measure what exactly needs to be improved.

What data to base the map on, if you want it to be effective

Expert evaluation is a hypothesis, not a map. A team that draws CJM exclusively based on their assumptions about the customer reproduces their own blind spots. A working map is built on three sources simultaneously: quantitative analytics (behavior, churn, heat maps), qualitative interviews (what the customer says about their emotions and barriers), and benchmarking of competitors and the category. The data shows the scale of the problem: only 52% of organizations that have CJM truly understand purchasing journeys for different audience segments — this is the largest data gap in the industry. At the same time, companies that do build maps understand the customer journey 21% better than those without maps. The 21% difference is the difference between a guess and a data-backed solution. The technological shift is also evident: 41% of companies have increased the use of analytics and AI tools for measuring journey over the past year — because manually aligning data from ten channels with real customer emotions is almost impossible.

What happens to the map after presentation: integration into task management

A map that lives in a PDF on the marketing drive is useless. The gap that is barely described in articles about CJM: how to turn map insights into tasks that go into product sprints, support KPIs, and agenda items for leadership. Companies that integrate CJM into operational processes, rather than keeping it as a one-time artifact, use the map to measure KPIs 40% of the time and bring it to leadership meetings 9% of the time. The difference is noticeable: without integration, the map is just a picture for reporting; with integration, it becomes a management tool. A practical synchronization scheme looks like this:

1. Each critical point on the map gets an owner — a specific person or department, not an abstract 'customer experience';
2. An insight from the map is translated into a task with pre/post metrics (not 'improve returns', but 'reduce return processing time from 5 to 2 days');
3. The task goes into the same tracker where product sprints and marketing live — not into a separate CX team file;
4. The map is not reviewed once a quarter just for the sake of it, but when new analytics data appears;
5. Once in 2-4 years, a full map update is conducted — such a cycle is considered a reasonable balance between relevance and the cost of repeated research.

It is no coincidence that CJM is most successfully adopted in marketing, sales, and customer service (94-96% integration in these functions) — these are the departments that first see whether the task from the map turns into a sprint or dies in presentation.

Where did CJM come from and when is it truly needed

The methodology was developed by OxfordSM company in 1998 year for the British operator Eurostar, and later it was applied in work with the British government services — that is, initially it was a tool for complex, multi-channel, emotionally charged scenarios, not only for e-commerce. Hence its strength: CJM well solves tasks where the customer journey branches, is interrupted and returns to another channel — for example, a customer starts checkout in an app, gets interrupted by a call to support and completes the purchase on the website. A map without accounting for such breaks records a single linear scenario and ignores the context that the customer expects to preserve when transitioning between channels. An investment in a map is not cheap — the average cost of CJM development is estimated at 260 000 dollars, and this is one of the reasons why 78% of organizations plan not to build a map from scratch again, but to update the existing one within two years. Meanwhile, 81% of companies consider such an investment justified: 95% of organizations with maps recorded an increase in customer satisfaction, 92% based on insights from CJM developed new products. And 79% of companies set a goal to ensure a positive experience at all touchpoints — although, as shown by the data gap in 48% of unclear segments, setting a goal and actually measuring it — are different stories.