You give yourself the whole afternoon to finish a presentation. You start after lunch, fiddle with fonts, reread the same slide twice, answer a few emails, go make coffee, and suddenly it is 5:30 PM and the deck is just barely done. The next week, the same presentation gets thrown at you with a 90-minute warning before a client call. Somehow, you deliver it, and it is not dramatically worse than the four-hour version.
If you have ever lived through that pattern, you have experienced Parkinson's Law in action. Coined in 1955 by British historian Cyril Northcote Parkinson in a satirical essay for The Economist, the law states: "Work expands so as to fill the time available for its completion." Give a task an hour, it takes an hour. Give it a day, it takes a day. The work itself did not grow — the container did.
Most productivity advice tries to help you work harder inside whatever container you choose. Parkinson's Law suggests something more radical: the container itself is the problem. Shrink the container, and a surprising amount of the "work" turns out to have been padding, polish, and procrastination all along. This article explains why Parkinson's Law happens, the psychology behind it, and how time blocking turns it from a productivity tax into a productivity tool.
Parkinson was writing about bureaucracies, not personal productivity, but the underlying mechanism is the same wherever it appears. Several forces push tasks to consume more time than they need:
Notice that none of these are signs of laziness or poor skill. They are the natural response of a rational mind to an open-ended deadline. Remove the constraint, and expansion is the default.
The counterpart to Parkinson's Law is the well-documented phenomenon that deadlines — even arbitrary ones — dramatically compress work. A 2002 study by Dan Ariely and Klaus Wertenbroch found that students who set their own intermediate deadlines for a writing assignment performed significantly better than students with only a final deadline. The self-imposed deadlines were not enforced by grades, yet they still worked, because having a specific target time is what matters, not the consequence of missing it.
This is why a 30-minute window before a meeting often produces more output than a three-hour "open" block. The meeting is an immovable wall. Your brain, sensing a real constraint, drops the perfectionism, skips the warm-up, narrows the scope, and simply gets the task done. The quality is usually surprising: not perfect, but not meaningfully worse than the three-hour version.
Parkinson's Law and the deadline effect are the same principle viewed from two directions. Open time invites expansion; constrained time forces compression. Time blocking is how you convert the open, expanding day into a series of constrained, compressing blocks — without needing external pressure to do it.
Time blocking is essentially a tool for manufacturing artificial deadlines. Every block has a start time and an end time, which means every task has a finite container. You are no longer saying "I will finish the report today." You are saying "I will work on the report from 9:00 to 10:30." That distinction is small on paper but enormous in practice.
When you schedule a 90-minute block for a task that could, in theory, consume an entire afternoon, you are betting that 90 minutes will be enough for the version that actually matters. Most of the time, you are right. The presentation does not need four hours — it needs the 90 minutes of focused work that would have happened anyway, minus the three hours of expansion around it.
If 90 minutes turns out to be too little, you learn something valuable: either the task was genuinely bigger than estimated, or the block needs to be split. Both outcomes are better than the default, which is silently letting the task consume whatever you give it.
A to-do item has no end time, only a beginning. A time block has both. That end time acts as a miniature deadline, and deadlines trigger the brain's natural tendency to focus and prioritize. You stop polishing the same sentence because the clock is ticking. You skip the font debate because the block ends at 10:30 and there is another block at 10:45. You stop checking whether you missed an email because the block is about the report, not the inbox.
Without time blocks, you can drift from the report to your inbox to Slack to the report again without ever feeling the cost. With blocks, switching means leaving the current block incomplete, which registers as a small failure. That friction is exactly what you want. It is not punishment — it is a signal that the task you just wandered away from is the one you committed to.
One of the quiet gifts of time blocking is that it forces you to estimate how long things take. Most people are terrible at this, because they have never had to put a number on it. When you block 45 minutes for "clear the inbox" and it turns out to take 90, you learn something real about how your time gets consumed. Over a few weeks, your estimates get sharper, and your schedule starts matching reality. None of this learning happens in a world of open-ended afternoons.
A calendar has a fixed number of hours. When you time block, you cannot pretend all your commitments fit — they either do or they do not. This forces the trade-offs that an open to-do list lets you avoid. You see, concretely, that adding the report means cutting something else. That visibility is what turns a wishful list into a realistic plan.
The trick is to make blocks short enough to compress the work, but not so short that you produce junk. Here is a practical framework.
If your first instinct is "this will take two hours," block 90 minutes instead. Most tasks are 75% work and 25% expansion; removing the expansion is usually painless. If 90 minutes leaves you genuinely short, you can extend it — but start tight. It is easier to grow a block than to recover hours that expansion already stole.
These lengths align with ultradian rhythms, the roughly 90-minute cycles of focus and fatigue your brain runs on. A 45-minute block fits tasks that benefit from tight compression: emails, reviews, quick edits, short meetings. A 90-minute block fits tasks that need a warm-up but still benefit from a hard cap: writing, coding, design, analysis. Blocks longer than 120 minutes almost always expand to consume the extra time without producing proportionally more output.
Before the block starts, write down what "finished" looks like. Not "work on the report" — "draft sections 1 and 2, bullet points only, no polish." A vague task will always expand because there is no clear point at which to stop. A specific definition lets you hit it, close the block, and move on without second-guessing.
Schedules need some slack, but most people over-buffer in ways that invite expansion. A 5 to 10-minute gap between blocks is enough to handle bathroom breaks, water refills, and quick context switches. A 60-minute buffer is not a buffer — it is an invitation for the previous task to consume it. If you need a real break, schedule it as a break block, with its own start and end.
The mere presence of a visible countdown changes behavior. It is the same reason chess players with a clock play faster than chess players without one: they can see the time disappearing, and the brain responds to that visibility. A block on a calendar is useful. A block with an actual timer ticking down is much harder to ignore.
Not every task should be compressed. Some work genuinely benefits from extra time — strategic thinking, creative exploration, complex problem solving, learning something new. Forcing a 45-minute cap on "figure out the architecture of the new system" would produce a shallow answer. Parkinson's Law does not mean shorter is always better; it means that time should match the task instead of the other way around.
The question to ask is: what kind of task is this?
Mixing these categories in your schedule protects both productivity and quality. Compress the executional work; give the exploratory work room to breathe; batch the routine. Parkinson's Law is a lever you apply selectively, not a universal rule.
The whole premise of DayChunks is converting open time into constrained blocks. Every feature is built around making Parkinson's Law work for you instead of against you.
Parkinson's Law is not a curse you have to fight every day — it is a feature of how your brain relates to time. Give the brain open time, and it will fill it. Give it constrained time, and it will compress the work to fit. Time blocking is the mechanism that lets you choose which of those happens.
The practical test is simple. Pick a task you would normally give an afternoon to. Block 90 minutes for it tomorrow. Start a timer. Define what "done" looks like before you begin. When the timer ends, stop, regardless of polish. Compare the result to your usual afternoon version. Most people find the 90-minute version is not dramatically worse — and the two and a half hours you reclaimed are now available for something else.
Do that ten times and your relationship to time changes. You stop thinking of tasks as "how long until it is done" and start thinking "how long should this deserve." That shift is what Parkinson's Law has been trying to teach you all along.
DayChunks is a free, visual time-blocking tool. No sign-up required. Set tight blocks, run the timer, and let the deadline effect do the heavy lifting.
Try It with DayChunks