Sample frameDay 194·Operations · Time

Good morning. Your delivery time is mostly not work. It's the gaps between the work.

Operations.

The Value-Add Ratio

6 min read·Apply by lunch

The question

Take the last job you delivered and separate the hours somebody was genuinely working on it from the days it spent waiting on a desk, in an inbox, or behind something more urgent — which of those two numbers is bigger? The waiting. It always is.

The idea

Draw a process map, then run a timeline along the bottom of it in two rows. The upper row carries the elapsed time between steps, usually counted in days. The lower row carries the time the unit is genuinely being worked on, usually counted in seconds or minutes. Total each row and you'll have two numbers with almost nothing to do with each other, and that pair of totals is the entire point of the exercise. The instruction manual for it appeared in 1998, when Mike Rother and John Shook published Learning to See through the Lean Enterprise Institute — less a book than a workbook, a set of instructions for drawing one diagram in pencil while standing where the work happens. Shook had spent eleven years inside Toyota and became the first American to hold a manager's post there in Japan; Toyota didn't call the technique value stream mapping at all, but material and information flow mapping, and used it without ceremony. The map itself is unremarkable. What earns its place is that two-row timeline. The trap is what most teams do next: they see the tiny working number, conclude the answer is to work faster, and spend a year shaving minutes off a process whose customers are waiting weeks. Delivery time was never in that row.

The framework

01
Time it twice, on the same walk.
One pass down the flow you've already mapped, two clocks running. The first records touch time: how long a person or a machine is actually doing something to the unit at each step, which is nearly always shorter than anyone guesses. The second records elapsed time: the clock between one step finishing and the next beginning. Both come off the same walk. Take them on separate days and you'll end up with two sets of figures nobody trusts and a meeting about methodology.
02
Why does the answer come out so small?
Divide total touch time by total elapsed time — in the same units, which is where most people quietly go wrong — and write it as a percentage. For most businesses the answer lands somewhere in low single figures, and the first reaction is disbelief followed by an argument about whether the measurement was fair. It was. The point of the number isn't precision, it's proportion: the overwhelming majority of what your customer experiences as your delivery time is your work sitting still. Put it on one dated line and keep it. Every improvement afterwards gets measured against it.
03
The three piles a gap can land in.
Some waits are batching: the unit is finished but held until enough others accumulate to justify moving them. Some are queueing: the next person or machine is busy with something else. Some are pure handover, where the work is done and simply sits until someone notices — the largest pile in most service businesses and by far the cheapest to fix. Attack that third pile first. It doesn't need investment, reorganisation or permission, only somebody made responsible for the moment of transfer.
04
Improvement here is measured in days removed.
Once the ratio is on the wall it changes what counts as a win. A change that takes three minutes out of a step and leaves the queue untouched isn't visible to the customer, however good it looks in a report; a change that removes a two-day wait shortens your delivery time by two days. So set the target on the elapsed row and leave the touch row alone. Then re-walk the flow each quarter, because waits creep back quietly, one reasonable exception at a time.

Members only · 4 principles + template + AI mentor

364 more frameworks are waiting.

The Value-Add Ratio is Day 1 of 365. One framework every morning for a year — across strategy, sales, negotiation, leadership, and more.

$1 /day

Billed $365/yr · cancel any time

365 frameworks

12 topics · templates · AI mentor

Reserve your place — $365/yr →

One payment a year · the whole library · no auto-renewal.

More Operations frameworks

All 24 operations frameworks →