Skip to content
UX Atlas
Plate LAW·013 · LawGrid A1 · Rev. 2026-08-14

Parkinson's Law

Work expands to fill the time available, which is why open-ended tasks in an interface tend to sprawl.

LawCraft conventionFoundational

Definition

Cyril Northcote Parkinson's 1955 aphorism, published in The Economist, that work expands so as to fill the time available for its completion. In interface design it is used to argue for constraints, defaults and visible time expectations.

Craft convention. True because the industry converged on it. Breaking it costs familiarity, not correctness.

On this plate
  1. 1Definition
  2. 2How it shows up in interfaces
  3. 3Applications
  4. 4Using time boxes in an interface
  5. 5In practice
  6. 6Local chart
  7. 7Sources
  8. 8Continue from here

Reach for this when

  • Setting defaults for any duration or quantity.
  • Designing forms and flows where users hesitate to start.
  • Building planning and scheduling tools.

Common mistakes

  • Citing it as research.
  • Publishing an optimistic time estimate that the flow does not meet.
  • Using artificial urgency, which is a different and more damaging thing.
  • Using a fabricated deadline, which is a deceptive pattern wearing a productivity argument.

How it shows up in interfaces

A form with no indication of length invites hesitation. A meeting scheduler defaulting to sixty minutes produces sixty-minute meetings. A task list with no time estimates produces tasks that never close.

The design lever is the default and the visible expectation. Both set an anchor, and most users accept the anchor.

Applications

  • Tell users how long a flow takes, and be accurate. 'Two minutes, four questions' outperforms an unlabelled form.
  • Default meeting lengths to something shorter than the habit, such as twenty five or fifty minutes.
  • Show step counts on multi-step flows so the end is visible from the start.
  • Use time-boxed defaults in planning tools rather than open-ended fields.

Using time boxes in an interface

Do

  • Show an honest estimate before a task starts, so people can plan around it.
  • Default to the shorter option when a duration is being chosen.
  • Make the finish line visible, so there is something for effort to compress towards.

Do not

  • Invent a countdown to create urgency that does not exist.
  • Set a time limit on a task where being rushed costs accuracy.
  • Treat a folk law about bureaucracies as a measured effect in interface design.

In practice

  1. i.

    Estimated completion time on forms

    Surveys and applications

    Stating an accurate time estimate up front raises completion. Stating an inaccurate one lowers trust and raises abandonment at the moment the estimate is exceeded.

  2. ii.

    Shortened default meeting durations

    Calendars

    Calendar products that default to twenty five and fifty minute meetings shifted a widespread organisational habit purely by changing a default value.

  3. iii.

    Two minutes, stated up front

    Estimates as a design element

    A form labelled as taking about two minutes is completed at a higher rate than the same form unlabelled, provided the estimate is true. An estimate people learn to distrust is worse than none.

Local chart

LAW·013 · Region I · Grid A1

This entry and the entries it is stated to connect with. Each line is labelled with what the connection means.

Sources

Where a source establishes something narrower than the popular reading of it, the note says so.

  1. [1]

    Parkinson's Law

    C. N. Parkinson, The Economist, 1955

    A satirical essay. Widely quoted, never experimentally established.

  2. [2]

    Procrastination, deadlines, and performance: self-control by precommitment

    D. Ariely and K. Wertenbroch, Psychological Science, 2002

    Experimental work on deadlines, and a better citation when evidence is required.

Each link says what the connection is, so you can tell a principle from an alternative from a thing people mix this up with.

Applies when you are designing

Why this works

The reasoning this entry rests on.

Applied through

Where this shows up as a concrete interface decision.

Check your work

Review passes that test whether this was done properly.

Related concept

Connected closely enough to change how you apply this.