What is How scope creep starts and how to contain it — and why should I care?
Scope creep rarely arrives as a demand. It arrives as a favor. A small addition here, a quick extra there, a reasonable request that feels awkward to refuse. By the time the team realizes the scope has drifted, weeks of unplanned work have already been absorbed into the budget. The problem is not that clients ask for more — that is human nature. The problem is that no mechanism exists to make the cost of that ask visible at the moment it happens.
How is it really applicable in real life?
This framework applies to any project or engagement where scope is defined upfront — consulting, technology delivery, construction, creative work, or advisory. It is most urgently needed when the client relationship is warm, because warmth is where scope discipline tends to dissolve first.
How does it actually work?
- 1Define scope in outcomes, not activities. 'Deliver a working integration between systems A and B' is scopeable. 'Support the integration effort' is not.
- 2Create a simple change request process from day one — even a one-page form. The act of writing it down changes the psychology of the ask.
- 3When a request arrives, acknowledge it positively and ask one question: 'Should we log this as a change or absorb it into the current scope?' Do not answer for the client.
- 4Keep a running change log visible to the client. Not as a threat — as a shared record of decisions made together.
- 5Price changes clearly, even when you plan to absorb them. 'This would normally be a change, we are including it this time' teaches the client the value of your boundaries.
- 6Conduct a scope health check at every project milestone. Not to restrict — to confirm alignment before the drift becomes structural.
- 7When scope has already expanded unmanaged, do not fight it retroactively. Document what was added, reset the baseline, and put the process in place from that point forward.
Visual diagram coming soon.
Show me a real example
A software consultant is three months into a system implementation when the client casually asks to include a reporting module that was never scoped. He does not say no. He says: 'That is a good addition — let me estimate the effort and we can decide whether to include it in this phase or plan it for the next.' The estimate comes back at four weeks of work. The client decides to defer it. Without that question, it would have been quietly absorbed, the timeline would have slipped, and no one would have understood why.