Scope & Scope Creep

Scope is the agreed definition of what a project will — and won’t — deliver. It’s the boundary line everyone signed up to. The version written down at the start, before work begins, is the baseline: the reference point you measure everything else against.

Scope creep is what happens when that boundary quietly drifts outward, one “small addition” at a time, with no matching change to the deadline or the budget. No single request feels unreasonable. Each one is small, sensible, and easy to say yes to. The problem is the sum. Add enough small things to a fixed timeline and you’ve quietly committed to a much bigger project than anyone agreed to fund — and the team is the one left absorbing the gap, usually with late nights.

Why it happens

Scope creep isn’t usually anyone’s fault, which is exactly why it’s so common. Requirements genuinely evolve as people see the work take shape. A stakeholder watches a demo and realises they need one more thing. A “quick win” looks free because it’s “just a small tweak.” Saying yes feels helpful and collaborative; pushing back feels obstructive. So the path of least resistance is always to absorb the request silently — and ten silent yeses later, the project is underwater.

The danger is precisely that each step is invisible. Nobody ever decides “let’s double the project.” It happens through a series of tiny, undocumented favours, none of which felt like a decision at the time.

The fix is visibility, not refusal

The goal isn’t to become the person who says no to everything — that just gets you routed around. Requirements should change as understanding improves. The goal is to make every change visible and deliberate instead of silent and free. That’s what change control is: a lightweight habit, not heavy bureaucracy.

Change control is three simple steps. Log the request so it exists somewhere other than a hallway conversation. Show its impact — what it costs in time, money, or other work. Then get a decision from whoever owns the trade-off. The request might still get a yes. The difference is that now it’s a choice made with eyes open, by the right person, rather than a cost quietly swallowed by the team.

The most powerful sentence in project work: “Happy to add that — it moves the date two weeks (or we drop feature X). Your call.” It turns a silent free favour into a deliberate trade-off.

That one sentence does something subtle: it doesn’t say no, and it doesn’t say a free yes. It hands the decision back to the person with the authority to make it, along with the real price tag. Most reasonable stakeholders, once they see the trade-off clearly, will either fund it properly or decide it can wait.

A quick scenario

A team agrees to build a simple marketing site. Then come the requests: “just add a blog.” “And a newsletter signup.” “And make it multi-language.” “And it still needs to launch on the same date.” Each ask is small. Together they’re a different, much larger project — on the original deadline. The team that wrote down the baseline can point to it and say, “All doable. Here’s what each one does to the date.” The team that didn’t simply ends up working weekends and getting blamed for being late.

How to use it

You don’t need authority to practise this. When a new request lands, resist the reflex to absorb it. Instead, name the trade-off out loud and put it in writing: “Sure — that’s about three extra days. Should it go in now, or after launch?” Keep a visible list of what’s in scope so “is that in or out?” has an answer that isn’t your memory. And when you feel the urge to be helpful by quietly saying yes, remember that the most helpful thing is usually clarity: showing the cost so the right person can choose. That habit protects your deadlines, your team’s evenings, and your credibility all at once.

Spot the scope moment

Read each situation and decide what’s happening, then tap a card to flip it and check your answer.

Sort the scope scenarios

Drag each statement into the type of scope moment it represents — or tap a statement, then tap a category. Hit Check placement when you’re done.