Parkinson's Law: What the 1955 Essay Actually Said and How Operators Use It Against Themselves

Work expands to fill the time you give it, and an operator with no boss gives it everything.

The founder who sets aside "the morning" for a proposal finishes it at 4 p.m. The coach who gives a launch "this quarter" ships it in week thirteen. The task did not grow. The container did, and the work rose to meet the rim.

Parkinson's law is the name for this. Most people know it as a joke about deadlines. The essay it comes from was about something sharper, and the research that followed shows the trap has a second jaw most operators never see.

This article covers what the 1955 essay actually argued, the popular misreading, why the law bites owner-operators harder than employees, the planning fallacy that compounds it, and a two-week counter-protocol built on time-boxing, deadlines with a cost, a done list and a Friday hard stop.

What the 1955 essay actually said

The essay was written by the naval historian C. Northcote Parkinson and published in The Economist in 1955. It is satire with a straight face, and its first line is the only part most people have read. The standard summary gives it as: "Work expands so as to fill the time available for its completion."

Parkinson offered that line as a "commonplace observation" and then moved on. The bulk of the essay is about something else: the growth of bureaucracies regardless of workload. His examples were the British Admiralty and the Colonial Office, whose staff grew while the number of ships and colonies they administered fell. The Colonial Office, he showed, "had its greatest number of staff when it was folded into the Foreign Office due to a lack of colonies to administer."

He explained the growth with two laws, which he named "The Law of Multiplication of Subordinates" and "The Law of Multiplication of Work," and stated as two forces: "An official wants to multiply subordinates, not rivals," and "Officials make work for each other." He put the resulting growth at 5 to 7 percent a year "irrespective of any variation in the amount of work (if any) to be done."

Then he wrote a formula. "In any public administrative department not actually at war the staff increase may be expected to follow this formula," he said, and gave an equation whose variables include the number of officials who want promotion, the hours spent preparing internal memoranda, and, in the denominator, the "number of administrative files actually completed."

Read that denominator twice. In Parkinson's mock-science, the only variable that measures real output is the one everything else gets divided by. That is the essay's actual thesis, and it is not about procrastination. It is about systems that generate work for their own sake.

The popular misreading

The summary notes that the first finding "has been called the personal version of the law and the second, which is not stated explicitly, the organizational version," and that "It is the first sense which is now most commonly called Parkinson's Law."

So the personal version won. It spawned corollaries, two of which are worth knowing because they describe operator behaviour precisely. The Stock-Sanford corollary: "If you wait until the last minute, it only takes a minute to do." And the Asimov corollary: "In ten hours a day you have time to fall twice as far behind your commitments as in five hours a day."

The misreading is to treat all of this as a wry comment on laziness. Parkinson was not describing lazy people. His officials were busy. They were writing memoranda to each other, reviewing each other's drafts, and hiring help to cope with the volume they created. The work was real and the output was flat.

That is the version that applies to an operator. You are not idle when the proposal takes all morning. You are researching a detail the client will not read, reformatting a table, answering two messages that arrived because you were available, and comparing three tools for a problem you did not have at 8 a.m. You are a department of one, making work for yourself.

Why the law bites operators hardest

An employee has a container built by someone else: a manager, a sprint, a meeting that ends. An owner-operator builds every container personally, and nothing pushes back when the walls move.

Three features of the operator's position make the law worse than it was for Parkinson's civil servants.

• No external deadline. The launch date, the publishing cadence, the price increase: all of them are yours to set and yours to quietly move. A deadline with no one on the other side is an estimate.
• Multiplication of subordinates has become multiplication of tools. The modern official does not hire two assistants. The operator adds a subscription, a template library and an automation that needs maintaining. Each one is a subordinate that makes work for the others. The decision fatigue protocol covers what that does to judgement by mid-afternoon.
• The work feels like progress. Memoranda felt like governing. Research, formatting and tool comparison feel like building. Both fill the container without moving the denominator.

Seneca wrote the operator's version two thousand years early. "It is not that we have a short space of time, but that we waste much of it," he says in On the Shortness of Life. And in chapter nine, the specific failure: "postponement is the greatest waste of life; it deprives them of each day as it comes, it snatches from them the present by promising something hereafter."

Postponement in Seneca's sense is not laziness either. It is the busy person who keeps "making ready to live." The quarter that is always about to be the one where the real work starts.

Training is the only block in most operators' weeks that does not obey the law. A session ends when the sets end. Nobody has ever let five sets of five expand to fill a morning. That is not because lifting is easier than writing a proposal. It is because the unit of work is fixed before the session starts, which is exactly the fix for everything else.

The second jaw: the planning fallacy

Parkinson's law describes what happens after you set the time. The planning fallacy describes how badly you set it in the first place.

The planning fallacy, first proposed by Kahneman and Tversky in 1979, is "a phenomenon in which predictions about how much time will be needed to complete a future task display an optimism bias and underestimate the time needed." The defining feature is that it survives experience: "people recognize that their past predictions have been over-optimistic, while insisting that their current predictions are realistic."

The study most often cited is Buehler, Griffin and Ross, 1994. As summarised in the reference above: 37 psychology students were asked to estimate how long it would take to finish their senior theses. The average estimate was 33.9 days. Asked for a best case, "if everything went as well as it possibly could," they averaged 27.4 days. Asked for a worst case, "if everything went as poorly as it possibly could," they averaged 48.6 days. The average actual completion time was 55.5 days, and about 30 percent finished in the time they had predicted.

