This is the post-mortem we don't usually write down. Not because it's embarrassing — because the lesson is so obvious in hindsight that it sounds smug to publish. But the gap between knowing the lesson and living through the lesson is wider than people admit. So here it is.
The project was solid on paper. Reasonable scope. A client we liked. A timeline that had a small buffer. We were a few weeks in when three things happened in the same fortnight.
First, a feature that we'd estimated at two days turned out to depend on an external API whose behaviour didn't match its documentation. Then the client realised they wanted a small extension to a flow that, on inspection, wasn't small. Then a team member's family had a medical emergency and they were out for a stretch we had to cover.
Any one of those is a normal week. All three at once was the kind of soft compounding that turns a calm project into a quiet panic.
We did not handle it perfectly. The first week, we under-communicated. We told ourselves we'd "pull it back" before we had to bother the client. We worked late nights privately. The status updates went out on Friday with the same line as always — "On track." They weren't.
The second week, we caught ourselves. We sent a long, honest message to the client laying out exactly what had happened, what was now realistic, and three options for how to proceed. The reply came back within an hour. "Thanks for being straight. Take the extra two weeks. We need it done well, not done fast."
That client became one of our longest. Not despite the slippage — partly because of it. The first time we'd been honest about being behind, they'd seen us choose their interest over our pride. They never forgot.
The rule we put in place after, and have not broken since, is the 72-hour rule. If we discover any reason a project will slip — internal, external, anything — we tell the client within 72 hours. Not when we have a fix. Not when we know how bad it'll be. Just the fact that something has changed.
It costs us nothing. It costs the client nothing. It saves the relationship. And the more we use it, the less often we need it — because the discipline of saying it early forces us to spot drifts earlier.
Every studio has builds that almost didn't ship. The ones who keep clients are the ones who tell the truth before the deadline does.