Scope Creep Begins When the Decision Remains Undefined

Scope creep rarely starts with a stakeholder asking for one more thing. It usually starts earlier — at the moment no one has written down which decision the work is actually supposed to support.

“Let’s just improve the onboarding funnel” sounds like a project. It isn’t anchored yet. Without a named decision it must serve, most new requests sound reasonable, because there’s no fixed reference to test them against.

“Can we also look at X?” isn’t scope creep if the project was never scoped to a decision in the first place — it’s just more work, and more work often feels like progress while it’s happening.

Name the decision first

The real fix isn’t simply saying “no” more often. It’s naming the decision before the work begins:

• What is this actually for?
• Who makes the call once it’s delivered?
• What would make that call obvious rather than debatable?

Once that decision is fixed, every new request has something real to be measured against. When one appears, ask one question: does this change the answer to the decision?

If it does, it belongs here. If it doesn’t, it’s a different project — and saying that out loud, early, keeps scope from quietly becoming the entire conversation.