Parkinson's Law at Work: Why Tasks Expand and How to Shrink Them

Parkinson's Law says work expands to fill the time available for its completion — give a two-hour task a full day and it will quietly take the day. The fix is to give work less room: set a tight, tracked time limit before you start, and base that limit on what the task actually took last time, not on what feels comfortable.

Quick answer

Parkinson's Law comes from a satirical 1955 essay in The Economist, but the personal version holds up: lab studies since the 1960s show that people given excess time for a task spend more of it working — without producing proportionally better results. Why do tasks expand? Because a deadline acts as an implicit goal, and a generous one invites padding, polishing, and procrastination. The counter-move: track how long tasks really take, then timebox them slightly under your median. For most well-defined work, the quality stays; the bloat goes.

What Parkinson's Law actually says

A satire about bureaucracy, not a law of physics

Cyril Northcote Parkinson opened his 1955 essay in The Economist with the now-famous line: "Work expands so as to fill the time available for its completion." His illustration was an elderly lady of leisure who spends an entire day writing one postcard — an hour finding the card, an hour hunting for spectacles, an hour and a quarter composing — while a busy person does the same job in three minutes.

None of this was about your to-do list. As Cal Newport points out in his close reading of the original, Parkinson was documenting bureaucratic growth: the British naval bureaucracy kept expanding even as the navy it served shrank. He blamed two forces — officials want to multiply subordinates, not rivals, and officials make work for each other. Growth, he showed, can be independent of the work to be done.

The personal version everyone quotes

Tim Ferriss popularized the individual reading in 2007: a task swells in perceived importance and complexity in relation to the time allotted to it. Newport, initially skeptical, came around on the practical advice — after constraining his own schedule, he found the restrictions didn't reduce how many projects he made progress on. If anything, he shipped more than colleagues working longer hours.

Why tasks expand

The personal version isn't just folklore, though. In a 1967 replication of the "excess time effect", participants who were allotted excess time for a task spent significantly more time working on it than participants given the minimum — the available time, not the work itself, set the pace.

At your desk, three mechanisms produce the same result. A deadline works like an implicit goal: a far-off one signals "no urgency," so the task loses every priority contest until it's close. That's the engine behind most procrastination patterns — the work happens in the final stretch regardless of how much runway you had. Spare time gets absorbed by scope creep and polishing — another round of edits, a nicer slide, a third option nobody asked for. And padded estimates feel safe, but the padding rarely comes back as free time. It just becomes part of the task.

For a freelancer, the cost is concrete. A deliverable estimated at six billable hours that drifts to ten isn't 67% more value for the client — it's four hours you can't invoice with a straight face, and can't spend shipping anything else.

How to shrink tasks

Timebox before you start

Timeboxing — fixing a maximum duration for a task before you begin — is the most direct counter. In a Harvard Business Review analysis of 100 productivity techniques, timeboxing ranked first. It's Parkinson in reverse: a tight container forces the essential version of the task to show up early.

Set the box from data, not optimism. People underestimate task duration by 20-40%. So track a few instances of the task, find your median actual time, then set the timebox slightly under it. A 90-minute box for a report that historically takes two hours creates useful pressure; a 30-minute box just creates a missed deadline.

Give your deadlines teeth

Behavioral research by Dan Ariely and Klaus Wertenbroch found that self-imposed deadlines improve performance over no deadlines — but they work best when they're binding and visible, and external deadlines still beat them. So borrow some externality. Tell the client the draft arrives Thursday, book the review meeting before the work is done, or commit a delivery date in writing — a deadline only you know about is the easiest one to renegotiate.

Pair the limit with a technique

A timebox needs a home and a rhythm. Time blocking gives each box a fixed slot on the calendar, so "write proposal, 90 minutes" becomes Tuesday 9:00-10:30 rather than a hopeful intention. For tasks under an hour, a 25-minute Pomodoro session works as a micro-timebox: one focused session, one clear stopping point, repeat only if the task earns it.

When to use it (and when to skip it)

Tight timeboxes work best on well-defined execution work: admin, email, invoicing, routine client deliverables, status updates — anything where the shape of "done" is clear and the main variable is how long you allow it to sprawl.

Loosen the constraint for creative and research-heavy work. Drafting a brand strategy or debugging a gnarly architecture problem benefits from iteration and sleep cycles; compressing it past a point trades quality for speed. Studies of time pressure show moderate constraints sharpen focus and decision-making, while heavy pressure pushes people toward fast, habitual, lower-quality choices.

And be honest about the data problem: if you don't know what a task actually takes, you can't set a sane limit. Measure first, then tighten.

How Pomlo fits in

You can't shrink a task until you know its real size — and that's the part Pomlo handles. Pomlo is a beautifully simple time tracker for iOS, Android, and the web, built for freelancers, indie hackers, and small teams who want focused work and clean records of it.

Three Pomlo features map directly onto this problem. Time tracking with one-tap start/stop captures what each task actually took, so your next timebox comes from your own median, not a guess. Focus sessions turn the timebox into a live, running container — start a 25- or 90-minute session and the limit is real, not theoretical. Reports show where the week actually went, including the gap between what you estimated and what you logged — the exact number you need to set tighter, fairer limits next week.

Download Pomlo on the App Store or Google Play and find out what your tasks really take.

Frequently Asked Questions

Is Parkinson's Law scientifically supported?

Partially. The original 1955 essay was satire about bureaucratic growth, but lab studies since 1967 have replicated the "excess time effect": people given more time for a task spend more time on it without producing proportionally better work. Treat it as a reliable tendency, not a physical law.

Should every task get the shortest possible deadline?

No. Moderate constraints sharpen focus, but extreme ones degrade quality — especially for creative or research-heavy work. A practical rule: set the deadline slightly tighter than your average actual completion time, which you only know if you track it.

What's the difference between timeboxing and time blocking?

Time blocking reserves calendar slots for kinds of work; timeboxing assigns a fixed maximum duration to a specific task before you start. Timeboxing is the more direct counter to Parkinson's Law because the limit travels with the task wherever it lands on your calendar.

How do I estimate realistic timeboxes?

Start from data, not optimism. People routinely underestimate task duration by 20-40%. Track a few weeks of real task times, take your median per task type, set the timebox slightly below it, and keep a buffer in the day for the unexpected.