Parkinson's Law
Work expands to fill the time allotted for it, so a deadline shapes effort more than the task's actual size does.
Parkinson's Law states that work expands to fill the time available for its completion. Cyril Northcote Parkinson coined it in a 1955 satirical essay about bureaucracy, observing that a British civil servant with a whole day to write one letter would take the whole day, complete with fussing over word choice and taking a walk to clear their head — not because the letter demanded that much time, but because that much time was on offer.
The mechanism runs through how effort calibrates to a deadline rather than to a task's intrinsic size. Given six weeks for a project that genuinely needs two, a team doesn't finish in two and relax — it discovers additional polish worth doing, additional edge cases worth handling, additional review passes worth requesting, until the six weeks are full. None of that work is fake or wasted exactly, which is what makes the law insidious: everyone involved can point to real work that filled the extra time, while the same task under a two-week deadline would have shipped with a smaller, sufficient version of the same decisions.
This gives Parkinson's Law an odd complementary relationship with Hofstadter's Law: Hofstadter says a task takes longer than any estimate, Parkinson says a task takes as long as whatever time you gave it — put together, the schedule is doing more work in determining the outcome than the task's actual difficulty is, in both directions at once. It's also part of why parallel or gold-plated feature work is a symptom of slack rather than ambition: a team with room to spare tends to spend it on the same total scope stretched thinner rather than converging faster.
The practical use of the law is as a scheduling lever rather than a complaint: a genuinely tight deadline, imposed deliberately, compresses a task toward its real minimum — which is most of the actual argument behind timeboxing and behind shipping a Minimum Viable Product on a fixed date instead of an open-ended one.
See also4
Hofstadter's Law
A task always takes longer than expected, even when you plan for it to take longer than expected.
Method5 connections
Minimum Viable Product
The smallest version of a product that lets you learn something real from actual users, not the smallest embarrassing version.
Method6 connections
Feature Creep
A product accumulates features one reasonable addition at a time until the sum is bloated, slow, and hard to use.
Method6 connections
Second-System Effect
The tendency for a system's successor, freed of its predecessor's constraints, to become dangerously over-engineered.
Method10 connections
Related1
Nearby in the graph rather than deliberately chosen. Looser, sometimes surprising.
Linked from3
- Brooks's LawMethod
Adding people to a late software project makes it later, because onboarding and coordination costs outpace the new capacity.
- Feature CreepMethod
A product accumulates features one reasonable addition at a time until the sum is bloated, slow, and hard to use.
- Hofstadter's LawMethod
A task always takes longer than expected, even when you plan for it to take longer than expected.