Day 194 of the Daily · Operations

The Value-Add Ratio

6 min read · 4 principles · apply it by lunch

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

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.

In the Daily · 4 principles and a template

The Value-Add Ratio is Day 194 of 365.

In the Daily, each of its four principles is explained in full, with a one-page template to apply it the same day. A new framework arrives every morning at 7am for a year, across all fifteen courses of the FutureMBA curriculum.

$29 a month · cancel any time · 7-day money-back guarantee

More from Operations

The next four in the course.

All 24 Operations frameworks
Day 203 · Operations

The Service Blueprint

Think of the last complaint that reached you personally — the thing that arrived late, or wrong, or twice. Was the failure inside a step somebody owns, or in the handover between two people who’d each done their own part correctly? If it’s the handover, it belongs to nobody. Nothing in your business is currently pointed at it, and it will happen again this month.

See the framework →
Day 212 · Operations

The Seven Wastes

Take the busiest hour of your week — the floor, the inbox, the board, wherever the work actually happens. Of everything going on in it, how much would survive if the customer had to approve each item separately, knowing they were paying for it? You already know it isn’t most of it. The useful question is which of seven kinds the rest turns out to be.

See the framework →
Day 220 · Operations

Utilisation and Variability

Take your most loaded person or team — the one absorbing something like ninety per cent of everything they can handle. There’s a queue sitting in front of them right now. If you handed back a fifth of their capacity, how much of that queue would clear? Far more than a fifth. The relationship isn’t linear, and no amount of effort from them is going to make it so.

See the framework →
Day 229 · Operations

The Product-Process Matrix

How many jobs did your operation deliver last quarter, and how many of those needed a step your standard path doesn’t have — and was the way your work is organised designed for that pair of numbers, or for the pair you had the day you set it up? Whenever the honest answer is the second one, the gap between those two pairs is coming out of your margin every week, in a line nobody can quite locate.

See the framework →