Scope creep starts in the kickoff
By the time scope creep is obvious, it's expensive. It almost always traces back to a vague definition of done at the very start.
Scope creep feels like it happens gradually in the middle of a project — one small addition at a time. But the conditions for it are usually set on day one, in a kickoff that never pinned down what the project actually included and, just as importantly, what it didn't.
Ambiguity is the opening
If the goal is fuzzy, every new idea seems like it might belong. Without a clear boundary, there's nothing to push against, so scope drifts outward by default. The additions feel reasonable individually; together they sink the timeline.
Define the edges up front
A good kickoff states not just what you're building but what's explicitly out of scope. That out-of-scope list is the most valuable part — it gives everyone a shared place to put 'good idea, not now.' You can always expand later; you can't easily reclaim a timeline.
Scope creep isn't a mid-project problem. It's a kickoff that forgot to say what it wasn't building.