Value Stream Mapping: How the Session Works

This series keeps referring to one technique as where the money hides: the value stream map. The should I use AI article introduced it, the bottleneck worksheet is its pocket version, and every use case article assumes you have aimed with it. So the final entry in the series gives the technique the full treatment: what VSM is, how the session runs, and the moment that happens in every single one. And a promise while we are here: a full session with a real business, on camera, whiteboard and all, is coming to this page later.

What a value stream map is

VSM comes from lean manufacturing, and I will admit the bias openly, this is my mechanical engineering upbringing showing. You take one value stream, the path from a customer wanting something to having it, and you draw every step on a wall: the work steps, the handoffs, the systems touched, and critically, the queues between them. Then you put two numbers under everything, touch time, the minutes of actual work, and wait time, the hours or days the job sits. That is the whole technique. Its power is that businesses run on an invisible process everyone assumes everyone else can see, and the map makes it visible, arguable, and fixable.

How the session runs

The room. The people who actually do the work, not just the owner, per the team article, they know where the bodies are buried, and being asked is the beginning of adoption. Whiteboard, sticky notes, two hours, phones down.

The walk through. We follow one real, recent job through the business, start to finish, in embarrassing detail. Not the official process, the actual one, including "then it waits in the ute" and "then Sharon re types it." The stickies go up, the queues get drawn, the numbers go under each step, argued to the nearest half day.

The moment. It happens in every session without exception. We total the two rows and the room goes quiet: the touch time is a few hours, the elapsed time is weeks. Something like four hours of actual work taking nineteen days to travel through the business. Nobody believes it until it is their own numbers on their own wall, and then nobody unsees it. That silence is the most valuable ten seconds in this entire series, because everything else, the funnel, the bottleneck, the AI targets, becomes obvious from that wall.

The aim. We circle the constraint, apply the squeeze first principle from the bottleneck article, and only then ask where AI belongs, at which point the answer is usually staring at us, drawn in whiteboard marker, ranked by wait time.

Run your own

The filmed session will show the craft, but do not wait for it, the bottleneck worksheet article is the self serve version, and a rough map argued over a pizza beats a perfect map never drawn. One warning from experience: map what happens, not what should happen. The gap between those two is the entire finding, and defensiveness is the only real enemy in the room.

That closes the series as planned. The resources page will keep growing from here, and if one of these articles helped you aim AI at your own business, it did its job.