Bottleneck Thinking: Fix the Constraint, Not the Whole System

Every project has one thing holding it back at any given moment. Find that constraint and you move the whole project. Miss it and you polish the parts that don't matter.

One constraint at a time

Borrowed from the Theory of Constraints, bottleneck thinking says a system's throughput is limited by a single constraint at any moment. Work anywhere but the constraint and you're just creating inventory — effort that doesn't move the finish line. The skill is finding the one thing actually holding a project back today.

Bottlenecks hide in lists

A vertical list is terrible at revealing constraints. Every item looks equally urgent, and the real blocker — the approval you're waiting on, the overloaded person — is invisible among the noise. You end up busy on the wrong end of the project while the bottleneck sits untouched.

A grid makes constraints visible

Spatial layout exposes bottlenecks. On Axtio, a project stuck because everything's parked in Other is obvious — the whole row is waiting on other people. A Mine column overflowing on one project screams 'this is where you're the constraint.' You see the choke point instead of guessing.

Move the constraint, move the project

Once you can see the bottleneck, the highest-leverage action is obvious: clear it. Everything else can wait. Fixing the constraint, not the whole system, is how projects actually accelerate.

Keep reading: seeing blocked work, keeping projects moving.