Parkinson's Law: The Deadline Decides the Duration

Give someone a week to write a two-page report and it will take a week. Give the same person a month and it will take a month. The report will usually be about as good either way.

Cyril Northcote Parkinson, a British naval historian, put this into a sentence in 1955: work expands to fill the time available for its completion.

He was writing partly as satire, having observed that the number of administrators in the Royal Navy kept growing while the number of ships fell. But the observation about time has outlived the joke, because anyone who has ever had a deadline recognises it immediately.

The interesting question is not whether it happens. It is why — because understanding the mechanism tells you when you can use it and when trying to will backfire.

Where the extra time actually goes

The uncharitable explanation is that people slack off when they have time. That is occasionally true and mostly wrong. Watch what actually happens on a long deadline and the time disappears into things that all feel reasonable.

Standards rise to fill the space. With a month available, a two-page report seems like it should be well researched. So you read more sources. You produce a draft, then improve it. Under a one-week deadline, the same person writes something serviceable and ships it — and often cannot tell you what the extra three weeks would have added.

Starting gets delayed. With plenty of time, there is no urgency today. The work compresses into the final stretch anyway, which means the generous deadline bought procrastination rather than quality.

More people get involved. A longer timeline leaves room for another round of review, another stakeholder, another opinion. Each addition is individually defensible and collectively expensive — and coordination costs grow faster than the number of participants.

Decisions get revisited. Time allows reopening settled questions. Sometimes that improves the outcome. Often it produces a different answer of similar quality, having consumed a week.

None of these is laziness. They are what "having time" causes, and they happen to conscientious people especially — because a conscientious person with spare time will find a way to use it.

Using it deliberately

The practical value of the law is that it works in reverse. If work expands to fill time, then constraining time constrains the work — and the quality loss is usually much smaller than expected.

Set deadlines shorter than feel comfortable. Not impossible, just tight. The discomfort is the mechanism working: it forces prioritisation, which is what most work lacks.

Give tasks a time box rather than a completion condition. "Spend two hours on this and show me where you get to" produces a different, usually better result than "work on it until it's ready," because the second has no natural end.

Shorten meetings and watch nothing break. A meeting scheduled for an hour uses an hour. Scheduled for twenty-five minutes, the same decision usually gets made. Meetings are the purest demonstration of the law, because the agenda rarely changes with the length.

Ship in smaller pieces. Frequent small deliveries impose natural deadlines and prevent the long unhurried middle where scope quietly grows. This is also why Gall's Law advice — build something small that works, then extend it — tends to finish faster than a single large effort.

Beware of buffers that become the plan. Adding contingency time is sensible, but if the buffer is visible it gets absorbed. Some teams keep the schedule tight and hold the buffer separately rather than distributing it into each task.

Where shorter deadlines stop helping

The law is real, and it is also used to justify some genuinely bad management, so the boundary matters.

Some time is spent learning, not polishing. For unfamiliar work, the early period is figuring out what the problem even is. Cutting that does not remove gold-plating; it removes understanding, and you get a fast confident answer to the wrong question.

Some quality does not degrade gracefully. Trimming polish from a report is fine. Trimming testing from something safety-critical, or verification from something financial, produces failures rather than a slightly rougher product. The law tells you effort expands; it does not promise the expansion was worthless.

Sustained compression stops working. A tight deadline is a useful forcing function occasionally. Permanent tight deadlines produce accumulated shortcuts — technical debt in software, deferred maintenance everywhere else — and the bill arrives later with interest. The speed was borrowed.

People are not interchangeable with time. Halving a deadline and doubling the team rarely halves the duration, because communication overhead grows with headcount. A late project given more people usually gets later.

Used well, Parkinson's Law is one of the highest-leverage things you can know about scheduling, because it says something genuinely useful: the amount of time you allocate is not a neutral measurement of how long something takes. It is one of the inputs that determines it.