Parkinson's Law: Why Work Expands to Fill the Time Available

By Camellia · Updated Oct 12, 2026

Parkinson's Law is the observation that work expands to fill the time available for its completion. Give a task a week and it tends to take a week, even if two focused days would have been enough. The practical fix is to set deliberate, realistic limits on time, scope and effort before you start, not after you've run out of room.

Key Facts

• 3. Northcote Parkinson first described the idea in a humorous 1955 essay in The Economist, later expanded into his book Parkinson's Law: The Pursuit of Progress (summary of the essay and book).
• The law is usually quoted as "work expands to fill the time available for its completion".
• The essay was mainly about bureaucracies. Parkinson argued that officials want to multiply subordinates, and that those subordinates make work for each other. The time-management reading came later.
• Judith Bryan and Edwin Locke examined the idea in a 1967 paper, "Parkinson's Law as a goal-setting phenomenon", in the journal Organizational Behavior and Human Performance.
• The opposite problem is just as real. The planning fallacy is an optimistic bias in which people underestimate how long a task will take, even when similar tasks ran long before.
• Hofstadter's Law, from his 1979 book Gödel, Escher, Bach, states that it always takes longer than you expect, even when you take Hofstadter's Law into account.

Where Parkinson's Law Comes From

Cyril Northcote Parkinson was a British historian and writer. His 1955 essay in The Economist was satire, aimed at the way administrative organizations grow. As one summary of the essay puts it, he made two claims: an official wants more subordinates, not more rivals, and subordinates create unnecessary work for each other. The observation about time was the opening line. The rest of the piece was about headcount.

That matters, because the law has traveled a long way from its source. When people today say "Parkinson's Law," they almost always mean a personal or team habit: the report that takes all week, the meeting that fills the hour, the project plan that uses every available sprint. Parkinson wasn't writing a productivity tip. He was making a joke about government offices. But the joke stuck because everyone recognizes the pattern.

So treat it as a useful rule of thumb, not as a proven law of nature. It describes something common. It doesn't say work always expands, and it doesn't say how much.

What the Research Says (and Doesn't)

Bryan and Locke's 1967 paper, published in Organizational Behavior and Human Performance, treats the idea as a goal-setting question, as its title says. That framing is the useful part for managers: if time expands because nobody set a goal for finishing sooner, then setting one is a lever you control.

Be careful with claims beyond that. Plenty of articles cite exact percentages for how much faster people work under a tight deadline. If you can't trace a number to a study you've read, don't repeat it.

How Parkinson's Law Differs from Related Ideas

Parkinson's Law gets mixed up with several neighbors. They pull in different directions, which is why they work best as a set.

Notice the tension. Parkinson says your deadlines are too loose. Hofstadter and the planning fallacy say your estimates are too tight. Both can be true on the same project. Padding a schedule can produce Parkinson's problem, and squeezing it can produce Hofstadter's. The way through is to separate the estimate (what the work really takes, based on past actuals) from the limit (how long you'll let it take).

On the planning side, Roger Buehler's research summary describes the fallacy as robust: it shows up for small tasks like household chores and large projects like subway construction. That's the counterweight to Parkinson. If you only ever shorten deadlines, you'll run into it.

Where You See It at Work

A few patterns to watch for:

• Meetings: A calendar default of 60 minutes gets a 60-minute meeting, even when the agenda needs 25. Our guide to pointless meetings covers the habits behind that.
• Deadlines set far out: "End of quarter" for a two-week job invites a last-week scramble.
• Reports and decks: Polish expands to fill the gap. The fourth round of formatting rarely changes a decision.
• Email and chat: A day with no hard stops fills with low-value messages.
• Planning cycles: A six-week planning process gets six weeks of debate.

The common thread is that no one chose the limit. It was inherited from a default, a habit or a calendar slot.

How to Counter Parkinson's Law: Step by Step

The aim isn't to rush. It's to choose a limit on purpose, and then protect it.

1. Define "done" in one sentence. Write down what the finished output looks like and who will use it. A vague finish line is the biggest source of expansion.
2. Estimate from past actuals, not hope. Look at how long the last two or three similar tasks really took. This is the fix for the planning fallacy, and it keeps your limit honest.
3. Set a limit slightly tighter than the estimate. Not half. A modest squeeze, enough that the work needs focus but still fits a normal day.
4. Break the work into pieces with their own mini deadlines. A single deadline three weeks out is easy to ignore. Three checkpoints a week apart are harder to ignore. Our article on setting tiered goals and metrics shows one way to layer them.
5. Decide what gets cut if time runs out. Fix the time and flex the scope, not the other way round. This keeps a tight limit from turning into stress or poor quality.
6. Put the limit where others can see it. A shared date, a calendar block or a "demo on Thursday" commitment beats a private intention.
7. Review the result. Did the work finish in the limit? Was quality fine? Next time, adjust the limit by what you learned.

If your tasks are mostly small and personal, the 1-3-5 rule and the Ivy Lee method give you built-in limits for a day. For deciding which tasks deserve a tight limit in the first place, start with the Eisenhower Matrix.

Ready-to-Copy Template: Deliberate Limit Planner

Copy this table into your planning doc. Fill in one row per task before you start it.

And a short weekly review table:

Examples by Business Function

These are illustrations of how a team might apply deliberate limits, not benchmarks.

Do's and Don'ts

Common Mistakes

Treating it as a reason to rush. Parkinson's Law is about slack, not speed. If a limit forces errors, it's too tight. The point is to remove empty time, not to remove thinking time.

Ignoring the planning fallacy. Teams that read about Parkinson's Law often shorten every deadline. Then Hofstadter's Law shows up. Use past actuals so the limit is tight but achievable.

Applying it to creative or exploratory work. A hard cap suits well-defined work such as reports, reviews and routine analysis. Open-ended research or design may need a time box for exploring, with a decision point at the end, rather than a deadline for a finished answer.

Setting limits for other people without asking. A deadline imposed from above, with no input, often creates resentment and hidden padding. Agree on the limit with the person doing the work.

Never reviewing. If you set a limit and never check whether it worked, you're guessing again next time. For habits that undermine personal systems in general, see why personal productivity fails.

Putting It Into a Team Routine

One person using a tight limit is a habit. A team using them is a system. A few ways to move from one to the other:

• Change the defaults. Set calendar defaults to shorter meetings. Set project templates with checkpoints already in them.
• Make estimates visible. Record estimate, limit and actual for each piece of recurring work. After a few cycles, you'll know which tasks expand and which don't.
• Pair it with execution discipline. A limit only works if the team follows through. The ideas in disciplined execution pair well with this.
• Look at the whole picture. Limits are one piece of how a team organizes work. Strategies to enhance productivity and efficiency puts them in context with other levers.