Journey map

A journey map spreads the whole experience across one page so the emotional dips are visible next to the actions that cause them. The map below traces a freelance designer from first hearing about Ledger through recurring monthly use. Five stages, three rows: what the user does, what the user thinks, how the user feels.

Why the emotion curve does the work

Any team can list actions in order. The map earns its keep by making the emotional dips visible next to the actions that cause them. The curve above dips sharply at onboarding when the app asks for bank details, and peaks at first invoice when the user realises the send action actually worked. Those two points are where design attention returns the most.

Reading top to bottom

Actions in the top row, thoughts in italics below them, emotion at the bottom. Every column is one stage. Reading down a single column tells you the whole scene at that moment. Reading across a row tells you the arc of one dimension. Journey maps that only show one row are missing the point.

The opportunity strip

The red-orange line at the bottom names a single, testable intervention tied to the biggest emotional dip. One opportunity per map. Journey maps that end in a wall of recommendations get read once and archived. A map that produces one clear next step gets referenced in every product review for the next quarter.

Where I gather the raw material

The thoughts row is the hardest to fill honestly. Product teams tend to write what they wish the user was thinking. Actual quotes come from interviews (five people is usually enough), support tickets, and unmoderated usability testing. If the italics on a journey map do not sound like something a person would actually say, the map is fiction dressed up as research.

Design decisions

• Emotion as a curve, not a scale. A single continuous line reads faster than five separate happy-sad ratings.
• Italic thoughts, direct quotes. Italics signal the row is verbatim. Non-italic sentences would read as authorial summary.
• Warm cream ground. Same palette as the other UX artifacts so the family is legible.
• One opportunity call-out. Concentrates the argument on the single change that would move the curve.

The stack

Tool

FigJam for the working session, Figma for the delivered artifact.

Research

Five moderated interviews, ten support tickets, one usability round.

Cadence

Revisited every quarter or after any major flow change.