Constraints and bottlenecks

The single number that ranks work by what it returns on your scarcest resource, the constraint.

Why adding more projects past a point reduces throughput: the capacity paradox in one idea.

Opportunity cost is real, but portfolios book the money they save and never the value they failed to earn. Here is why, and what closes the gap.

Project governance keys on size in dollars. That is why work below the threshold skips scrutiny and still consumes your most constrained specialists.

Optimism bias is not spread evenly across a portfolio. It grows where a benefit claim cannot be checked, and that is what wins your scarcest capacity.

Project constraints usually mean scope, time and cost. Delivery speed is set by one shared resource, and elevating it just moves you to the next ceiling.

Adding people to your constraint makes you slower first. How deep the dip goes, how long it lasts, and the cancellation trap.

Benefits realization usually tracks whether value showed up. The real limit is whether the organization had the capacity to absorb the change at all.

Capacity planning multiplies headcount by a calendar. Those hours vanish into leave, support and switching long before any project sees them.

The theory of constraints says one resource sets your pace. Flow Economics prices every project against it with value per constrained resource hour.

Bottleneck management usually means managing the busiest team. The constraint is different, and the clone test tells you which one you actually have.

Resource allocation by project size puts the biggest promise first. Ranking by return per constrained hour puts the most valuable first.