Iron Triangle

mental-model

Every project constrains three variables: scope, time, and resources. Tightening one side without loosening another does not remove the trade-off; it forces the remaining side to absorb it.

A tighter deadline does not necessarily make the same project happen faster. If no extra people, money, or tools arrive, the deadline quietly changes what the project can be.

E1

Pressure has to move somewhere

Scope, time, and resources form a coupled system. Scope is the work promised; time is the window available; resources are the capacity that can be applied. Compress the schedule while holding capacity fixed, and fewer units of work can be completed. The resulting scope reduction may be explicit—features are removed—or concealed through thinner testing, less polish, and unfinished detail. The triangle is therefore a constraint model, not a productivity slogan: changing one variable creates pressure on at least one other.

E1

Where it shows up

The immovable deadline

When delivery must happen sooner and resources cannot increase, the honest response is to reduce the promised work. Keeping every requirement merely hides the cut instead of preventing it.

E1

Not every constraint is truly fixed

The triangle clarifies trade-offs, but it does not prove that current estimates, processes, or resource limits are optimal. A better method may increase capacity. What it rules out is assuming that an unchanged team can reliably deliver unchanged scope in less time without identifying a real source of added capacity.

Turn the deadline into a deletion list

For your next compressed project, write down the deadline, available capacity, and every promised deliverable. If time moved earlier and capacity did not rise, rank the deliverables and explicitly remove the lowest-value ones until the plan fits—before hidden cuts appear in quality.

E1

Episodes that teach this