Day 310 of the Daily · Operations

Common Cause, Special Cause

5 min read · 4 principles · apply it by lunch

Morning. Most of what your dashboard flags as a problem this week is just the process breathing.

The question

The last time a weekly number moved the wrong way, did anyone check whether that figure had ever sat outside its ordinary range before you changed something — or did you adjust, watch the next week land back where it always lands, and quietly credit the change you’d made?

The idea

Walter Shewhart was a physicist in Western Electric’s inspection engineering department when, on 16 May 1924, he sent his superior a one-page memo with a sketch on it. The sketch was the first control chart. The group moved to Bell Telephone Laboratories the following year, and Shewhart set the argument out properly in Economic Control of Quality of Manufactured Product (1931). It turns on a single division: every process produces two kinds of variation. Chance causes are the ordinary jitter of a process working exactly as built — there’s nothing in any one of them worth investigating, and they’ll all be back tomorrow. Assignable causes are real events: a new supplier, a worn tool, one person doing the job differently this week. You’ll know the pair by their later names, common cause and special cause. What made Shewhart unusual is that he didn’t treat any of this as a statistical question. He treated it as an economic one — the chart exists to stop you spending money on the wrong kind of variation. React to an ordinary point as though it were an event and you tamper: you adjust a stable process in response to noise, and the adjustment contributes variation of its own. The trap is that tampering looks exactly like management. Something moved, you responded, it came back.

In the Daily · 4 principles and a template

Common Cause, Special Cause is Day 310 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 318 · Operations

The Cause Map

When something last went wrong badly enough to need a written explanation — the missed shipment, the wrong invoice, the error a client found before you did — how many candidate causes were on the table before the room settled on one, and how many questions deep did the settled one go? If the honest answers are one and three, you didn’t investigate. You confirmed the first idea that fitted.

See the framework →
Day 327 · Operations

Poka-Yoke

When the same small mistake turned up for the third time — the blank field, the wrong file attached, the discount applied to the wrong line — did you change the step so it couldn’t happen again, or send a message asking everyone to take more care? The message has already worn off.

See the framework →
Day 336 · Operations

Standard Work

Take the process your business runs most often — the onboarding, the client handover, the monthly close — and ask whether two of your people, working it on the same day, would produce the same thing in the same order. If the honest answer is no, you haven’t got a process; you’ve got several, and you’re paying to run all of them.

See the framework →
Day 345 · Operations

Process Capability

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.

See the framework →