Gumshoe · Method reference

Journey mapping

Visualize a person's end-to-end experience across steps, emotions, and touchpoints to find pain and opportunity.

Conceptual illustration of journey mapping.
Effort
High
Participants
Not required
Remote friendly
Yes
Evidence / output
Direct user

What it is

A visualization of the stages a person goes through to accomplish a goal, mapping their actions, thoughts, emotions, and touchpoints across time to reveal pain points and opportunities.

When to use it

During Synthesize, once you understand the experience well enough to chart it end to end.

Why (value)

Builds shared understanding of the whole experience, exposes emotional lows and gaps between channels, and prioritizes where to intervene.

How to run it

  1. Define the persona and the journey scope (goal, start, end).
  2. Lay out the stages and the user’s actions at each.
  3. Add thoughts, emotions, and touchpoints per stage.
  4. Mark pain points and moments that matter.
  5. Identify opportunities and owners.

Inputs and outputs

  • Inputs: Research on the experience, a target persona, a defined scope.
  • Outputs: A journey map with pain points and prioritized opportunities.

Time and effort

High. Meaningful maps require real research plus synthesis.

Evidence and limitations

Only as credible as its inputs, a map built from research reflects reality; one built from assumption is a hypothesis diagram. Distinguish current-state (evidence) from future-state (design intent). See Evidence and limitations.

Tips and pitfalls

  • Ground it in research; do not map an imagined journey as fact.
  • Include emotion, it is where opportunity often hides.
  • Separate current-state from future-state maps.

Variations

Current-state vs. future-state, experience maps, service blueprints (adds backstage).

Need help choosing and applying a method?

Gumshoe helps teams connect research, collaborative workshops and service design to the decisions they need to make.

Discuss your project with Gumshoe Explore Gumshoe services

Sources and further reading

Experience orchestration extension (2026-11-07)

Define the user’s goal beyond the immediate interface interaction. Capture meaningful moments, channel transitions, actor changes, workarounds, and recovery. Attach source and confidence to important elements; leave unsupported thoughts and feelings unknown. Separate current-state evidence, desired future experience, opportunities, and solution ideas. Pair consequential gaps with owners and an outcome measure.

Adapted from Risdon and Quattlebaum, Orchestrating Experiences (Rosenfeld Media, 2018), especially chapters 2–11.

Explore related methods

  • Service blueprinting — Extend a journey map with the backstage people, systems, and processes that deliver each frontstage moment.
  • Scenarios — Narrate how a specific person accomplishes a goal so the team designs for realistic context.
  • Personas — Represent key user types as memorable archetypes to keep design decisions grounded in real needs.

A general practice reference. This page does not establish that a method was used on a particular client project or that an outcome was measured.