Author: Ben Rawson
-
A dependency looks free because nobody books it. It costs you the last arrival, shared risk, and a queue that lives between two plans.
-
Green for months, red three weeks out. Percent-complete cannot warn you, because it never measures the thing the plan protects.
-
The same scope as one project or as four. Batch size decides when value arrives, when problems surface, and how much risk you carry.
-
Starting a project before it can actually run costs more than starting it late, because a stalled start still holds the constraint.
-
Your constraint is not your busiest team. Read the queues instead, and use the clone test to find the resource that sets your speed.
-
Everyone pads their estimates and the projects are still late. Where the safety goes, and why adding more of it cannot help.
-
Weeks of elapsed time, minutes of real work. Busy people and waiting work are the same condition, not opposite ones.
-
A road jams long before it is full, and so does a team. Why ninety-five percent busy is the slowest way to run a portfolio.
-
A portfolio where everything has started is not a portfolio in motion. It is a queue. The fix is a limit, not an exhortation.
-
Ranking projects by size puts the biggest promise first. Ranking by return per constrained hour puts the most valuable first.