Parkinson's Law
Parkinson's law is the observation that work expands so as to fill the time available for its completion. A task given a week takes a week; the same task given two days usually takes two days.
It began as satire. C. Northcote Parkinson, a naval historian, opened an essay in The Economist in November 1955 with the sentence "It is a commonplace observation that work expands so as to fill the time available for its completion," and went on to explain why the British Colonial Office kept growing as the empire shrank. The essay became a book in 1957, and the first sentence outlived everything else in it.
Why it holds
Three mechanisms, and they compound.
- Estimates anchor on the deadline, not the work. Asked how long a task will take, most people look at how long they have. The deadline becomes the plan.
- Slack gets consumed by scope. Given more time than a task needs, people do not finish early; they improve, extend, check and polish until the time is used. Much of that is real work. Some of it is only visible because the time was there.
- Starting is deferred. A distant deadline gives no reason to begin. The work is done in the final fraction of the window, at which point the window looks exactly as long as the work needed.
The result is that measured task durations tell you about deadlines as much as about tasks, which is a problem for anyone using historical durations to plan.
Where it stops being true
The law is a satirist's observation, not a finding, and it fails in predictable places.
Work with a fixed physical duration. A build that runs for forty minutes runs for forty minutes. Manufacturing, testing, curing and travel do not compress because someone set a shorter deadline.
Work that is already saturated. Parkinson's law describes slack being absorbed. A team with no slack and a shortened deadline does not get faster; it ships less, ships worse, or works evenings. Our page on burnout covers what that looks like six months later.
Work whose quality is the point. Some of the expansion is polish that matters. A contract, a diagnosis or a load calculation given too little time is not done efficiently; it is done badly.
The practical reading: the law tells you that padding is invisible and gets spent, not that every deadline should be halved.
How to use it
- Estimate the work before you look at the calendar. Ask how long the task takes with full attention, then set the deadline from that, plus a stated buffer. The buffer being visible is what stops it being consumed.
- Timebox rather than deadline. The Pomodoro technique is the smallest version of this. A fixed block of time with a defined stopping point turns the law to your advantage: the work fills the box and then stops. Our focus blocks guide covers how to hold those boxes in a real calendar.
- Shorten the meeting, not the project. Meetings are where the law is most reliable and least costly to test. A thirty-minute meeting scheduled for twenty-five usually loses nothing.
- Separate "done" from "improved". Define what finished looks like before starting, so that time left over is a decision about whether to polish rather than a default.
- Plan capacity on work, not on elapsed time. If historical durations were set by deadlines, using them to plan repeats the padding. The capacity planning guide covers estimating from effort instead.
The related idea people reach for next is deep work, which is roughly what happens inside a timebox when the law is working for you rather than against you. The wider set of methods is in our time management techniques guide.
Related laws often quoted alongside it
| Name | Claim | Relationship |
|---|---|---|
| Parkinson's law of triviality | Groups spend the most time on the least important item, because everyone can have an opinion on it | Same essayist; often called bikeshedding |
| Hofstadter's law | It always takes longer than you expect, even when you take this into account | The opposite failure: underestimating rather than padding |
| Student syndrome | Work starts only when the deadline is close | The third mechanism above, named on its own |
| Goodhart's law | A measure that becomes a target stops being a good measure | What happens when task durations are scored |
Key points
- Parkinson's law: work expands to fill the time available. It began as a 1955 satirical essay in The Economist by C. Northcote Parkinson.
- It holds because estimates anchor on the deadline, slack is absorbed by scope, and starting is deferred until the window looks tight.
- It fails for work with a fixed physical duration, for teams that are already saturated, and for work whose quality is the point.
- Estimate the work before looking at the calendar, and make the buffer visible so it is not spent.
- Timeboxing turns the law to your advantage: the work fills the box and stops. Meetings are the cheapest place to test it.
- Historical task durations reflect deadlines as much as effort, so plan capacity on work rather than elapsed time.
Frequently asked questions
What is Parkinson's law?
The observation that work expands so as to fill the time available for its completion. A task given a week will usually take a week; the same task given two days will usually take two days.
Who came up with Parkinson's law?
C. Northcote Parkinson, a British naval historian, in a satirical essay published in The Economist in November 1955. He expanded it into a book, Parkinson's Law: The Pursuit of Progress, in 1957. The essay was about the growth of bureaucracy; the opening line is what survived.
Is Parkinson's law real?
It is an observation rather than a scientific law, but the mechanisms behind it are well documented: people anchor estimates on available time, use slack to extend scope, and defer starting. It is reliable for knowledge work with flexible scope and unreliable for work with fixed physical duration or teams already at capacity.
How do you overcome Parkinson's law?
Estimate the work before setting the deadline, make any buffer explicit rather than hidden, use timeboxes with defined stopping points, define what finished means before starting, and shorten meetings. The aim is to stop padding being invisible, not to make every deadline shorter.
What is Parkinson's law of triviality?
A second observation from the same author: a committee will spend the most time on the item everyone understands, such as the color of a bike shed, and wave through the item nobody does, such as a reactor. It is usually called bikeshedding.
Does Parkinson's law apply to teams?
Yes, and the effects compound. A team's historical durations reflect its deadlines, so planning from them repeats the padding. Estimating from effort and holding a visible buffer at the project level works better than shortening every individual task.