Parkinson’s Law

011 min

Parkinson's Law at a glance

• What it is: Work expands to fill whatever time gets set aside for it, real or padded.
• The number that matters: Parkinson's own figures show Admiralty staff rising 78.45% in fourteen years while the fleet shrank by two-thirds.
• Origin: A satirical 1955 essay in The Economist, not a scientific study.
• Where it breaks: The tested cousin is the planning fallacy. A 2002 "proof" of deadline effects was retracted in 2026 for tampered data.

021 min

The problem Parkinson's Law names

A team given a month to finish a two-week project rarely finishes in two weeks. The extra time does not go unused. It fills with more meetings, more revisions, and more debate over details that a tighter deadline would have forced the team to settle quickly. A product manager who blocks a full quarter for a project that needs six weeks usually gets a project that takes a quarter, not one finished early with time left over. The cost is not that the work looks different. It is that time, a limited resource, gets spent without a matching increase in what actually gets produced. A founder who sets no deadline for a hiring decision can spend two months on a choice that four focused days would have settled. The problem here is not laziness; people genuinely believe they are working the whole time. The issue is that the amount of time available, not the actual size of the task, ends up setting how long the task takes.

032 min

Understanding Parkinson's Law

Parkinson's own explanation names two forces, both drawn from years spent watching the British civil service, not from an experiment. The first is that an overworked official does not ask for a colleague of equal rank to split the job with, because a colleague at the same level would become a rival for the next promotion. The official asks for two subordinates instead, each junior enough that neither can replace the official, and each kept in check by rivalry with the other rather than with anyone above. The second force is that new staff generate work for each other: an incoming document now passes through several more people before anyone decides anything, each one drafting, amending, or forwarding it, so the total time spent on that single document grows even though no new task has actually appeared.

Parkinson dressed this in a mock formula, x = (2k^m + p)/n, delivered with the flat seriousness of real mathematics. Nothing in the essay tests the formula against a case where staff did not grow.

The everyday version of the claim, the one people actually mean when they cite Parkinson's Law today, drops the bureaucracy story and keeps only its shape: a task with no firm deadline expands because nothing forces a decision about when it counts as finished, so checking, revising, and reconsidering keep happening until the clock runs out, not the work.

041 min

Where Parkinson's Law comes from

C. Northcote Parkinson, a naval historian, published "Parkinson's Law" as a satirical essay in The Economist in November 1955. He expanded it into a book, Parkinson's Law, or the Pursuit of Progress, published in the United States in 1957 and in Britain in 1958.

The essay opens by calling its subject "a commonplace observation," then spends most of its length walking through a mock-serious statistical case for it, before closing by describing itself as "a purely scientific discovery." The flat, deadpan tone is the joke: a real bureaucratic pattern Parkinson had watched for years, stated in the confident language of a scientific law, with no comparison case to test it against.

052 min

How this plays out

Parkinson's own case study was the British Admiralty. Between 1914 and 1928, the Royal Navy shrank on every measure that mattered to its actual fighting strength, while its administrative staff grew steadily.

Between 1914 and 1928 the Navy's Admiralty officials grew from 2,000 to 3,569, even as its fighting strength fell by a third in men and two-thirds in ships. From 1922 the fleet's size was capped by the Washington Naval Agreement, so no growth in ships was even expected over that period. The number of officials rose 78.45% over those fourteen years, an average of about 5.6% a year, in a navy that was shrinking on every other count.

Parkinson found a similar pattern in the Colonial Office, where staff grew at a peacetime rate that averaged 5.89% a year between 1935 and 1954, even as the territory the office administered shrank as colonies gained independence.

These are Parkinson's own compiled figures, not a result an outside researcher measured independently. They are also the entire evidentiary basis for the essay: no comparison organization, no control case, and no test of an explanation other than the one Parkinson proposed.

062 min

Where the evidence is contested

Parkinson's Law is often repeated as if it were an established finding, but the original essay only ever tested itself against itself. Parkinson picked two departments that had grown and read that growth as proof of a general law, without comparing them to a department that had not grown under similar conditions. There is no control case, and no ruling-out of a rival explanation for why the staff numbers moved.

