Reveal typical experiences the customers have over time when interacting with your brand. You need to get behind your users goal (not your business one)
We’ve all seen them. The "Monolith Maps."
Those five-foot-long, beautifully designed customer journey maps that live in glass frames or buried in a Confluence page. They are detailed, they are colourful, and often they are useless.
The problem with traditional journey mapping is that it rewards completion over clarity. We spend weeks documenting every touchpoint, every emotion, and every possible "path to purchase." But as researchers and product teams, our job isn't to be cartographers of the obvious. Our job is to be hunters of risk.
If you have a tight timeline, a huge ask, and a project shrouded in mystery, you don’t need a traditional map. You need a Lean Journey Map.
The biggest mistake we make in research is asking users what they "usually" do.
When you ask for the "usual," people give you the "ideal." They describe the person they wish they were, or the process they think the company wants them to follow. It’s a fantasy.
A Lean Journey Map starts with a reality check. We don't map the "ideal scenario." We ask: "Tell me about the last time you actually did this." By focusing on a specific, recent memory, we bypass the polished business process maps and get to the messy reality. We find the workarounds, the manual "hacks," and the moments where the user actually steps away from our product to do something else entirely.
I recently worked with a product team in a high-speed discovery phase. They had a path they wanted the users to take, but they were flying blind on where the actual friction lived.
We used the Lean Journey Map to bridge the gap.
We looked for the "hidden" steps. The things that don't show up in your analytics. Like when a user takes a screenshot of a page to "save it for later" or spends twenty minutes on Pinterest before even visiting your site.
These aren't just actions; they are windows into their psychology. When a user screenshots your app instead of using your "Save" button, they are telling you something vital about their trust, their habits, or your UI. A Lean Journey Map forces you to ask why that trigger exists, giving you a focused area to spend your research budget.
I like to explain it this way: Imagine you’re looking at a field after a rainstorm. All the puddles look the same from a distance. You’re trying to decide which one to jump into.
Just because a puddle is right in front of you doesn't mean it’s the most important one. Some are shallow; some are six feet deep.
The Lean Journey Map is how you find the deep puddles. It’s about identifying where your assumptions fall along the journey and pinpointing where you have the highest risk and the least amount of data.
If you’re running this in a workshop, don’t start from zero. The "Secret Sauce" is mapping assumptions. I always give the team a little homework: "Bring me every assumption you have about this journey before we start." If we map those assumptions against the real steps, the "truth" appears almost instantly.
When you’re mapping, you’ll inevitably hit a wall where a user (or stakeholder) says a step is "fine," even when you know from prior conversations it's not.
Don't push back; pivot. I like to use two specific prompts to break the seal:
1. If you were training someone on this step, what would you tell them to look out for?
2. What part of this do you think would be the trickiest to explain to a total beginner?
This moves them from "defensive user" to "expert mentor," and the friction points start pouring out.
What do you do once the map is done? You dot vote.
You cannot research twenty assumptions in a week. The goal of this map is to kill the "monolith" research plan. Instead of one giant, slow-moving project, the Lean Journey Map allows you to write "One-Page Plans"—short, sharp questions that can be answered in weekly sprints.
The biggest pitfall? Perfectionism.
Stop trying to make your map a piece of art. It’s a diagram. It’s a living document. It’s a tool to get the ideas out of your system and into the light. If it’s polished, you’re less likely to change it when you’re proven wrong.
The Lean Journey Map isn't about detail; it's about focus. It’s about making sure that when you finally "jump into the puddle," it’s the one that actually matters for the business and the user.
So, stop over-designing your maps. Grab a recent example, map the messy reality, and find out where you’re actually guessing.
Now you're ready to plan, 1 plan per question. Keep the scale small.
Draw Next card