The Trojan Horse
Journey management is rarely bought as organizational change, but that is what it delivers. You map a journey to improve an experience, and what you expose is the operating model underneath it.
Why it matters
A journey crosses every boundary the org chart draws. The moment you follow one honestly, the silos, the misaligned incentives and the unowned seams become visible and difficult to deny. That is the real payload, and it is why journey work meets resistance that seems disproportionate to a diagram.
Run these three questions
- Who is accountable for this journey end to end, continuously, rather than for a channel or a project?
- When did we last improve a journey because of structured cross-functional analysis, rather than because of a complaint spike?
- If the person holding this left tomorrow, would the discipline survive, or would it leave with them?
Worked example
A spike in complaints triggers a mapping exercise. The team runs it well, finds the real breakpoints, presents the findings, and nothing moves. The insight has nowhere to go: the journey spans three teams and therefore belongs to none. The map was never the deliverable. What the exercise actually produced was evidence about the operating model, and the organization had no route for acting on that kind of evidence. Diagnosis without authority is just documentation.
Read the essay this came from: The Trojan Horse of Journey Management