Day 318 of the Daily · Operations

The Cause Map

5 min read · 4 principles · apply it by lunch

Complicated failures rarely have one cause. They have two or three that lined up on the same morning.

The question

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.

The idea

Kaoru Ishikawa taught engineering at the University of Tokyo and spent his career inside Japan’s postwar quality movement. Explaining to engineers how a tangle of factors related to a single outcome, he drew what the world now calls the fishbone: the problem at the head, and a rib for each category of cause — machine, method, material, manpower, later widened to take in measurement and environment. He set it out for a general audience in Guide to Quality Control, which appeared in Japan in 1968 and in English a few years later. The diagram does one job extremely well. It forces breadth before depth, so a room has to populate every rib before it’s allowed to fall in love with the first plausible answer. Depth is Taiichi Ohno’s contribution: at Toyota he insisted on asking why five times, and his own worked example runs from a machine that stopped, to an overload that blew a fuse, to a bearing that wasn’t properly lubricated, to a pump that wasn’t pumping, to a worn pump shaft — and lands on a missing strainer that had been letting metal scrap into the pump. Five whys, and the answer is a part you can fit this afternoon. Stop at three and the answer is a pump: it tells you what to replace this week, and nothing about why you’ll be replacing it again in March.

In the Daily · 4 principles and a template

The Cause Map is Day 318 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 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 →
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 →