Projects rarely collapse overnight. They slip a little, then a little more, until one day the deadline is obviously unreachable and everyone pretends to be surprised. The slip was visible weeks earlier. People just didn’t say anything, because naming a delay feels like admitting failure. Learning to handle the early slip is one of the most useful project skills there is.
Notice it before the deadline does
The first sign is almost never dramatic. A task that should have taken two days takes four. A dependency arrives a bit late. On its own, each looks minor. The danger is that small slips compound silently, because no single one feels worth raising. Track progress against the plan often enough that a one-day drift is visible while it’s still cheap to fix.
Say it plainly and early
When you spot a slip, the instinct is to wait and hope you’ll make it up. You almost never do. Raising it early gives people options; raising it late just delivers bad news with no room to act. A calm, specific heads-up earns far more trust than a confident silence followed by a missed date.
Choose a lever
Once a delay is real, you have a limited set of honest moves:
- Cut scope, and decide together what genuinely matters
- Add time, and reset expectations openly
- Add help, accepting that it slows things before it speeds them
- Lower the quality bar in a place where good enough truly is enough
What you can’t do is wish the constraint away. Pretending all four corners are fixed is how teams end up shipping something broken, late, and exhausting all at once.
A slipped project isn’t a moral failure. It’s information. The teams that recover well are simply the ones that treat a delay as a problem to solve out loud, early, while there’s still time to choose.