Nobody decides to be two months late. There's no meeting where someone stands up and says "let's push the launch to August." It just happens. A little at a time. And one day you look up and the plan you sent in March doesn't resemble the plan you're living in.
That's the thing about schedule drift. It's never one big move. It's a hundred small ones.
The Slip You Can't Feel
A phase runs three days long. Nobody panics over three days. The next phase starts three days late, runs four days long, and now you're a week off. Still fine. Still recoverable. You tell yourself you'll make it up later.
You won't. Later has its own delays.
Six weeks of this and the gap is real. But because it arrived in three-day increments, you never felt the moment it got serious. There was no alarm. Each individual slip was too small to notice, and the sum was too gradual to feel.
This is the trap. Day to day, your plan looks basically fine. It's only when you put March next to May that the story snaps into focus.
Why You Can't See It From Inside
You're too close. You updated the plan yourself, one edit at a time, so every version felt like a reasonable adjustment to the last one. The frog doesn't notice the water heating up.
Your stakeholders, on the other hand, see it instantly. They haven't watched the gradual changes. They remember the timeline from the last board deck, and they're comparing it to what you just showed them. To them, the drift isn't gradual. It's a cliff.
That's the worst way to find out a plan slipped — from the person you were supposed to be managing the plan for.
Comparison Isn't About Catching Changes
Most people think of schedule comparison as a way to spot what moved. Useful, but that's the small version of it.
The real value is seeing the pattern. Not "this phase moved 8 days," but "everything in the backend workstream is sliding, and nothing in design is." Not "we're late," but "we've slipped a week every month for three months, and it's accelerating."
One slip is noise. The trend is the signal. And you can only see a trend by laying versions on top of each other.
Put March Next to May
Here's the whole trick. Take the plan you have now. Put it on the same timeline as the plan from two months ago. Look at the shape.
Where the bars line up, you held. Where the current bar has walked right of the old one, you slipped — and the size of the gap tells you by how much. Do this across a portfolio and the pattern is obvious in seconds: which workstreams are stable, which are quietly eroding, where the next crisis is forming before it's a crisis.
You're not hunting for individual changes anymore. You're reading the drift the way your stakeholders will read it — before they do.
The Habit That Saves You
The teams that don't get ambushed do one boring thing: they keep their old versions and compare on a rhythm.
- Monthly. This month's plan against last month's. Catches the three-day slips while they're still three days.
- Before every board meeting. Current plan against the version you presented last quarter. Now you walk in knowing the story instead of improvising it.
- After the project. Original plan against the final timeline. This is where you learn that you always underestimate testing by 40 percent, so next time you don't.
None of this requires more discipline in how you run the project. It requires keeping your versions and looking at them together.
See the Drift
Strategy Gantt's comparison view overlays two versions of a plan on one timeline — the old one as an outline, the current one as a solid bar — and tells you, per phase, how many days moved and which way. The pattern you couldn't feel from the inside, laid out in about thirty seconds.
It's free for one person, version comparison included. Plan solo, free — import two versions and see what's really been happening.