Read those numbers as an operator. The real result was worse than the students' worst case. Not their average guess. Their worst case. And a 1997 survey of Canadian taxpayers found they mailed their forms about a week later than they predicted, despite having "no misconceptions about their past record."

Put the two laws together and the trap closes from both sides. You estimate a task at a day because you are imagining the best case. Then you give it a day, and the work expands to fill it, and then past it. The fix has to address both: estimate from history, not imagination, and then build containers that do not stretch.

The operator's counter-protocol

Four tools. None of them require buying anything, which matters, because a new tool is a new subordinate.

1. Time-box the work, do not list it

A to-do list has no container. A time block does. Every piece of real work gets a start, an end and a defined output before you begin, and the block ends when the clock says so, not when the work feels finished. Time blocking is the full method; the rule that matters here is that the end time is the deliverable's deadline, not a suggestion.

Size blocks with the planning fallacy in mind. Take your honest estimate and apply your own historical ratio. If you do not know your ratio yet, the thesis study gives a reference: actual time ran roughly 1.6 times the average estimate. Measure your own within two weeks and replace it.

2. Give every deadline a cost

A deadline you can move without anyone noticing is not a deadline. Attach a consequence that exists outside your head: a client expects the draft at 2 p.m.; the call is booked before the deck is written; the newsletter goes out Thursday at 7 a.m. whether the third section is polished or not; a peer gets a message with your commitment and a date.

The consequence does not have to be severe. It has to be external. Parkinson's officials had no external check on their memoranda, and neither does an operator who sets private deadlines.

3. Keep a done list

The to-do list measures containers. The done list measures the denominator: what actually shipped, sent, published or closed today. Write it at the end of each day in one line per item, with no process entries. Researched pricing does not go on it. Sent the pricing page to three clients does.

After a week, the done list tells you the truth the to-do list hides. If the days are full and the list is short, you have found your Colonial Office.

4. The Friday hard stop

Set a time on Friday when the working week ends, with no exceptions for one more thing. The hard stop does for the week what the block does for the day: it fixes the container, so the week's work has to fit inside it rather than leak into the weekend.

It also forces the planning fallacy into the open. Anything that did not fit by the hard stop was mis-estimated, and the Friday review is where you record by how much. The compound operator's weekly schedule shows where the stop sits in a full week.

The two-week install

Do not try to fix the law in a day. Measure first, then constrain.

Days 1 to 3: measure the gap

1. Before each significant task, write your estimate in minutes.
2. After it, write the actual time. No judgement, just the two numbers.
3. On day three, divide total actual by total estimate. That ratio is yours. Most operators who do this honestly find it is well above one.

Days 4 to 7: build the containers

1. Time-box every task over 30 minutes. Multiply your estimate by your ratio to set the block length.
2. Start the done list. One line per completion, written at the end of the day.
3. Pick one task you have been "making ready" for and give it a block this week with a fixed end.

Days 8 to 14: add the costs

1. Attach an external consequence to every deadline that matters this week. Send the commitment to the person who will receive the work.
2. Set the Friday hard stop and tell one person what time it is.
3. On Friday, review: estimate versus actual for the week, the done list against the to-do list, and what you will stop making ready for and start doing next week. The procrastination protocol covers the tasks that keep sliding even inside a block.

Frequently asked questions

What is Parkinson's law?

Parkinson's law is the observation that "Work expands so as to fill the time available for its completion." It comes from a satirical 1955 essay in The Economist by C. Northcote Parkinson. The essay offered that line as a commonplace and spent most of its length on a second finding: that bureaucracies grow regardless of the work to be done.

Who came up with Parkinson's law?

C. Northcote Parkinson, a British naval historian, published the essay in The Economist in 1955 and expanded it into the 1957 book Parkinson's Law, or The Pursuit of Progress. He drew on his experience of the British Civil Service, using the Admiralty and Colonial Office as examples of staff growing while ships and colonies declined.

Is Parkinson's law scientifically proven?

The essay was satire, and its formula for bureaucratic growth was mock-science. The personal version, that work stretches to fill the time allotted, is an observation rather than a tested law. The related planning fallacy is well documented: people reliably underestimate how long tasks will take, and the two effects together explain why operator deadlines slip.

How do you beat Parkinson's law?

Fix the container before you start. Time-box tasks with a defined end and output, size the box using your own measured ratio of actual to estimated time, attach an external consequence to every deadline that matters, keep a done list that records completions rather than activity, and set a Friday hard stop so the week cannot expand into the weekend.

What is the difference between Parkinson's law and the planning fallacy?

The planning fallacy is the tendency to underestimate how long a task will take; in one well-known study, students' actual completion time exceeded even their worst-case estimate. Parkinson's law describes what happens after the estimate: work expands to fill whatever time is allotted. One sets the container too small in theory; the other stretches it in practice.

Fix the container, not the worker

Parkinson's real target was never the individual. It was a structure in which busy people produce flat output because nothing fixes the unit of work. An operator is that structure in miniature: hiring tools instead of subordinates, writing to themselves instead of memoranda, and moving deadlines nobody else can see.

The answer is the one a lifter already knows. Decide the sets before the session. End when they are done. Record what you lifted, not how long you were in the gym. Then do it again Monday.

The free 5-Day Stoic Operator Challenge installs that structure across the whole day: a training block that ends on time, a Stoic review that records what was actually done, and a daily rhythm with fixed edges. Five days is enough to see how much of your week was container, and how much was work.