SCOPE DRIFT
You didn’t agree to more work.
But the work kept expanding anyway.
What this pattern is
Scope doesn’t usually change all at once.
It shifts through small moments:
“While we’re at it…”
“Can we also include…”
“It should be quick…”
Each one feels reasonable.
But no one stops to ask:
Is this still the same project?
What this actually looks like
The scope document still exists
The process is still in place
The plan hasn’t officially changed
But:
The team is doing more than originally defined
Stakeholders expect more than was agreed
And new work shows up without a clear decision
Nothing feels like a formal change
But the project is no longer what it was
Why this happens
Most scope expansion doesn’t go through a formal process
It happens through conversation
Small agreements
Quick approvals
Offhand decisions
Each one makes sense on its own
But together, they quietly redefine the work
What this causes
The project starts to feel harder than it should be
Timelines slip without a clear reason
Workloads increase without acknowledgment
And expectations keep growing without reset
You’re trying to manage the plan
But the work has already moved beyond it
First move to stabilize it
Assume the scope has already shifted
Start asking:
What was originally agreed?
What has been added since?
Where did those additions come from?
Clarity comes from identifying where the work expanded
Not from relying on the original plan
If this feels familiar, you’re not the only one seeing it.
If this pattern feels familiar, you’re not the only one dealing with it.
I write about these moments every week in PM Clarity—how to spot them earlier and what to do before they turn into rework.
Weekly notes for project managers who want to see what others miss.
When changes are discussed but never clearly confirmed, the team starts moving on different assumptions. What feels agreed often isn’t.
→ See Undocumented Agreement
When the project story no longer matches what’s actually happening, it becomes harder to track what’s changed—and why. Scope starts drifting without a clear narrative.
→ See Project Story Drift
When the project starts to feel out of control, it’s often not one big issue—but many small shifts that were never stabilized.
→ See Project Stabilization
When you inherit a project where scope already feels unclear, it’s often because changes were absorbed without being fully surfaced or tracked.
→ See Inherited Project Story