Table of contents
- A law that began as a joke
- Why work stretches to fill the deadline
- Student syndrome and hidden padding
- What experiments say about deadlines
- When shorter deadlines don't work
- Four ways to take back control
- Its little brother: the law of triviality
- A one-week experiment to try
- To wrap up: you can't beat Parkinson with willpower
- Keep your deadlines in view with FluidOps
- Frequently asked questions
A law that began as a joke
In November 1955, the British historian Cyril Northcote Parkinson opened an article in The Economist with this sentence: "Work expands so as to fill the time available for its completion." It was a satire of British administration, not the result of a lab experiment.
His proof is a delight. He compared the Admiralty with the fleet it was supposed to run: between 1914 and 1928, the number of Admiralty officials grew by about 78%, while the number of capital ships fell from 62 to 20. Fewer boats, more desks. His explanation has two parts: an official wants more subordinates, not more rivals, and those subordinates make work for each other. Work doesn't need to grow for the staff to grow.
Parkinson turned it into a book in 1957. But what project managers kept is the first sentence, taken literally: a two-hour task, given two weeks, ends up taking the two weeks.
Why work stretches to fill the deadline
The "law" itself has never been tested directly. A solid theoretical framework does explain what we see, though: Temporal Motivation Theory (Steel & König, 2006; Steel, 2007). Its idea is simple. Our urge to start a task rises with how likely we think we are to succeed and how much the task is worth to us, and falls with the delay before the payoff and with our taste for instant rewards.
In practice, while the deadline is far away, the task carries little weight in today's choices: there is always something more urgent. It only becomes attractive when the delay shrinks, hence the last-minute surge of motivation everyone knows.
An example. On Monday you're asked for a two-page summary due in two weeks. No rush, so it slips behind the urgent stuff. A first draft appears the following Monday, gets tweaked on Wednesday, reread on Thursday and sent on Friday at 5 pm. You didn't work more than needed: you worked more spread out, and the summary sat in the back of your mind for two weeks. Meanwhile the available time filled up with perfectionism, second-guessing and small side tasks.
This drift also feeds procrastination, a mechanism we detail in Why Do We Procrastinate on Projects?
Student syndrome and hidden padding
The engineer Eliyahu Goldratt, who created the critical chain method, put a name on what happens just before a deadline: "student syndrome" (Goldratt, 1997). You know you have two weeks, you start the night before. Anyone who has crammed for an exam knows the feeling.
On projects it comes with a quieter trap. When asked for an estimate, everyone slips in a safety margin "just in case". Nothing shameful there. The problem is that the margin gets swallowed by Parkinson's Law (the work spreads out), and whatever is left is burned by student syndrome (you start late). Goldratt draws an asymmetry from this: delays pass on to the next task, while early finishes get lost, because nobody benefits from announcing they're done early.
His answer is to strip the margin out of each task and pool it into a single buffer at the end of the chain. Everyone works to a realistic but tight estimate, and the buffer absorbs the surprises. Its consumption becomes a health indicator for the project. Even if you never adopt the method, the question is worth asking: where are your margins hiding, and who can use them up without anyone noticing?
What experiments say about deadlines
Studies that test Parkinson directly are rare, but research on deadlines has plenty to say. In a series of experiments, Dan Ariely and Klaus Wertenbroch (2002) compared participants asked to proofread texts, depending on how deadlines were set. Those given evenly spaced deadlines did better (more errors caught, fewer late submissions) than those with a single final due date. Those who chose their own deadlines landed in between.
Two practical takeaways. First, intermediate milestones help, even when you set them yourself. Second, they help a little less than ones someone else imposes: committing in front of other people (a team, a client, a colleague) does something a personal calendar doesn't quite do.
When shorter deadlines don't work
It's tempting to conclude that you should simply squeeze everything. It isn't that simple, and three cases deserve some caution.
- The unrealistic deadline. When you've misjudged how long something takes, a short deadline doesn't create momentum, it creates stress. And we are poor estimators of our own tasks: Buehler, Griffin and Ross (1994) show that people underestimate how long they need, even when they know their past projects ran over. For a clearer view, read our article on estimation biases.
- Deep work. A 90-minute block is for making progress on a subject, not necessarily for finishing it. Boxing the session rather than the outcome keeps you honest about what a morning can produce.
- The deadline with no stakes. A date nobody checks eventually triggers nothing. A short deadline needs someone looking over your shoulder, however lightly.
| Type of deadline | Likely effect | Example |
|---|---|---|
| Distant and single | Late start, spread-out work, final rush | A report due in a month |
| Close and realistic | Focus, less perfectionism | A page to write in one morning |
| Close and unrealistic | Stress, sloppy work, cascading delays | A week-long file promised for tomorrow |
| Intermediate and regular | Steady progress, gaps spotted early | One chapter every Friday |
This table sums up tendencies, not laws: context and the person matter as much as the date.
Four ways to take back control
- Time-boxing. Give the task a short block of time, placed in your calendar, with a non-negotiable end. When time is up, you stop and look at what's left rather than extending "just a bit more". Scrum applies the same principle to its meetings (the daily Scrum lasts 15 minutes at most) and its cycles (Schwaber & Sutherland, 2020).
- Short sprints. Cycles of one to two weeks keep the deadline constantly in view, and a sprint never lasts more than a month. That is the whole point of the Scrum sprint.
- Intermediate milestones. A deliverable due in three weeks becomes three pieces to show every Friday. That's the Ariely and Wertenbroch lesson, and it matches the case for breaking tasks down.
- An open buffer instead of hidden margins. Announce tight estimates and set aside a visible reserve for surprises. Margins you show can be managed; margins you hide evaporate.
Its little brother: the law of triviality
In his 1957 book, Parkinson describes another mechanism, just as recognizable in meetings. A committee has to approve a ten-million-pound nuclear plant, then a 350-pound bicycle shed. The plant goes through in minutes, nobody daring to contradict the experts; the bike shed takes three quarters of an hour, because everyone has an opinion about a bike shed.
It's called the law of triviality: discussion time goes to what everyone can comment on, not to what matters. A simple remedy is to give each agenda item a time limit before the meeting, and to sort your topics with the Eisenhower matrix before getting pulled into the most visible detail.
A one-week experiment to try
Rather than taking our word for it, test it on your own tasks.
- Pick five tasks you keep dragging out, each under half a day of work.
- For each, write down how long you think it will take and when you would normally have handed it in.
- Book a block in your calendar, a little shorter than usual but doable.
- When the block ends, stop and write down what's left.
- On Friday, compare: how many tasks are done, how much real time, how much is left over?
It's not scientific proof, just your own data. If a task keeps overrunning its block, it's your estimate that needs revisiting, not your discipline.
To wrap up: you can't beat Parkinson with willpower
We rarely lack the time for a two-hour task. What we lack is a frame that makes it present today rather than in thirteen days. A short block, a visible milestone, an honest buffer: none of these asks you to be more motivated, only to take away the fog in which work loves to spread out.
Keep your deadlines in view with FluidOps
In FluidOps, break your goal into small tasks on a Kanban board, group them into short stages with a clear goal (Scrum), and keep your deadlines in sight on the project timeline (Gantt): late tasks are circled there. For the "I don't know where to start" side, our article on blank page syndrome pairs well with this one.
The free plan is €0 per month, the Individual plan €12 per month or €120 per year, and the Business plan starts at €12 per seat per month billed annually. Details are on the pricing page.
Frequently asked questions
What is Parkinson's Law?
It's the idea that work expands to fill all the time available for its completion. Formulated by the historian Cyril Northcote Parkinson in The Economist in 1955, it began as a satire of British administration.
Is Parkinson's Law scientifically proven?
Not directly: it has never been tested in a lab. But Temporal Motivation Theory (Steel, 2007) explains the phenomenon: the further away a deadline seems, the less the task motivates, and work tends to cluster near the due date.
What is student syndrome?
It's the tendency to start a task only at the last moment, even with plenty of time available. The term comes from Eliyahu Goldratt, who shows that it wastes the safety margins added to estimates.
How do you avoid Parkinson's Law on a project?
Break the work into short tasks, give each a realistic block of time (time-boxing), set evenly spaced milestones and keep a visible reserve for surprises instead of hiding margins in every estimate.
Sources
- Ariely, D., & Wertenbroch, K. (2002). Procrastination, deadlines, and performance: Self-control by precommitment. Psychological Science, 13(3), 219-224. doi:10.1111/1467-9280.00441
- Buehler, R., Griffin, D., & Ross, M. (1994). Exploring the “planning fallacy”: Why people underestimate their task completion times. Journal of Personality and Social Psychology, 67(3), 366-381. doi:10.1037/0022-3514.67.3.366
- Goldratt, E. M. (1997). Critical Chain. North River Press.
- Parkinson, C. N. (1955). Parkinson's Law. The Economist, 19 November 1955. [PDF]
- Parkinson, C. N. (1957). Parkinson's Law and Other Studies in Administration. Houghton Mifflin.
- Schwaber, K., & Sutherland, J. (2020). The Scrum Guide. scrumguides.org
- Steel, P. (2007). The nature of procrastination: A meta-analytic and theoretical review of quintessential self-regulatory failure. Psychological Bulletin, 133(1), 65-94. doi:10.1037/0033-2909.133.1.65
- Steel, P., & König, C. J. (2006). Integrating theories of motivation. Academy of Management Review, 31(4), 889-913. doi:10.5465/amr.2006.22527462