Why plans slip on ordinary days, and how to catch it while it is still small.
WRITTEN BY
Lena Vermeer
PUBLISHED
READING TIME
4 min read
IN SHORT
01
Slips start small and on ordinary days.
02
Two days only hurts when it lands on someone already full.
03
Reading the plan daily keeps the fix cheap.
Most launches do not fail in a dramatic meeting. They slip on an ordinary Tuesday, by a day or two, while every status still says green.
Why nobody notices
The trouble is that a two-day slip looks harmless on its own. A review ran long, a dependency arrived on Wednesday instead of Monday, someone covered a sick colleague. Each reason is fair, and none of them feels worth raising.
So the slip goes unreported. Not because anyone is hiding it, but because it is too small to deserve a conversation. By the time it is big enough to mention, it has already spread.
Where the damage happens
A slip only becomes a problem when it lands on the one person who was already full. Your designer has three days of slack. Your release engineer has none. The same two days mean nothing to the first and move the launch for the second.
That is why counting late tasks tells you so little. What matters is where the delay ends up, and who is standing there when it arrives.
What to do on Wednesday
Reading the plan every morning changes that. You are not looking for bad news. You are looking for anything that moved since yesterday and what it now touches.
A small gap is cheap to close when you can still see it. Swap a handover, share a review, move a freeze by a day. Each of those takes minutes on Wednesday and takes a whole week in the month of launch.
A small gap is cheap to close while you can still see it.
