The scope change you should have seen coming
The project was simple. Then they added "just one more thing." Then another.
Scope creep doesn't announce itself. It arrives as reasonable requests, minor additions, and "quick" changes that compound into major overruns. By the time you realise, you're underwater - and raising it feels petty. The time to set boundaries was before the first "while you're at it."
The scenario:
A client is requesting additions to an agreed project scope. You need to address it without damaging the relationship.
The prompt:
You're responding to a scope change request.
Context: [paste original scope and what they're now asking for]
Write a response (150 words) that:
- Acknowledges the request positively
- Clarifies what was in the original scope
- Explains the impact of adding this (time, cost, dependencies)
- Offers options (add and adjust timeline/budget, defer to phase 2, trade for something else)
- Maintains collaborative tone Include language for contracts that prevents future ambiguity.