Scope Grows Unless Bounded
Every addition was reasonable. Why is it three months late?
The idea
Every reasonable small addition expands a project, and the sum of reasonable additions is an unshippable one.
In the real world
Six small requests turn a two-week build into two months.
Going deeper
Judging each addition on its merits has no mechanism for saying no, because each one really is small and sensible. Six reasonable additions turn a two-week build into two months without any single unreasonable decision.
A fixed budget supplies the missing mechanism. When the total is agreed up front and anything new must displace something already in, the cumulative cost becomes visible at the moment of asking, and the conversation shifts from is this worthwhile to is this more worthwhile than what it replaces. That second question has an answer; the first almost always returns yes.
Where it stops applying
Rigid scope freezes discard genuine discoveries made during the work, which is when the most valuable information usually arrives. The trade is explicit displacement, not refusal to change.
Why it matters
It shows that scope control is about the cumulative total, not about whether each request is sensible.
Try this today
Write down what is explicitly out of scope before the next project starts.
Test yourself
A two-week project takes two months after six additions, each of which was individually justified and small. Where should the control have been?
Show the answer
On the total, agreed up front, with anything new displacing something already in. Judging each request on its own merits has no mechanism to say no, because each one really is small; only a fixed budget makes the cumulative cost visible at the moment of asking.
Learn this in the feed Answering from memory, then again days later, is what makes it stick.