The Three Frictions That Break Journey Work

Journey management fails for predictable reasons. The same patterns appear across organizations of different sizes, industries, and maturity levels — patterns that become visible once you have seen them enough times. Three of these patterns are structural. They do not arise from individual failures or poor execution; they arise from the fundamental mismatches between how journey work is designed and how organizations actually function.

Understanding them before they appear is the difference between a journey management practice that survives disruption and one that collapses the moment the organizational terrain shifts.

Friction One: Insight vs. Politics

Customer research produces facts about the customer experience. Organizations produce facts about internal power. These two fact systems regularly contradict each other.

A discovery cycle reveals that customers are abandoning the product at the activation stage because the onboarding sequence is confusing. The team responsible for onboarding has been saying for two years that the problem is customer expectations, not product design. The journey map now carries evidence that challenges this position directly. The question is not whether the evidence is true — it almost certainly is. The question is whether the team responsible will act on it, or whether the political investment in their existing position will be stronger than the customer evidence pointing against it.

This is the insight-vs.-politics friction. It appears whenever evidence threatens someone's narrative about their own work. The orchestrator's job is not to force the issue — that rarely works and usually creates lasting resistance. It is to find the framing that makes the evidence useful rather than threatening: a problem worth solving together, not a performance gap worth defending against.

"Customer evidence doesn't move organizations on its own. It moves organizations when the people who hold the evidence find the way to present it that makes acting on it the rational choice."

Friction Two: Map vs. Operation

Journey maps are representations. Operations are realities. The gap between them is constant, and it creates a specific frustration for practitioners who have spent significant effort building a map that teams then struggle to connect to their daily work.

A map shows the customer moving through awareness, activation, acquisition, retention, revenue, and referral. The product team works in sprints. The sprint doesn't correspond to a journey stage — it corresponds to a feature set or a bug list. The marketing team works in campaigns. The campaign doesn't correspond to a journey stage — it corresponds to a channel, a quarter, and a budget cycle. The customer service team works in tickets. Tickets don't correspond to journey stages — they correspond to problem categories.

This is the map-vs.-operation friction. Journey maps are designed for strategic orientation; organizational operations are designed for tactical delivery. The map that lives at the right altitude for strategic decision-making tends to be too abstract to be directly actionable for teams doing the daily work.

The resolution is not to make maps more detailed — that typically makes them more unwieldy without making them more useful. It is to develop the translation discipline: helping teams see how their operational work connects to the journey stage and customer outcome it ultimately serves.

Friction Three: User vs. Organization

Organizations are designed to optimize internal processes. Customers are trying to accomplish something that matters to them. These two orientations are not inherently incompatible, but they diverge constantly in practice.

The checkout flow is designed to minimize fraud risk, not to make the purchase experience frictionless. The support ticket system is designed to resolve tickets efficiently, not to make the customer feel heard. The account renewal process is designed to maintain subscription revenue, not to give the customer a clear picture of the value they have received. Each of these represents a local optimization — rational from the organization's internal perspective, costly from the customer's experience perspective.

Journey management is the structural response to this friction. By making the customer's progression through the lifecycle visible and measurable, it creates a forcing function: decisions that improve internal process at the customer's expense become visible as such, and the experience score provides a common metric for the cost of those decisions.

The three frictions are permanent features of the terrain, not problems to be solved once and archived. Managing them is the ongoing work of the orchestrator — which is why journey management is less a methodology and more a practice: something you do continuously, not something you complete.