Loading...
In January, NovaCorp's CTO Kai greenlights a customer portal rebuild. The engineering lead Mira estimates 12 weeks — she's done similar projects before. The VP of Product, Leo, adds a 4-week buffer 'just in case,' setting the deadline for mid-May. By March, the team has burned through 8 weeks but completed only 30% of the work. Mira notices engineers spending days perfecting login animations and debating database schemas that won't matter until Phase 2. With 16 weeks of runway, nobody feels urgency — meetings multiply, code reviews become philosophical debates, and a 2-day API integration stretches to three weeks of 'doing it right.' In April, Leo calls an all-hands: they're behind. He revises the estimate to August, confident this time because he's 'accounting for the delays we've seen...
Popular framing: Lazy engineers and bad management blew the deadline; better people would have shipped on time.
Structural analysis: Parkinson's Law expanded the work to fill the available buffer; the planning fallacy meant each revised estimate stayed optimistic by ignoring the team's own track record on similar projects; Hofstadter's Law guaranteed the next revision would underestimate again. With Pareto-distributed task value diluted across animations and schema debates, the 80% that didn't matter consumed the 80% that did. Replace the cast and the buffer-driven scheduling architecture produces the same 14-month, 5x-over-budget outcome.
Blaming estimation or leadership preserves the belief that better judgment next time will fix it, which protects the organization from confronting the incentive structure that rewards confident deadlines and punishes uncertainty. The competitor's success was not a talent advantage — it was a constraint advantage: no runway meant no Parkinson's expansion. Until NovaCorp changes the structural conditions, the same pattern will recur on the next project.
