The Lobbi Delivery Team
Operational Systems Engineering
Pick any process at any company and time it two ways. Time the actual work — keystrokes, conversations, decisions, approvals. Then time the customer's experience from the moment they ask to the moment they're done.
You will find a ratio of about 1:10. Sometimes 1:50. The work takes minutes; the experience takes days.
That ratio is the value stream map's whole reason for existing.
What the lens answers
A value stream map (VSM) is a Lean tool that came out of the Toyota Production System and was popularized for service work by Mike Rother and John Shook in Learning to See. It looks like a horizontally-arranged process diagram with each step boxed, and three numbers underneath each box:
— Process time (PT): how long the actual work takes when someone is actively doing it. — Lead time (LT): how long the step takes from when work arrives in the queue to when it leaves. — Percent complete and accurate (PCA): what fraction of the work that arrives downstream is correct enough to use without going back.
You then add up the PTs across the diagram, and add up the LTs, and compare. The gap is the waste.
Why the gap is so big
For most knowledge work, the gap is huge because work spends most of its life waiting:
— Waiting for an approval from someone whose calendar is full. — Waiting in a queue because the person handling it is doing something else. — Waiting for someone to read an email. — Waiting for a system to sync. — Waiting for the customer to respond to a clarification request that wouldn't have been needed if the request was clearer in the first place.
None of that wait time shows up in a swimlane diagram. The swimlane shows that step 4 hands off to step 5. It does not show that the average gap between 4 and 5 is 27 hours, of which 22 hours are pure queue and 4 hours are someone reading a Slack thread to figure out what step 4 actually meant.
VSM is the lens that draws the wait.
What "good" looks like
We tell teams to expect three patterns the first time they VSM a process:
1. The work is way smaller than they thought. A process the team complains takes 'all week' usually has 90 minutes of actual work in it.
2. The biggest queue is upstream of the most senior approver. Approvals stack because senior people are over-allocated. The fix is rarely "approve faster" — it's "approve fewer things."
3. PCA falls off a cliff at one specific handoff. That's where the rework loop is. That handoff usually has a missing artifact, a missing field, or a missing instruction.
Optimizing the work without first surfacing the wait gets you nothing the customer can feel.
How we use VSM inside an engagement
We don't VSM until the swimlane is stable. Steps and lanes have to settle before adding numbers — otherwise you're measuring a process that won't exist next week.
Once it's stable, the team measures actual times in production for two weeks. Not estimated times. Not 'how long it should take' times. Wall-clock measurements. The numbers are usually shocking, which is the point. After that, the place to start improving is the longest stretch of pure wait.
Most knowledge work is 90% wait. The work isn't slow — the wait is invisible. Value stream maps draw the invisible.
Sources
Topic clusters