Day 327 of the Daily · Operations

Poka-Yoke

5 min read · 4 principles · apply it by lunch

Good morning. Asking people to be careful isn’t a control. It’s a request you’ll be making again next month.

The question

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.

The idea

Shigeo Shingo was an industrial engineer who spent years teaching and consulting inside Toyota’s production system. In 1961, at Yamada Electric, he was shown a recurring fault: a small switch had two push buttons, each needing a spring underneath, and operators occasionally assembled one without its spring. The units reached the customer before anyone noticed. Shingo didn’t ask for more training. He had the operator count two springs into a small dish before starting each unit — if a spring was still in the dish afterwards, the omission announced itself immediately, at the bench, for the price of a dish. He called such devices baka-yoke, fool-proofing, until a worker objected to being called a fool, and renamed them poka-yoke, mistake-proofing. The whole method sits in Zero Quality Control: Source Inspection and the Poka-Yoke System — 1985 in Japanese, 1986 in English — and it turns on one distinction: a mistake and a defect are not the same thing. Mistakes are inevitable, because attention is finite and people are people. A defect is a mistake that got through. So you either make the mistake impossible, or you catch it at the instant it happens rather than at an inspection later, once it has collected cost. The trap is filing every recurrence under discipline — a reminder, a retraining, a word with someone — which leaves the step exactly as easy to get wrong as it was this morning.

In the Daily · 4 principles and a template

Poka-Yoke is Day 327 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 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 →
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 →