The classic triangle
Project Management 101 draws three corners of a triangle: scope, time, cost. The math is unforgiving — if scope expands and time is fixed, cost goes up (you add people or pay overtime). If scope expands and cost is fixed, time slips. If time and cost are both fixed, scope must shrink. There is no fourth direction the system can move.
↳ the lie everyone tells
The fourth corner: quality
The triple constraint hides a fourth lever: quality. When the other three are pinned, quality is what actually flexes — usually invisibly. Bugs get deferred. Tests get skipped. Documentation goes unwritten. Six months later you're paying interest on those decisions in incident response and rework.
PMBOK 7 treats quality as a co-equal performance domain, not a consequence. The honest version of the constraint: scope, time, cost, quality — pick three, and name what you're trading on the fourth.
How to use it in conversation
The triple constraint is most useful as a conversation tool with sponsors, not as an equation you compute in private. When a stakeholder asks for more scope, your job is to surface what they're trading off:
— the constraint conversation
That sentence is the entire job, distilled. It surfaces the trade-off, makes the sponsor own the trade-off (because they're the one funding it), and removes you as the bottleneck. The worst version is "sure, we'll fit it in" — followed by a slip the sponsor didn't see coming.