The most direct attempt to test something like it in a controlled setting shows how easily this territory goes wrong. In 2002, Dan Ariely and Klaus Wertenbroch published a cited study in Psychological Science reporting that people who spaced out their own deadlines finished work better than people who set one deadline at the end. In 2026, a replication by Kyle Hyndman and Alberto Bisin failed to reproduce the result, and the forensic team Data Colada concluded that the data behind one of the original experiments had been tampered with. Ariely later said the data underlying the study "contained serious anomalies," and the paper was retracted.

The concept with real, replicated evidence behind it is not Parkinson's Law but the planning fallacy: people reliably underestimate how long their own tasks will take. Daniel Kahneman and Amos Tversky first described it in 1979, and it shows up in real projects too. The Sydney Opera House was expected to open in 1963. A scaled-down version finally opened in 1973, a decade later.

071 min

Parkinson's Law vs. nearby concepts

Parkinson's Law and the planning fallacy are often used as if they were the same idea, but they describe different mistakes. The planning fallacy is about the estimate itself being wrong before work starts: a team says six weeks and needs twelve. Parkinson's Law makes no claim about whether the estimate is right. It says that whatever time gets allotted, correct or not, tends to get used in full. A single project can suffer from both at once: an underestimated deadline that expands, in turn, to fill whatever revised time it is later given.

081 min

What this means for your work

A product manager who blocks a full quarter for a project that could fit in six weeks should expect the extra ten weeks to disappear into meetings, revisions, and debates over details that a shorter runway would have forced the team to skip. The fix is not to guess less time on purpose. It is to break the quarter into shorter checkpoints with their own deadlines, so no single stretch of unclaimed time is available to expand into.

An engineer estimating a migration should separate the actual technical uncertainty, how long the riskiest step could take if it goes wrong, from the padding added simply because the sprint has room for it. A four-week sprint built around a two-week task tends to produce a two-week task that finishes in four weeks, not one finished early.

A founder deciding on a hire should notice that an open-ended search, with no fixed number of candidates and no closing date, tends to run until something external forces a decision, not until the best candidate has clearly appeared. Setting a fixed number of interviews and a real closing date changes what actually ends the search.

In each case the lever is the same: shrink the time or the scope on purpose, rather than assuming a generous deadline is a free safety margin.

091 min

How to apply Parkinson's Law

Set the deadline to match the size of the actual task, not the size of the calendar slot that happens to be open. A constraint that is looser than the work requires does not protect quality. It removes the pressure that would otherwise force a decision about what "done" means.

Break one long deadline into several shorter ones, each with its own concrete deliverable, rather than a single deadline at the end. One distant deadline leaves the whole stretch of time open to expand into; several close ones each close off a smaller stretch at a time.

Where possible, create genuine time scarcity instead of an unenforced rule: a tight but achievable limit, a fixed number of review rounds, or a hard stop on a meeting's length. Asking people to simply try to move faster, without changing the deadline or the scope, tends not to hold.

101 min

When Parkinson's Law breaks

Treating Parkinson's Law as if a shorter deadline always produces the same quality of work, only faster, is a misuse. Compressing a genuinely underspecified or technically uncertain task below the time it actually needs produces rushed, lower-quality output, not the same output sooner. The essay was about paperwork with no hard floor on how fast it could go, not about work with a real technical minimum.

A second failure is citing the 78.45% Admiralty figure, or the essay generally, as proof that bureaucracies always grow at a fixed rate. Parkinson measured two departments over a chosen period and drew a general rule from them. A single historical case, however well documented, is not a tested finding, and nothing in the essay rules out an organization whose administrative staff shrank or stayed flat under comparable conditions.

112 min

Frequently asked questions about Parkinson's Law

?7 questions

Questions people ask

▶3 videos

Watch

• 

  Understanding Parkinson’s Law

• 

  Parkinson’s Law: How to Manage Your Time More Effectively

  The Art of Improvement

• 

  Parkinson’s Law | Do your work more efficiently | full explanation in Hindi

  BookApt Motivation

§5 sources

Sources