The Iron Triangle (Scope, Time, Cost)

The Iron Triangle is the traditional model of project trade-offs: scope, time and cost are interdependent, and a project manager cannot fix all three independently. If scope is fixed, then time and cost move together; if time is compressed, then either scope reduces or cost increases; if cost is capped, then scope or time must flex. The model is a simplification — quality is often added as a fourth dimension, and real projects have more variables — but the core principle is usefully robust.

For project controls, the Iron Triangle frames the contingency and confidence discussions. A programme that claims simultaneous P80 confidence on scope, time and cost is claiming something the triangle says is not coherent: if all three are fixed at P80, there is no residual flexibility to absorb any risk that materialises. The honest position is typically P80 on two of the three, with the third allowed to flex — and the sponsor should be explicit about which dimension is the flex.

The Iron Triangle is also what makes pain-gain and target-cost contracts work: by constructing a commercial mechanism where time and cost trade against each other within a defined scope, the parties create an incentive structure that acknowledges the trade-off rather than pretending it does not exist. NEC4 Option C contracts are explicit about this; lump-sum fixed-price contracts often pretend the triangle does not apply and produce disputes when reality disagrees.