Day 212 of the Daily · Operations

The Seven Wastes

5 min read · 4 principles · apply it by lunch

Nobody in your business is idle. That isn’t the same thing as everybody doing work a customer would agree to fund.

The question

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.

The idea

Taiichi Ohno joined Toyota Motor Company in 1943 as a shop-floor supervisor and spent the next thirty-five years rebuilding how the company built cars, rising eventually to executive vice president. His book, Toyota Production System: Beyond Large-Scale Production, appeared in Japanese in 1978 and in English a decade later, and its most portable idea is also its smallest: a list. Muda is Japanese for waste, and Ohno sorted it into seven kinds — overproduction, waiting, transport, over-processing, inventory, motion and defects. He was explicit that the first is the worst, because overproduction hides all the others: making more than is needed, sooner than it’s needed, manufactures things to store, things to move, things to check, and enough visible activity to conceal the lot. What the list really does is turn an argument into an inspection. Saying the team should be more efficient invites opinion and goes nowhere. Saying that a particular report is over-processing, and nobody has read it since March, names one thing one person can stop doing on Friday. The eighth waste you’ll see on posters — unused talent — is a later Western addition, not Ohno’s.

In the Daily · 4 principles and a template

The Seven Wastes is Day 212 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 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 →
Day 239 · Operations

Takt Time

Ask whoever runs your busiest repeated process how often a finished one has to come off the end for the business to keep the promises it’s already made — could they give you a number, or would they tell you they’re going as fast as they can? One of those is a rate you can staff to. The other is an apology.

See the framework →
Day 248 · Operations

The Level Schedule

Look at what your team actually started in each of the last four weeks — not what was sold, what was released into the work — and how far apart are the biggest and the smallest of those weeks? If you don’t have the numbers to hand, the shape is almost certainly your order book’s, because that’s the default: whatever arrives gets released, and the swing gets paid for by everyone standing behind you.

See the framework →