You can't fix an experience you don't fully understand.
Most organizations have a theory about where the customer experience breaks down. Sales has one. Support has another. Product has a third. Every team sees the part of the journey they're responsible for, and nobody has a view of the whole thing.
Journey Mapping is a research engagement that builds that view. I conduct original research across your customer or operational journey, map what's actually happening at every stage, and show you where the real friction is, not where your internal teams think it is.
The output isn't a workshop artifact built on assumptions. It's a map built on evidence.
Who this is for
This is a good fit for operations and product executives who are about to make a significant investment in improving the customer or operational experience and need an honest picture of the current state before they design the future one. It's also the right starting point when customer complaints are rising and every internal team has a different theory about why, or when growth has created operational complexity that nobody has mapped end-to-end.
If you've just taken a new leadership role and want an outside read on how things actually work, this is where you start. And if you're working through a merger, acquisition, or major service redesign, a research-based journey map is the foundation everything else gets built on.
The industries where this work tends to land most naturally: healthcare, financial services, logistics, telecom, and any company with a complex multi-touchpoint service model. If the phrase "service design" is part of how your organization talks about this work, this engagement is what that requires.
How it works
The engagement starts by scoping the journey: where it begins, where it ends, who the actors are (customers, employees, partners), and what decisions the map needs to inform. That scoping conversation also surfaces the riskiest assumptions — the things your organization thinks it knows about the experience that may or may not be true.
From there I design and conduct the research. Depending on the journey, that might be customer interviews, employee interviews, observation and shadowing, contextual inquiry in the field, or some combination. I go where the experience actually happens, not just where it's documented.
Synthesis produces the map: a clear picture of what's happening at every stage of the journey, where customers or employees hit friction, what's causing it, and where the biggest opportunities are. The final readout includes specific recommendations prioritized by impact, not just a comprehensive inventory of everything that's broken.
The deliverable is designed to be used: as a foundation for a transformation program, as a shared artifact that aligns cross-functional teams, or as a brief for a design or engineering team that needs to know what to build.
What you get
A research-based map of the end-to-end customer or operational experience, built from real data rather than internal assumptions. A clear picture of where the experience is breaking down, why it's happening, and what to prioritize. A shared artifact that gives cross-functional teams a common picture to work from. And specific recommendations your team can act on.
About the Journey Mapping engagement
What is research-based journey mapping?
Research-based journey mapping is the process of conducting original customer or employee research — interviews, observation, contextual inquiry — and using that data to build an accurate map of the end-to-end experience. Unlike workshop-based journey mapping, which is built from internal assumptions, research-based mapping reflects what customers or employees actually experience rather than what internal teams believe they experience.
How is journey mapping different from discovery research?
Discovery research is focused on understanding who you're building for and what they need before you build something. Journey mapping is focused on the end-to-end experience after a product or service already exists: where it breaks down, why, and what needs to change. They answer different questions and are often used in sequence.
How long does a journey mapping engagement take?
A focused single-audience journey mapping engagement typically takes six to eight weeks. Multi-audience or ecosystem-level engagements run longer — sometimes three to six months depending on the complexity of the journey and the number of customer or employee groups involved.
Who typically commissions journey mapping research?
COOs, CPOs, VPs of Customer Experience, and operations leaders most commonly commission journey mapping research. It's often triggered by rising customer complaints, a planned technology investment or service redesign, a new leadership role, or a merger where two operational models need to be understood before they can be combined.
What is the difference between journey mapping and service blueprinting?
A journey map documents what a customer experiences across a series of interactions: their actions, thoughts, and pain points at each stage. A service blueprint goes deeper, mapping the internal processes, employee actions, and systems that support that customer experience behind the scenes. Journey mapping research often produces both deliverables, since you can't design a better customer experience without understanding the operational layer behind it.