What Is Parkinson's Law?

The popular version goes like this: work expands to fill the time you give it, therefore the move is to give it less time. Set a two-hour deadline on a task that "should" take a day, feel the pressure focus you, and reclaim your week. It's a tidy story, it has the ring of a life hack, and it is half right in a way that makes the wrong half hard to see.

Parkinson's Law is the observation that a task tends to swell in perceived importance and complexity to fill whatever time is allotted to it. That's the whole claim. Notice what it is and isn't: it's a descriptive observation about how loose deadlines invite bloat — not a prescription that artificially tight ones produce quality. The leap from one to the other is where most people get hurt.

The deadline-slashing view (and what's right about it)

Let me steelman the productivity-hacker before disagreeing, because the instinct is sound. Slack genuinely does invite waste. Give yourself a full day for a one-hour email and you'll find ways to spend the day — re-reading, re-polishing, inventing sub-tasks, "researching." A tighter box really can cut that. The technique also fights perfectionism: a hard stop forces you to ship something instead of buffing it forever. And there's a real motivational kick — urgency concentrates attention, and a looming clock can pull you out of dithering. All true. If your problem is that you let trivial tasks sprawl, shrinking the box is a fine fix.

But the hack smuggles in a second claim Parkinson never made: that time pressure is the same thing as efficiency, so the tighter the deadline, the better the output. That part is the comforting fiction, and it's where the law gets misapplied.

How it actually works

1. The law is about scope, not the clock

The reason work "expands" isn't that time is magic. It's that an undefined task has no natural finish line, so it keeps absorbing effort until something external stops it. The deadline is just the most common external stop. The actual cause of bloat is a fuzzy definition of done — and you can fix that directly without playing clock games. A task with a sharp, written "done when X" doesn't expand much even on a generous timeline, because it already knows where to end.

2. Tight deadlines cut the wrong things first

Here's the part the hack ignores: when you compress time, the work does shrink — but you don't control which parts get cut. Under real pressure, the first casualties are the invisible, valuable ones: checking your assumptions, the second pass that catches the embarrassing error, the small rethink that would've saved a rework later. You get something shipped on time that's quietly worse, and the cost shows up downstream where it's hard to trace back. Speed bought by amputating the quality steps isn't efficiency. It's a loan.

3. Manufactured urgency stops working when it's always on

The motivational jolt of a tight deadline is real, and it's also a stimulant with tolerance. Run your whole life at artificial DEFCON-1 and your body stops treating the alarm as an alarm. What was a useful sprint becomes a baseline of low-grade stress, focus dulls, and you've traded a tool you could deploy occasionally for a pressure you can't switch off. The people who take "shrink every deadline" most seriously are the ones it exhausts fastest.

4. The honest lever is scope, slack, and a real finish line

So if not clock-slashing, then what? Define done before you start (one written sentence). Right-size the box to the actual work plus a margin, not to an ego-flattering minimum. And protect deliberate slack — not as waste, but as the room where the second-pass thinking and the catching-of-errors live. Parkinson's Law, read correctly, is an argument for clarity, not for pressure.

A concrete example

Two people get the same report to write. The first uses the hack: "this gets one hour, go." She produces something in an hour — and it's missing the one number the reader actually needed, because checking it didn't fit. It comes back the next day for a redo. Total time: ninety minutes, plus a credibility ding.

The second skips the clock theatrics and instead writes one line first — "Done when the recommendation is stated and the three supporting numbers are verified." That sharp finish line stops the work from sprawling on its own, and the verification step survives because it's part of the definition, not a luxury to be cut. She's done in seventy minutes, once. Same law, opposite move: she constrained the scope, not the clock.

Why this matters

If you believe Parkinson's Law prescribes tight deadlines, you'll reach for time pressure as your default tool, cut the quality steps without noticing, and slowly cook yourself on permanent urgency — all while feeling productive. If you understand that the law is really about undefined scope, your effort moves to the cheap, durable fix: deciding what "done" means before you start. The honest caveat cuts both ways — loose timelines genuinely do invite bloat, and a hard stop is a legitimate tool to deploy sometimes, especially against trivial tasks you're over-polishing. The error isn't using deadlines. It's mistaking the deadline for the lever, when the lever was always the finish line you forgot to draw.

The practical implication of being right about this: fix the definition of done, and the timeline mostly takes care of itself.

Try this

Take the next task on your list and, before touching it, write one sentence: "This is done when ___." Make it specific enough that a stranger could tell whether you'd hit it. Then give the task an honest box — the real work plus a margin — instead of the smallest number that flatters you. You've just removed the thing that makes work expand, without spending a drop of artificial stress.

A finish line only works if you can find it again, which is the quiet reason a [weekly review](the-weekly-review.md) and a written "done when" outlast any deadline trick. Jot that one sentence into JustJot.ai next to the task itself — so the task carries its own ending around with it, and the work has somewhere to stop.

The rule: work expands to fill undefined scope. Don't shrink the clock — draw the finish line.