Reading0%
Journey Management · Apr 21, 2026

Managing Is Narrative Work, Emotional Work, Alignment Work

The word "management" in journey management is frequently misread as a technical or administrative role — someone who tracks progress, runs syncs, and ensures delivery. These activ

SJ60 3 min Customer Journey, Journey Management
Journey Management
SCQA dossierSJ60
Situation The word "management" in journey management is frequently misread as a technical or administrative role — someone who tracks progress, runs syncs, and ensures delivery. These activ
Complication The old frame no longer explains the work cleanly.
Question Managing Is Narrative Work, Emotional Work, Alignment Work
Answer The word "management" in journey management is frequently misread as a technical or administrative role — someone who tracks progress, runs syncs, and ensures delivery. These activ

The word "management" in journey management is frequently misread as a technical or administrative role — someone who tracks progress, runs syncs, and ensures delivery. These activities are part of it. But they are not its core.

The core of journey management is the work that does not appear in any job description: the continuous act of holding a shared story about what the organization is trying to achieve for its customers, and ensuring that story remains credible, connected to evidence, and alive in the conversations where decisions are made.

Narrative Work

Organizations run on stories. The way a product team understands what it is building, the way a leadership team justifies an investment, the way a cross-functional group holds together around a shared direction — all of these depend on a narrative that makes sense of the work.

In journey management, that narrative is the customer experience story: where we are, where we need to get to, what we are doing about it, and why it matters. This story does not maintain itself. It needs to be actively constructed, continuously updated with new evidence, and regularly re-told to the people who need to hear it.

The journey orchestrator is, among other things, the keeper and re-teller of this story. They know which customer insights are most current, which solutions are showing the most promise, and which experience scores have improved since the last review. They make this knowledge accessible — not through information dumps, but through the kind of purposeful communication that connects evidence to strategy in a way that decision-makers can act on.

"Managing is a real workload. It is narrative work, emotional work, alignment work. It is expectation-setting, friction-identification, and the continual practice of ensuring the journey does not collapse into a pile of disconnected projects."

Emotional Work

Journey management involves navigating the emotional terrain of organizational change — which is more complex and less predictable than any methodology can capture.

When a team's emerging solution is merged into a Big Solution led by a different team, someone may feel that their work has been absorbed rather than credited. The orchestrator's job is to ensure that does not happen — to make the contribution visible, the credit explicit, and the combined direction genuinely better than what either team could achieve separately.

When a Big Solution stalls because a key decision-maker is unavailable for three months, the orchestrator maintains momentum with the teams that are waiting — keeping them oriented toward the customer experience logic that motivated the work, rather than allowing the pause to erode commitment.

When discovery reveals a customer pain that implicates a team that has been resistant to journey work, the orchestrator finds the framing that makes the insight useful rather than threatening — the way of presenting the finding that creates a problem worth solving together rather than a performance gap worth defending against.

Alignment Work

The practical output of all this narrative and emotional labor is alignment — the condition in which multiple teams are working toward the same customer experience outcome without requiring continuous coordination overhead to maintain that direction.

Alignment is not agreement. Teams can disagree about methods, technical approaches, and prioritization while remaining aligned on the customer experience outcome they are working toward. What alignment prevents is the drift that happens when teams lose sight of the shared purpose and begin optimizing for their local objectives.

The journey orchestrator maintains alignment not through authority but through presence: being the person who sees across all the Big Solutions, who knows where the experience scores stand, who can connect a team's daily work to the journey stage and customer outcome that justify it. That presence is the soft authority that makes journey management possible in organizations that cannot be changed by mandate.


Back to Writing