The Bottleneck Should Never Go to Lunch

In manufacturing, productivity gains are often associated with investment.

Sometimes all of that is necessary.

But sometimes the fastest improvement comes from something much simpler:

I was once invited to a production facility to give recommendations on how to increase output. The target was modest but important: at least 5% more production.

The process was straightforward. A linear chain of seven machines. Each machine performed one operation and passed the part to the next stage. Raw material entered at one end. Finished product came out at the other.

After walking through the workshop, I met with the company leadership and the shop floor management team.

They asked the expected question:

My answer surprised them.

“I need to know only one thing.”

Then I asked:

There was a pause.

The question sounded almost irrelevant. They expected a discussion about equipment capacity, investment, technical upgrades, or staffing levels.

After a moment, the production manager answered:

“Yes. Everyone goes to lunch at the same time.”

That was enough.

I said:

During the walkthrough, I had noticed a buildup of semi-finished parts before the third machine.

That detail mattered.

Inventory before a process step is not just inventory. Very often, it is a signal. It tells you where the flow is waiting. It shows where the system is constrained.

In this case, the third machine was the bottleneck.

And in any production system, the bottleneck is not just one machine among many.

If the bottleneck stops, the system loses capacity that cannot be recovered by making other machines work faster. The machines before it continue to feed the queue. The machines after it eventually start waiting.

The entire system follows the constraint.

So the solution was simple:

The operators were working on similar machines. That meant the operator from the second station could temporarily cover the third machine while the third operator was having lunch.

When the third operator returned, the second operator could take their own break.

Just one operational rule:

The effect was immediate.

A 45-minute lunch break inside an 8-hour shift looks small when viewed as a local scheduling detail.

But if that 45 minutes belongs to the constraint, it becomes system-level lost capacity.

Keeping the bottleneck running added productive time exactly where it mattered. And because the bottleneck defined the throughput of the whole line, the improvement translated directly into additional output.

This is one of the most important lessons in operational excellence:

Improving a non-bottleneck may make one local area look better, but it will not necessarily increase total output.

Improving the bottleneck changes the performance of the entire system.

The same logic applies far beyond manufacturing.

Many organizations try to optimize everything at once.

But systems do not improve equally from equal effort.

The first question should always be:

The second question should be:

Of course, this was not the end of the work. Once one bottleneck is relieved, another constraint may appear somewhere else. That is normal. A production system is dynamic. Improvement is not a one-time event. It is a discipline of continuous observation, adjustment, and learning.

But the principle remains the same.

Sometimes productivity is not hidden in a new machine.

Sometimes it is hidden in a lunch schedule.

First published on zavodovskii.com by Dmitrii Zavodovskii.