Most value stream mapping exercises produce a beautiful poster and zero behaviour change. A facilitator runs a full-day workshop, the team covers a wall in sticky notes, photos get taken, the wall comes down — and three months later, the process runs exactly the same way it did before. The artefact lives on a shared drive. The improvement doesn't happen.
We've run value stream mapping (VSM) sessions across services, operations, finance, and marketing teams. The format below is deliberately short — 90 minutes — and the outputs are deliberately small. The goal isn't a complete map. The goal is three real commitments the room is willing to own. That's a higher bar than it sounds, and it's the bar that produces results.
Before the room (30 minutes of prep)
The session fails or succeeds before anyone walks in. Two pieces of prep matter most:
- Pick one process, end to end.“Customer onboarding from signed contract to first invoice.” Not “onboarding.” The clearer the start and end events, the easier the room's job becomes.
- Invite the right people.Every step in the process needs someone in the room who does it. Not someone who manages it. Someone who does it. If you can't fill that requirement, postpone the workshop.
Six to eight people is the right size. Twelve is a town hall. Four is a meeting with diagrams. The Goldilocks zone is whoever actually touches the process.
The 90-minute agenda
Minute 0–10: frame the problem
Open with one sentence that names the start event, the end event, and the symptom. “Customer onboarding takes us six weeks from signed contract to first invoice, and we'd like to get it under three.” Write it on the board and leave it there.
Set one explicit rule for the session: no solutions until minute 70. The single failure mode of every VSM workshop is the group leaping to fixes before they understand the process. Naming the rule out loud lets the facilitator hold it.
Minute 10–35: map the current state (the boxes)
Each participant gets a stack of sticky notes. They write one process step per note — just the verb-noun pair (“send contract,” “create CRM record,” “trigger onboarding email”). The facilitator arranges them left to right in rough order on the wall.
Resist the urge to make it pretty. Resist the urge to be complete. Twenty boxes is plenty for a 90-minute session. If you have more than 30, you've picked too large a scope.
Minute 35–55: add the time data (the magic step)
Under each box, add two numbers:
- Touch time — how long the step actually takes someone to do (minutes or hours).
- Wait time — how long the work sits between this step and the next one (hours or days).
Don't aim for precision. Order-of-magnitude estimates are enough. The point isn't the exact numbers — it's the ratio. When the room totals up the touch time and the wait time at the end, the answer is almost always startling: a process that takes six weeks of clock time often contains six hours of actual work. People remember that ratio.
Minute 55–70: mark the pain
Each participant gets three red dot stickers. Place them on the steps that are the most painful, the most error-prone, or the most likely to slip. No discussion yet — just stick the dots.
Step back. Where the red dots cluster is where the conversation needs to live. Almost without exception, the cluster is on handoffs, approvals, and wait times — not on the work itself. The room sees that pattern without needing to be told.
Minute 70–85: propose three changes (and only three)
Open the floor for solutions. Limit the room to three: one quick fix, one structural change, one experiment. The constraint forces the group to prioritise.
For each change, write:
- What we'll change.
- Who owns it.
- By when it'll happen.
- How we'll know it worked.
If a proposed change doesn't have a clear owner in the room, kill it. Unowned commitments don't ship.
Minute 85–90: close cleanly
Read the three commitments aloud. Confirm each owner explicitly. Schedule a 30-minute follow-up in four weeks to review progress. End on time. Letting the session drift past 90 minutes is a tell that the next one will too.
What to do with the map afterwards
The map itself is a snapshot, not a living document. Photograph it and put it in the project channel — but don't spend a week rebuilding it in Miro. The map served its purpose the moment the commitments landed. Treat it as scaffolding.
The one piece of follow-up that matters: the four-week review. Show up, ask each owner what happened, and decide whether to keep, adjust, or kill each change. That review is where the workshop actually pays back. Skip it and the commitments quietly evaporate.
The five facilitation mistakes that ruin the session
- Letting people skip steps. Every step the room glosses over is the one that turns out to be the bottleneck.
- Letting one person dominate. The senior person in the room knows the official process. The junior person knows the actual one. Protect the junior voice.
- Allowing “ideally we do X” statements.The map is current state, not desired state. If “ideally” enters a sentence, redirect to what really happens.
- Solving in the middle. The 70-minute rule exists for a reason. Hold it.
- Not closing on commitments. A workshop without named owners and dates is a meeting with diagrams.
When to use a longer format
Some processes genuinely don't fit into 90 minutes — anything that crosses three or more business functions, or anything where regulatory steps add real complexity. For those, use the same structure but stretch it across two sessions: one for current-state mapping, one for commitments a week later. Avoid the all-day marathon. The marginal value past three hours drops sharply, and the room's commitment quality drops with it.
The honest bottom line
Value stream mapping isn't the deliverable. The deliverable is three small things the team agreed to change. A 90-minute room with the right people, a clear scope, and a hard stop on solutions until the data is on the wall produces those three things more reliably than a full day with consultants. Run it monthly on the processes that hurt most, and the cumulative effect is more than any single large transformation programme delivers.