Parkinson's Law

"Work expands so as to fill the time available for its completion." Cyril Northcote Parkinson wrote that in 1955, and once you've seen it you can't stop seeing it. It's why the two-week task becomes a two-month project, and why the same team that shipped weekly as a startup ships quarterly once it's big.

I've lived both ends of this. At large companies, a simple change could take a quarter — design reviews, sign-offs, alignment sessions, a 40-page doc nobody read. At my own companies, with no money and no time, we shipped the same class of thing in a week. The teams weren't more talented. They just couldn't afford to let the work expand, so it didn't.

The MVP that quietly becomes a maximum

Every founder knows this movie. "Two weeks, just the core feature." Then week one you add auth — and social login, and password reset, and 2FA while you're in there. Week two the thing works but could be prettier, so, animations. Week eight you still haven't launched, and the minimum viable product has become the maximum one. Not because any of it was wrong, but because you had the time, and work expands to fill it.

The only real defense is constraint

You can't repeal Parkinson's Law, but you can starve it. Give yourself a deadline you'd be embarrassed to miss. Keep the team small enough that there's no room for the work to spread into. Ship at 70% and iterate, because you can always improve a thing later but you can never get the month back. When I plan now, I cut the timeline in half — then I look again and cut it once more. It's startling how much turns out to be "not essential" the moment there's no time for it.

This is the real reason small teams beat big ones. While the giant is on month six of its two-month project, you've shipped, learned, and moved on. They have time and resources. You have a deadline and no choice. The deadline wins more than you'd think.