Înapoi la Perspective

Perspectivă din 20 august 2026

English

Everyone treats "bottleneck" like a dirty word in business. It usually means someone or something is blocking the flow while everyone else waits. Frustrated. Looking for someone to blame.

But what if a bottleneck is neither good nor bad? What if it's simply real: something that exists in your system, whether you like it or not. The job is to map it, understand it, and work with it.

I'm currently reading "The Goal" by Eliyahu Goldratt (decades late to this one, I know), and it reframed how I think about this completely. He treats the bottleneck as a fact of the system: a constraint every business has, and the real lever for improving the whole operation.

His argument, roughly:

- Optimize the bottleneck itself. Look at the process, the tools, the framework it runs on right now, and find where it's wasting capacity. - Optimize everything feeding into it. Look at what happens upstream that adds delay or extra load before work even reaches the constraint. - Unload the bottleneck of anything that doesn't need to go through it. Free it up to work only on what it can deliver.

The goal (no pun intended!) is capacity: room for the bottleneck to do the one thing nothing else in the system can do.

So next time you spot a bottleneck in your company, resist the urge to judge it as good or bad. It's simply real, something to handle well for the sake of the whole operation.

What's the bottleneck in your business that everyone's been pointing fingers at?

Several weathered padlocks attached to a metal railing.