Day 345 of the Daily · Operations

Process Capability

5 min read · 4 principles · apply it by lunch

Good morning. Your average is fine. Your customer never experiences the average.

The question

You promise your customers something with a number in it — delivery in five days, a reply within the hour, an error rate under one per cent — so what proportion of the time do you actually hit it, measured rather than felt? If the only figure you’ve ever reported is the mean, the answer is that you don’t know, and neither does the customer who has been quietly counting the misses.

The idea

In 1986 Bill Smith, an engineer at Motorola, made an argument that grew into Six Sigma: products needing rework on the line failed disproportionately early in the customer’s hands, so the defects you catch internally forecast the ones the customer will find. Acting on that requires a way to set how much your process varies against how much variation the customer will tolerate, and the arithmetic is disarmingly simple. Put two widths side by side: the span your process ordinarily covers, which is six standard deviations of its own results, and the tolerance your customer will actually accept. Divide the second by the first and you have Cp. If Cp is 1.0 the two are the same width, your specification sits exactly three standard deviations either side of centre, and roughly 2,700 units in every million fall outside it — and that assumes perfect centring, which no process has. Plenty of industrial customers won’t accept anything under 1.33. You don’t need the full statistics to use any of this: count your last thirty results, count how many fell outside the line the customer will actually take, and you’ve got the same number in cruder form — which is more than most businesses can produce for any promise they’ve already signed.

In the Daily · 4 principles and a template

Process Capability is Day 345 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 354 · Operations

The Focused Factory

If you asked the five people who run your delivery — the ones who decide what gets pulled forward when the week is full — what this operation is optimised for above everything else, would you get one answer or five? Ask them separately this morning, and write the replies down before you compare them. The spread across those replies is a fair measure of how much focus you’ve got left.

See the framework →
Day 363 · Operations

The Operations Operating Review

Without opening a spreadsheet, can you say where your operation is limited this week, how long one order takes from yes to delivered, and what fraction of that time anybody was actually working on it? Most people get the first right, guess the second, and have never measured the third. It’s the third that pays for the other two.

See the framework →
Day 042 · Operations

Theory of Constraints

Where does work visibly queue in your business — the unanswered quotes, the approval that waits on one person, the step everything routes through — and if you can name that point without looking anything up, why haven’t you pointed this week’s effort straight at it?

See the framework →
Day 044 · Operations

The Retrospective

When something went wrong for your team last month — the slipped deadline, the messy launch, the handover that dropped — did anything about how you work actually change, or did everyone privately note it and move on; and if you can already name the problem that will recur, why haven’t you scheduled the hour that fixes it?

See the framework →