Scope Creep

Scope creep is the gradual expansion of what a project is expected to deliver, without a corresponding change to the time or budget. It rarely arrives as one large request. It arrives as a series of small, individually reasonable ones.

"While you are in there, could it also..." is the sound of scope creep.

Why it is not simply the client's fault

The standard framing blames the buyer for changing their mind, which is unfair and not very useful.

Most scope creep comes from ambiguity that was present at the start and got resolved later. A requirement that could be read two ways gets built one way, the client meant the other, and fixing it looks like a change when it is really a clarification. A supplier who wrote a vague specification has created the conditions for it.

It also comes from suppliers who say yes to everything to stay pleasant, absorb the cost for a while, and then produce an uncomfortable invoice or a late delivery.

What it costs

Beyond money, the real damage is to the relationship. Both sides end up feeling the other behaved badly: the client sees an invoice for work they thought was included, and the supplier sees a project that consumed twice the estimated effort.

It is also the most common reason fixed-price projects go wrong. The supplier who priced their worst case is overcharging the client who stays in scope, and losing money on the one who does not.

How to prevent it

Write deliverables, not activities. "We will work with your team to optimise the user journey" cannot be judged complete. "Redesigned checkout with three screens, tested on mobile and desktop" can.

State the assumptions. Every estimate rests on them. A supplier who will not write them down has transferred that risk to you silently.

Agree a change process before you need it. How a change is raised, estimated, approved and priced, and who can approve one. A supplier who says only that they are "flexible" means unpriced, and unpriced means a conversation later.

Say what is out of scope explicitly. The list of what a project will not do is more useful than the list of what it will.

The healthy version

Change is not the enemy. A project that learns nothing during delivery was not worth doing.

What separates a working arrangement from scope creep is whether change is visible: raised, costed and agreed as it happens, rather than absorbed silently and settled at the end.