Flow vs Local Optimization

Flow Is Not Efficiency: The Dangerous Confusion That Kills Throughput

Efficiency and flow are not the same thing. In fact, the relentless pursuit of efficiency is often the single biggest destroyer of flow — and therefore of the throughput that actually matters.

5 min readMay 18, 20266 viewsKurt Corthout
Share:

The Efficiency Paradox

Every organization I have worked with shares the same assumption: if we make each part more efficient, the whole system will perform better.

It sounds logical. It is also wrong.

Efficiency measures how well a resource is utilized. Flow measures how smoothly work moves through the entire system. These are fundamentally different — and often contradictory — objectives.

When you optimize for efficiency, you fill every resource to capacity. When you optimize for flow, you deliberately maintain slack — because slack is what allows the system to absorb variation and maintain throughput.

The Highway Metaphor

Think of a highway. At 70% capacity, traffic flows smoothly. Cars move at speed. The system is productive.

At 95% capacity — which looks "efficient" on a utilization report — the highway becomes a parking lot. One small disruption cascades into gridlock. Total throughput collapses even though every lane is "fully utilized."

Organizations work the same way. When every person, every team, every resource is running at maximum utilization, the system loses its ability to absorb the inevitable variations that complex work produces.

What I See in Practice

In a recent engagement with a technology organization, I found that their average resource utilization was 97%. Management was proud of this number. "No waste," they said.

But their average project delivery time was 3.2x the estimated duration. Customer satisfaction was declining. Their best engineers were burning out.

The problem was not laziness or incompetence. The problem was that the system had no capacity to flow. Every unexpected event — a bug, a requirement change, a sick team member — created a cascade of delays because there was no buffer anywhere in the system.

The Counter-Intuitive Solution

We reduced planned utilization to 80%. Management was initially horrified.

Within three months:

  • Average delivery time dropped by 40%
  • Throughput (completed projects per quarter) increased by 25%
  • Employee satisfaction scores improved significantly

Less utilization. More output. This is not magic — it is physics. It is the same reason a hospital emergency room maintains empty beds, and a fire station keeps trucks available even when there are no fires.

The Leadership Challenge

The hardest part of this shift is not technical. It is psychological.

Leaders who have been trained to see idle resources as waste must learn to see strategic slack as an investment in flow. This requires a fundamental shift in how we think about organizational performance.

The goal is not to keep everyone busy. The goal is to keep work moving.

This distinction — between resource efficiency and flow efficiency — is perhaps the single most important insight in operational excellence. And it is the one most organizations get wrong.

#flow#efficiency#throughput#utilization#TOC
Share:

Is Hidden Capacity Trapped in Your System?

Take the 5-minute diagnostic to discover how much throughput your organization is leaving on the table.

Take the Diagnostic

These Reflections Are Becoming a Book

Join the waiting list to be notified when it launches — and receive early-access chapters.

Join the Waiting List