When scope creep is worth the effort

There is no clever trick in this one, just a handful of decisions worth making deliberately. Scope creep is not free, and pretending otherwise leads to bad decisions.

The projects that go badly are rarely the ones with the hardest technical problems. It is the sort of thing that looks like polish right up until it costs you an enquiry.

When it is worth it

Small additions compound into missed deadlines. The teams that handle this well are rarely the ones with the biggest budgets. Most teams find the first pass takes an afternoon and the maintenance takes minutes a month.

When it is not

If nothing downstream depends on it and nobody is complaining, it can wait. Where this goes wrong is almost never a lack of knowledge.

How to decide

Say yes to the change and honest about the cost. This is the sort of thing that compounds, quietly, in both directions. Assume whoever inherits this will have half your context and none of your patience.

In practice

Clear scope protects the client at least as much as it protects the agency. Three things worth confirming about scope creep before you move on:

• Someone can say what the current setup is without going to look
• A written change process protects both sides — and you know whether that is true here
• There is a way to tell whether the last change to this helped

Worth checking on your own setup before it becomes someone else's problem to fix.