Parkinson's Law
Parkinson's Law: Work expands to fill the time available for its completion. Give a task a week, it takes a week. Give it a day, it takes a day. The implication: the right amount of time for a task is usually much less than people allocate β and artificial deadlines dramatically improve output quality and quantity.
What Is Parkinson's Law?β
Cyril Northcote Parkinson introduced the law in a satirical essay in The Economist in 1955, opening with the memorable observation that "an elderly lady of leisure can spend the entire day in writing and despatching a postcard to her niece at Bognor Regis." The observation extended: the work involved in any task expands to fill the time given for it.
Parkinson originally applied this to bureaucracy: government departments grow regardless of the actual work to be done, because administrators create work for each other and the appearance of busyness is its own reward. But the principle applies to individual tasks, projects, meetings, and organizations at every scale.
The mechanism: when people have abundant time for a task, they use it. They revisit decisions already made, add complexity that wasn't necessary, seek more input than required, and generally fill the available container. When time is constrained, focus sharpens, unnecessary complexity is abandoned, and "good enough" becomes achievable.
This is not about laziness β it happens even with highly motivated people. The abundance of time changes the decision-making frame: with plenty of time, perfection feels achievable; with limited time, sufficiency is the target.
How It Worksβ
Parkinson's Law in Practice:
Mechanism:
Time available β Sets expectations β Work expands to meet expectations
Symptoms of Parkinson's Law:
β’ Projects consistently finish just before deadline, regardless of deadline
β’ Meetings consume their entire scheduled time
β’ Budget is always fully spent by year-end
β’ Email responses expand to fill available response time
β’ Bureaucratic paperwork grows over time regardless of workflow changes
Countermeasures:
1. Set shorter deadlines than you think are needed
2. Timebox meetings and work sessions (Pomodoro Technique)
3. Use "good enough" criteria before starting
4. Eliminate or shorten meetings that have always taken their allotted time
5. In organizations: set headcount constraints before defining scope
Three Real-World Examplesβ
The 37signals Work Experimentβ
Basecamp (formerly 37signals) deliberately runs six-week project cycles with a hard cutoff β not an eight-week cycle with two weeks of buffer. Their observation: six weeks is enough to build a meaningful feature because the constraint forces teams to cut complexity aggressively. With eight weeks, the same feature would acquire two extra weeks of scope.
They call the extra scope "scope creep that Parkinson's Law would have generated" and argue that the hard six-week constraint produces better products with less work β because the constraint forces ruthless prioritization.
Budget Cyclesβ
Nearly every organization with annual budgets fully spends them by year-end. Even in years of unusual efficiency, department heads find ways to allocate remaining budget β because unspent budget signals that the allocation was too high, which risks a lower allocation next year.
This is Parkinson's Law applied to budgets: spend expands to fill the available allocation. The solution used by some organizations: rolling budgets (reallocation based on need rather than annual cycles), or "use it or lose it" replaced with explicit incentives for returning unspent budget.
Meeting Durationβ
A meeting scheduled for one hour will take one hour. The same meeting scheduled for 30 minutes will also produce a result β but with tighter focus and less peripheral discussion. Jeff Bezos banned PowerPoint presentations at Amazon executive meetings in part to address this: the reading time of a 6-page memo is fixed, while a presentation can expand indefinitely to fill time.
When to Use Itβ
β Apply Parkinson's Law awareness when:
- Setting project timelines (set shorter than you think you need, then adjust)
- Designing meeting structures (timebox aggressively)
- Diagnosing why tasks consistently take "as long as they take"
- Evaluating organizational efficiency and bureaucratic growth
| Pairs well with | Why |
|---|---|
| Theory of Constraints | Both identify how timing and capacity decisions shape system output |
| Pareto Principle | 80% of a task's value is produced in 20% of the time β Parkinson explains the rest |
| Precommitment | Deadlines are a form of precommitment against Parkinson expansion |
Common Misusesβ
Treating Parkinson's Law as an argument for cruelty. Unrealistic deadlines don't improve quality β they increase errors, burnout, and technical debt. The law suggests deadlines should be tighter than the team's instinct; not impossibly tight.
Ignoring legitimate complexity. Some tasks genuinely require the time allocated. Parkinson's Law applies most strongly to tasks with variable scope and uncertain criteria for "done."
Common Misuses and Limitationsβ
Treating it as satirical only. Parkinson's Law is often quoted as wit, but the research and mechanism are serious. The phenomena of work expansion and bureaucratic growth are real and well-documented. Dismissing it as merely clever misses its practical value for project management and organisation design.
Using it to justify cruelty. "Set impossible deadlines to force efficiency." Artificial time pressure reduces quality, increases errors, damages morale, and produces technical debt. The correct application is appropriate constraints and clear scope definition β not arbitrary stress. Parkinson described what happens, not a prescription for how to manage.
Assuming all expansion is bad. Some tasks genuinely warrant the time allocated to them. A system design review may expand to fill a week because the system is genuinely complex. Parkinson's Law applies most clearly when the expansion is in low-value activity (status meetings about the project, email threads, formatting reports) rather than the core work.
Ignoring context. Knowledge work is harder to constrain than task-based work. A lawyer's brief genuinely may require a week of research β the quality difference between one-day and five-day research is real. Parkinson's Law is most actionable for project planning and meeting design, not for all professional work.
Related Modelsβ
| Model | Relationship |
|---|---|
| Theory of Constraints | Identifying the real constraint prevents Parkinson's Law from consuming slack |
| Eisenhower Matrix | Time-boxing by priority prevents low-priority work from expanding into high-priority slots |
| Pre-commitment | Pre-committing to deadlines counteracts Parkinson's Law expansion |
| Brooks's Law | Brooks's Law and Parkinson's Law together explain why software projects chronically run late |
Frequently Asked Questionsβ
What is Parkinson's Law of Triviality (the "bikeshedding" corollary)?
Also from C. Northcote Parkinson: organisations give disproportionate time to trivial issues because they are comprehensible to everyone. In a committee approving a nuclear power plant and a bicycle shed, the nuclear plant is approved quickly (too complex for most to critique) while the bike shed generates hours of debate (everyone has opinions about colour and materials). Applied to modern product development: teams will spend less time on architecture decisions (complex) and more on button colour (trivial). Structuring meetings to protect complex topics from trivial ones is a direct countermeasure.
How does Parkinson's Law affect remote work?
Remote work removes many natural time constraints (commute timing, office hours), which can amplify Parkinson's Law: without the structure of a physical workday, tasks may expand further. Counteracting this requires explicit time-boxing, clear deliverable definitions with deadlines, and async communication norms that prevent low-value synchronous meetings from filling the schedule. The best remote teams are often more disciplined about Parkinson's Law than office teams precisely because they've had to design around it explicitly.
What's the optimal strategy for using deadlines to combat Parkinson's Law?
Make deadlines (1) specific β not "end of month" but "Friday at 5pm"; (2) output-defined β what is the deliverable, not just when it's due; (3) appropriately challenging β tight enough to prevent expansion, not so tight that they destroy quality; and (4) committed publicly β Parkinson's Law weakens when others are counting on the deadline. Time-boxing meetings (strict end times), sprints (fixed-length development cycles), and "working backwards" planning all operationalise these principles.
Further Readingβ
- Parkinson, C.N. (1955). "Parkinson's Law." The Economist β the original essay
- Parkinson, C.N. (1957). Parkinson's Law and Other Studies in Administration β the expanded book
- Newport, C. (2016). Deep Work β time constraints and high-quality focused output
Apply with AIβ
π Set better deadlines and timeboxes with MindMax β
This page is part of the MindMax Mental Models Knowledge Base.