Home › The Garage › Takt time
Lean

Takt time & flow

Takt time is the heartbeat of demand — how often you must finish one unit to keep up with the customer. Compare it to how long each step actually takes, and your bottlenecks name themselves.

By LeanBean · Updated November 2026 · 5 min read
What's in this guide
  1. What takt time is
  2. How to calculate it
  3. Takt vs cycle time
  4. Designing for flow
  5. Common questions
Takt = 60s Step 1 · 40s Step 2 · 50s Step 3 · 85s Step 4 · 35s Step 3 rises above the takt line — it can’t keep up with demand, so it sets the pace of the whole line.
Any step above the takt line is a bottleneck: it cannot meet demand, so it caps the whole flow.

What takt time is

Takt time is the pace at which you must complete one unit to exactly meet customer demand — the rhythm the process has to keep. If customers need 480 units a day and you work 480 productive minutes, takt time is one minute: finish one unit a minute and you keep up, no faster, no slower. It converts demand into a target rate every step can be measured against.

How to calculate it

Takt time = available working time ÷ customer demand, over the same period. Use net available time — subtract breaks and planned stops — and real demand, not capacity. The result is a time per unit: “one every 90 seconds,” “one every four hours.” It is deliberately set by the customer, not by how fast the process happens to run.

Takt vs cycle time

Cycle time is how long a step actually takes; takt time is how long it is allowed to take to keep up with demand. Line the cycle times of every step against the takt line and the picture is immediate: any step whose cycle time exceeds takt cannot keep up — it is the bottleneck, and it sets the pace of the whole process. Steps well under takt may be over-resourced.

Designing for flow

Balance the line to the beat
Smooth flow means every step works close to takt — not far above (it can’t keep up) and not far below (it’s waiting or overproducing). The work of improvement is to rebalance: shift tasks between steps, cut the bottleneck’s cycle time, and aim for one-piece flow paced to demand rather than batches racing and queuing. Takt gives you the number to balance against.

Describe a process. Get the whole analysis.

LeanBean turns a plain-language description of any process into a professional map — with Lean waste, SIPOC, design-thinking, AI-readiness and capacity analysis built in, and a Transformation Coach that sequences the fixes. Free to start.

Build your first map free →

The Garage — a community of practice

The Garage is where Lean, process and AI-readiness practitioners learn in the open — short lessons, real examples, and a place to compare notes. Join the community: follow along, try it on your own work, and share what you find.

Common questions

How do you calculate takt time?

Divide the net available working time by customer demand for the same period. For example, 450 productive minutes and 90 units of demand gives a takt time of 5 minutes — one unit must be completed every five minutes to keep pace.

What is the difference between takt time and cycle time?

Takt time is the rate demand requires; cycle time is the rate a step actually achieves. If a step’s cycle time is longer than takt, it cannot keep up and becomes the bottleneck that paces the whole process.

What happens if cycle time is faster than takt?

That step has spare capacity. Running it faster than takt just produces ahead of demand — overproduction — which creates inventory and cost. The aim is to balance each step close to takt, not to maximise every step.

Does takt time apply to office or service work?

Yes. Any process with recurring demand has a takt — claims to settle per day, patients to see per session. It gives service teams the same demand-paced target that manufacturing lines use to balance work.

Related guides: Process cycle efficiency · Kanban & pull systems · Capacity modelling