The Coordination Ceiling

The coordination ceiling is the point past which adding more projects to a portfolio reduces total throughput rather than increasing it. It is the capacity paradox in one idea: doing more things at once makes the organisation deliver less.

Most organisations behave as though capacity is additive. If a team can run five projects, the reasoning goes, it can surely take a sixth, and a seventh, as long as everyone works a little harder. For a while the numbers seem to support it. Then, past a certain load, output stops rising and starts falling, even as more work is pushed in.

Why the ceiling exists

Two forces create it. The first is contention for the constraint. Every extra project competes for the same scarce resource, and past a point the constraint spends more of its time being fought over, switched between and queued for than actually producing.

The second is coordination overhead. Each additional project does not just add its own work, it adds relationships: more handoffs, more dependencies, more meetings, more context-switching, more places for delay to propagate. That overhead grows faster than the work itself. Beyond the ceiling, the marginal project consumes more coordination and constraint capacity than it contributes, so the whole portfolio slows down.

What it means for how you run a portfolio

The coordination ceiling is why "just add it to the list" is so often the most expensive decision a leadership team can make. The cost of a new project is not only its own effort. It is the throughput lost across everything already in flight.

Running below the ceiling deliberately, by limiting the number of concurrent projects to what the constraint can actually carry, usually delivers more total value, faster, than running above it. Less work in progress, more finished. Recognising where the ceiling sits, and having the discipline to stay under it, is one of the highest-leverage moves available to a portfolio.