Day 239 of the Daily · Operations

Takt Time

5 min read · 4 principles · apply it by lunch

Morning. ‘Faster’ isn’t an instruction. A rate is.

The question

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.

The idea

Takt is German for beat — the word for what a conductor keeps. It reached Japanese industry from German aircraft plants of the 1930s, where airframes were moved between stations at a fixed interval, and Toyota later built its entire rhythm on it. Yasuhiro Monden, a Japanese professor of management accounting, set the practice out for English readers in Toyota Production System (1983), five years before Taiichi Ohno’s own account of the system was translated. The arithmetic is trivial: take the working time genuinely available in a period, divide it by the customer demand inside that same period, and you have the interval at which a finished unit has to appear. Four hundred and eighty minutes, sixty orders, one every eight minutes. That single number is the difference between an exhortation and a specification. ‘We need to move faster’ can’t be staffed, scheduled or argued with. ‘One every eight minutes’ tells you how many people the work needs, which of your steps sit above the beat, and roughly when in the day things will start going wrong — and it tells you all of that before anyone’s worked a shift.

In the Daily · 4 principles and a template

Takt Time is Day 239 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 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 →
Day 257 · Operations

Batch Size and Changeover

Pick the thing your operation does in batches — the Thursday invoice run, the fortnightly release, the print run, the monthly board pack — and ask why it’s that size rather than half of it: can you give a reason that isn’t simply that switching over is a nuisance nobody wants to do twice? If not, you’ve been paying for that nuisance in flow time every week since, and never once priced it.

See the framework →
Day 266 · Operations

Pull and the WIP Limit

Count the pieces of work your team has open right now — the half-drafted, the in-review, the waiting-on-a-client, the one you’d have to check the board to remember — then count the people, and ask whether the first number is more than double the second. If it is, you already know why everything takes so long. The queue isn’t in front of your team; it’s inside it.

See the framework →
Day 273 · Operations

The Buffer Choice

When demand for your business spikes next month — the week everyone calls at once, the order that lands at three times the usual size — which of the three absorbs it: stock you’re already holding, capacity you’ve deliberately left idle, or your customer’s patience? For most businesses it’s the third, and nobody chose it; it simply happened, and the customer paid the bill.

See the framework →