Designing the System Behind the Experience
Over the years, I’ve had the chance to implement journey maps, service blueprints, and varying degrees of journey management across organizations of all shapes and sizes. From early experiments to enterprise-wide transformation efforts, I’ve seen firsthand what it takes to keep journeys alive—not just as artifacts, but as strategic tools that shape decisions, structures, and services.
The organizations that do it well invest not just in the visible outputs, but in the scaffolding that makes those outputs meaningful, actionable, and durable.
That’s what led me to create the Journey Management Stack—a way to visualize the components that, together, form the foundation for sustained journey management. It’s both a guide and a conversation starter, helping teams assess where they are and where they want to grow.
Here’s a breakdown of each element:
Journey Map
What it is: The heart of the stack. A journey map visualizes the stages a customer moves through—along with what they’re doing, thinking, and feeling along the way. Multiple maps may represent different journeys, and nested maps may detail different levels of zoom.
Why it matters: It shifts the lens from inside-out to outside-in. It’s not about how the business sees itself; it’s about how the customer experiences it.
Structure
What it is: The way your organization is aligned to support journeys.
Why it matters: Some companies go as far as restructuring around journeys to improve planning, accountability, and culture. This only works if the journey structure is designed to last—flexible enough to evolve, stable enough to anchor real change.
Service Blueprints
What it is: A detailed view of how the experience is delivered—across people, processes, products, and systems.
Why it matters: Blueprints provide operational clarity. They’re essential for coordinating work, diagnosing breakdowns, and guiding changes to org design or tech infrastructure.
Experience Vision
What it is: A clear picture of the desired future state.
Why it matters: An organization can’t all move toward something it can’t see. A compelling vision, made tangible through storytelling and prototypes, inspires teams and informs prioritization. When the vision shifts, the stack shifts with it.
Data
What it is: The signals that show how journeys are performing—from across the organization and directly from your customers. This includes both quantitative data (e.g., usage, conversion, NPS) and qualitative insight (e.g., interviews, feedback, ethnographic research).
Why it matters: Data informs the journey and grounds decision-making. When teams have access to meaningful input—both behavioral and emotional—they can see the whole story, spot opportunities, and respond with clarity and care.
Metrics
What it is: Key indicators that the journey is performing as expected and well.
Why it matters: Good journey management metrics focus both strategy and real-time problem solving. Additionally, they keep you honest about whether you’re actually improving the experience.
Training
What it is: The ongoing development of skills, knowledge, and confidence needed to practice journey management across the organization.
Why it matters: Even the best-designed stack is only as strong as the people using it. Training ensures teams know how to map journeys, interpret metrics, use tools, and make decisions through a customer-centered lens. It builds shared language, demystifies the work, and enables adoption at scale.
Tools
What it is: Platforms and systems that help you manage all of the above.
Why it matters: Managing journeys at scale requires more than sticky notes. Whether it’s purpose-built tools from Adobe, Smaply, TheyDo, or adapted internal systems, you need infrastructure that fits your organization’s needs.
People & Roles
What it is: The individuals and teams responsible for stewarding, maintaining, and activating the journey work.
Why it matters: Journeys don’t manage themselves. Clearly defined roles—like journey owners, experience leads, and cross-functional coordinators—help ensure that accountability is distributed, decisions are made, and the work stays alive.
Processes
What it is: The routines and rituals that keep the work moving—review cycles, update cadences, handoffs, governance forums.
Why it matters: Without processes, even the best journey map will collect dust. With them, journey management becomes part of how the organization operates.
Change Enablement
What it is: The support systems that help people and teams adopt journey management as a way of working. This includes coaching, internal storytelling, pilot programs, and building comfort with ambiguity and iteration.
Why it matters: Sustained change isn’t just about delivering something new—it’s about making the organization ready and able to work differently. Change enablement turns friction into momentum.
Governance
What it is: Oversight that ensures consistency, quality, and longevity.
Why it matters: Governance keeps the system healthy. It turns a set of practices into an enduring capability. Done well, it sustains the work even as teams, tools, and priorities shift.
Why it all matters
Journey management is more than a map or a tool—it’s a system of integrated parts. These parts may take different shapes, operate at different levels of maturity, and evolve over time. But in some form, each one influences your ability to manage journeys effectively.
That might sound overwhelming. But like anything meaningful and complex, you can start small. Make progress in one area of the stack. Just don’t forget: every part is connected. Improvements in one layer will have ripple effects—good or bad—through the rest.
When supported by the right structure, tools, and behaviors, journey management becomes a force for alignment and momentum. This stack helps make that real. Use it to take stock. Use it to spark conversations. And most of all, use it to make the customer experience more intentional—and more impactful.
How does your organization stack up?