Documentation is the first thing dropped under pressure — and the worst one to lose

When you cut documentation, then testing, then even refactoring, you think you get back to schedule. In reality, you just doomed your project and not even know about it.

I've heard this defended as pragmatism. "We'll write it up afterwards." "The code is the documentation." "We can add tests in the next sprint."

Afterwards never comes. You just took a loan with unknown interest that you pay every day until it buries your organization.

And here is how I push back: dropping tests is a pain You feel within weeks. Bugs surface, on a stakeholder's phone right on the demo. Regressions appear, users get angry and drop the app. The team notices falling KPIs and eventually pushes back, too late though.

Dropping the documentation is invisible at first. There's no immediate feedback loop for it, the system continues to work, velocity may seem stagnant too. The sprint still closes, nobody raises a flag, retros are calm.

And the cost accumulates silently. Every new engineer who joins spends weeks decoding decisions that took hours to make. Every senior engineer asked "why did we do it this way?" answers from memory, and differently each time. Every stakeholder who asks for a system overview gets a two-hour whiteboard session instead of a one-page document. Trade-offs hide in minds unspoken.

Six months later the team is 30% slower and nobody can point to why. Retros are livid but nothing seems to work to correct.

Tests protected you from breaking what worked and now you have a hole in that guardrail. Documentation protected you from forgetting why it worked and now you repeat embarrasing mistakes.

Both matter. But only one of them bleeds quietly. Don't forget, you still pay its interest anyway.

Start with my Tech North Star packages, so the quiet bleeding never happens.