Here is the uncomfortable thing about scope creep: from the inside, while it is happening, it looks exactly like work. Everyone is busy. Tickets are moving. The team is plainly putting in effort. And the go-live date keeps sliding, a week at a time, for reasons no one can quite name. Nobody decided to expand the project. It expanded anyway.
That is the distinction the title is pointing at. Progress is movement toward a defined end. Drift is movement, full stop. They produce the same standups, the same sense of momentum, the same tired satisfaction at the end of a long day — and only one of them is actually getting closer to done.
Scope creep is usually an absence
We tend to picture scope creep as a decision: someone signs off on a big new requirement and the project grows. In practice it is almost never that. It is the absence of a decision, repeated. The "while we're in here, let's also." The field that's "tiny" to add. The requirement that arrives disguised as a bug. The stakeholder who routes one more ask through a side conversation instead of the change process. Each addition is individually reasonable. No single one is worth stopping the program over. The sum is a project nobody chose.
This is why drift is so hard to catch from the inside. There is no moment where someone stands up and proposes doubling the scope. There are forty moments where someone says "this'll only take a second," and they are each telling the truth, and every one of them is wrong about the aggregate.
The tells
You can feel the difference, if you know what to listen for.
- The date moves, and no one can say exactly why. Progress has a reason for every slip. Drift just slips.
- New work appears without an owner who chose it. It's in the backlog, but no one can point to the decision that put it there.
- You're busier than last month and no closer. Effort is up, distance-to-done is flat. That gap is the whole diagnosis.
- You can't quickly name what's out of scope. If everything could plausibly belong, nothing has been decided. A scope that excludes nothing isn't one.
Make the expansion a decision
The fix is not to freeze the project in amber. Requirements change, and pretending otherwise is its own kind of failure. The fix is to make every expansion a decision someone makes on purpose, with the tradeoff named out loud: if this goes in, what comes out, or what date moves. A change is not free because it is small. It is just a small bill — and the program pays all of them.
That naming is the entire discipline. It converts a side-door addition into a choice with a cost attached, which is something a program can actually weigh. Half of what gets proposed survives the question. The other half was drift wearing the costume of progress, and the question is what undresses it.
The cure for drift is not standing still — it is deciding where you grow, which is the next piece in this series. Both drift and progress move. The only difference is that one of them chose where.