Project Management Triangle
Speed, quality, and low cost compete for the same finite capacity. Push hard on two, and the third usually becomes the price—even when nobody names the sacrifice.
A project can be fast. It can be good. It can be cheap. The impossible brief is demanding all three at once—as though three reasonable requests remain reasonable when combined.
E1The third side pays
Speed requires concentrated effort or fewer iterations; quality requires skill, care, and rework; cheapness limits the people, tools, and time available. These demands draw on overlapping resources, so maximizing two transfers pressure to the third. This is the fast-good-cheap version of the Iron Triangle and a practical trilemma: the constraint does not disappear because a plan omits it. The sacrifice merely becomes implicit.
E1A constraint map, not a law of exact prices
The triangle does not prove that every improvement must cause equal damage elsewhere. Better tools, narrower scope, or a different delivery path can shift the frontier. It also cannot tell you whether more money will guarantee quality—a reminder to distinguish constraints from guarantees. What it exposes is the need to account for the trade-off.
Name the protected corner
At your next project kickoff, rank fast, good, and cheap from one to three, then write the permitted failure beside the lowest-ranked corner. If speed and quality are protected, approve the extra cost explicitly; if cost and quality are protected, set a later date. When the real escape is reducing the work, define that reduction before scope-creep quietly restores it.
Episodes that teach this
-
You Can't Have Everything You Want | Impossible Trilemmas
· explained at 0:53
1,763 views
"You can't have things that are fast, good and cheap."