There is a strange thing that happens when you give someone two weeks to complete a task that should take two days.
It takes two weeks.
Give them a month, and somehow it becomes a month-long project.
This phenomenon has a name: Parkinson’s Law.
“Work expands so as to fill the time available for its completion.”
The observation was made by British historian and author C. Northcote Parkinson in 1955. Although Parkinson originally presented the idea somewhat humorously, it describes something nearly everyone has experienced.
The amount of work involved in a task is often surprisingly flexible.
And the deadline itself can determine how complicated the work becomes.
The Two-Hour Job That Takes All Day
Imagine you need to prepare a presentation.
If the presentation is due tomorrow morning, you might spend two hours putting together the slides, review them once, and call it finished.
But suppose the same presentation is due three weeks from now.
Suddenly there is time to research alternative templates.
Maybe the graphics could be improved.
Perhaps the order of the slides should change.
You rewrite the introduction.
Then rewrite it again.
Someone suggests adding another section.
A meeting is scheduled to discuss the presentation.
After the meeting, the presentation needs revisions.
Three weeks later, you finally finish.
The result might be slightly better than the version you could have created in two hours.
But probably not 60 hours better.
The available time didn’t simply allow more work.
It created more work.
Where Parkinson’s Law Came From
C. Northcote Parkinson introduced the idea in an essay published in The Economist in 1955.
His original target wasn’t personal productivity.
It was bureaucracy.
Parkinson noticed that bureaucratic organizations had a tendency to grow even when the amount of actual work they were responsible for declined.
More administrators created more communication.
More communication required more coordination.
More coordination required more administrators.
The organization could therefore become increasingly busy without necessarily becoming increasingly productive.
Parkinson was satirizing government bureaucracy, but the underlying observation applies remarkably well to modern organizations.
Especially large ones.
Complexity Expands Too
One of the most interesting consequences of Parkinson’s Law is that it isn’t just time that expands.
Complexity does too.
Give a technical team three days to solve a problem and they may implement the simplest solution that works.
Give the same team six months and the discussion may suddenly include:
- architecture committees
- design documents
- multiple proof-of-concept environments
- new platforms
- additional tooling
- governance requirements
- dashboards
- reporting
- recurring status meetings
Some of those things may be useful.
But each one also creates additional work.
Eventually the infrastructure surrounding the solution can become more complicated than the original problem.
This is how organizations sometimes spend six months solving problems that a competent engineer could have solved in an afternoon.
Meetings Are Parkinson’s Law in Its Purest Form
Calendar meetings provide one of the easiest demonstrations.
Schedule a meeting for an hour.
How long does it usually last?
About an hour.
Schedule the same meeting for 30 minutes and something interesting happens.
People get to the point faster.
The introductions become shorter.
Tangents get cut off.
Decisions happen sooner.
The discussion somehow compresses itself into the available space.
This raises an uncomfortable question:
If the meeting accomplished essentially the same thing in 30 minutes, what exactly was happening during the other 30 minutes?
The answer is often simply that the time existed.
Deadlines Change Behavior
Deadlines are usually viewed as administrative constraints.
But deadlines also change the way people think.
A distant deadline encourages exploration.
A close deadline forces prioritization.
When time becomes scarce, people begin asking better questions.
What actually needs to be done?
What can be eliminated?
What is necessary for this to work?
What can wait?
What would happen if we simply didn’t do this part?
These questions are powerful because much of the work inside organizations isn’t strictly necessary.
It accumulated.
Someone requested a report five years ago, so the report still gets produced.
Someone created a weekly meeting, so the meeting still happens.
Someone developed a twelve-step approval process, so everyone continues following twelve steps.
Organizations rarely stop to ask whether the original reason still exists.
The Difference Between a Deadline and a Time Budget
There is another way to think about Parkinson’s Law.
Instead of asking:
“When should this be finished?”
Ask:
“How much time is this worth?”
Those are very different questions.
Suppose you need to research a new piece of software.
You could easily spend an entire day reading reviews, watching videos, comparing features, and building spreadsheets.
But perhaps the decision simply isn’t important enough to justify eight hours.
So instead you decide:
I will spend 45 minutes researching this and then make a decision.
That changes the problem.
You have created a time budget.
Time budgets force the amount of effort to remain proportional to the importance of the decision.
Without them, trivial decisions can consume enormous amounts of time.
Perfectionism Loves Unlimited Time
Parkinson’s Law also has a close relationship with perfectionism.
There is almost always something else that could be improved.
Another paragraph could be rewritten.
Another test could be performed.
Another source could be consulted.
Another feature could be added.
Another person could review the work.
Theoretically, improvement could continue indefinitely.
At some point, however, additional effort produces almost no additional value.
The difficult skill isn’t producing perfect work.
It is recognizing when the work is good enough for its purpose.
That doesn’t mean accepting poor quality.
It means recognizing diminishing returns.
Spending four hours improving something by 50 percent may be worthwhile.
Spending another four hours improving it by 2 percent probably isn’t.
Parkinson’s Law in IT
Technology organizations may be particularly vulnerable because technical work can expand almost infinitely.
Consider a simple request:
Deploy a new server.
That could mean:
Create the VM, configure the operating system, patch it, secure it, install the application, test it, and hand it over.
Or it could become:
Evaluate the virtualization architecture.
Review naming standards.
Update the provisioning process.
Modify the Terraform modules.
Create a new CI/CD pipeline.
Update monitoring.
Build dashboards.
Review backup policies.
Update documentation.
Schedule an architecture review.
Schedule a security review.
Schedule a change-management review.
None of those activities are inherently unreasonable.
The problem is that organizations often lose the ability to distinguish between work required to accomplish the objective and work generated by the organization itself.
Eventually the process becomes the product.
Artificial Constraints Can Improve Work
This leads to a counterintuitive idea.
Sometimes the solution to having too much work is not having more time.
It is having less.
Constraints force decisions.
A 30-minute meeting requires an agenda.
A one-page proposal requires clarity.
A two-day deadline discourages unnecessary features.
A small budget forces prioritization.
A limited engineering team discourages architectural extravagance.
Unlimited resources sound ideal, but limits often produce simpler solutions.
And simple solutions have an enormous advantage:
They are easier to understand, maintain, troubleshoot, and replace.
But Parkinson’s Law Can Be Misused
There is an obvious danger here.
If reducing a deadline from three weeks to one week increases efficiency, management might conclude that reducing it to three days will increase efficiency even further.
Eventually every project becomes an emergency.
That isn’t productivity.
It is organizational dysfunction.
Some work genuinely requires time.
Research requires exploration.
Engineering requires testing.
Writing requires revision.
Complex systems require careful design.
And constantly operating under artificially compressed deadlines eventually produces mistakes, technical debt, and burnout.
The lesson of Parkinson’s Law isn’t:
Give people impossible deadlines.
It is:
Don’t automatically assume that more available time produces proportionally better work.
Often it simply produces more activity.
Ask a Different Question
When starting a project, most people ask:
How long will this take?
Parkinson’s Law suggests asking another question first:
How long should this take?
The distinction matters.
The first question allows the task to define the schedule.
The second forces you to consider the value of the task before deciding how much of your life it deserves.
That applies to projects.
It applies to meetings.
It applies to research.
It applies to decisions.
And it applies to organizations themselves.
Because work has an extraordinary ability to reproduce.
Give it enough room and it will create meetings, reports, processes, approvals, committees, dashboards, documentation, and eventually entire departments devoted to managing the work created by the original work.
Sometimes those things are necessary.
But sometimes the most productive thing you can do is give the task less room to grow.
Set a reasonable limit.
Do the important work.
Finish it.
And move on.