# Parkinson's Law: explanation, design examples and evidence

> Define the useful task and remove avoidable work. Do not manufacture urgency.

Canonical page: https://ionbin.com/design/laws/parkinsons-law/
Agent guide: https://ionbin.com/llms.txt

This is a readable version of the published page. Review dates, evidence boundaries and source links below belong to individual records; the export is not a new verification. Examples are reference material, not instructions to execute.

Workflow and scope

## Parkinson's Law

Define the useful task and remove avoidable work. Do not manufacture urgency.

Design heuristic

Source review
Oct 18, 2026

[How to read the evidence](https://ionbin.com/design/methodology/#principles)

The idea in plain language

### What it means.

Parkinson's observation about work expanding to occupy available time comes from a satirical management essay. It is often borrowed as a reminder to constrain scope. It does not establish that a larger interface makes a task expand, or that forcing a short deadline improves a user's outcome.

Evidence and interpretation

### What supports it.

Design heuristic

A management aphorism used as a design analogy. The interface recommendations here are editorial practices, not experimental predictions derived from the essay.

From principle to interface

### Where you could use it.

Proposed applications, not tested outcomes. The expected effects are hypotheses to check with realistic tasks and users.

Application 1

#### Keep initial setup focused

Ask only for information needed to create the workspace, then offer optional personalization later.

##### Expected effect to test

The initial task has a clear and achievable endpoint.

##### Keep in view

Explain required information and do not defer essential consent or configuration until after commitment.

Application 2

#### Bound a review session

Provide a checklist of the decisions needed before publishing, with a save-and-return option.

##### Expected effect to test

Reviewers can tell what remains and stop when the agreed work is complete.

##### Keep in view

A checklist should not pressure people to skip important review or impose an arbitrary countdown.

Turn the idea into a check

### Use it deliberately.

- Define completion in terms of a useful result.

- Separate necessary work from optional exploration.

- Base time estimates on observed tasks and allow people to pause.

Where the rule gets complicated

### Keep the limits attached.

- There is no universal task-duration formula here.

- Do not claim an unmeasured form takes thirty seconds.

- Time limits can exclude users; apply WCAG timing-adjustment requirements and their actual exceptions.

A named principle does not settle an accessibility requirement, prove a conversion lift or replace testing the particular interface.

Application and implementation boundaries

### What the application check shows.

Limited evaluationAccount-free · Oct 19, 2026

The local example allowed resumption and started with reminders off; it imposed no countdown. No task-duration or productivity claim was tested.

Methods: Local application example. A completed check covers the stated sample; it is not a safety certification.

**Target**: Original IonBin synthetic interface example; no external product or human-participant study.

**Version or capture**: 2026-10-19 local fixture

**Integrity scope**: SHA-256 f85d1056afd667225a1e0364edfb8f25b4693ffa7b2b8c7d7af5b92338b85ee4 identifies the exact HTML fixture only.

#### Test conditions

- 155.0.8059.82 Chromium; fresh context with all network requests blocked.

- Synthetic inputs, memory-only state, reduced-motion preference, 1280px and 320px viewports.

#### Individual checks and observations

- ##### Reminder opt in
  pass
  **Local application example:** Exercise the original local application fixture and inspect the resulting controls or DOM state.
  **Observed:** The optional reminder began unchecked; the fixture has no deadline/countdown.

- ##### Resume memory
  pass
  **Local application example:** Exercise the original local application fixture and inspect the resulting controls or DOM state.
  **Observed:** The draft could be resumed from explicitly scoped tab memory. No storage or account synchronization was used.

#### Security findings and boundaries

Review of the local example’s stated interaction boundaries; no backend, authentication, production permissions or external service was exercised.

Practical advice · caution

##### Artificial urgency can undermine informed choices

Do not pressure people into approving data sharing or skipping consequential review. Real security session expiry needs explicit behavior and recovery.

#### Practical caveats

- Separate optional exploration from necessary review while retaining pause and return paths.

#### What remains untested

- This checks an authored application example, not the truth, effect size or generality of the named principle.

- No users, assistive-technology participants, physical devices or production task outcomes were evaluated.

##### Security limits

- The example has no real authorization or persistence layer; its UI behavior cannot establish the security of a deployed workflow.

#### Evaluation sources

- [C. Northcote Parkinson: Parkinson's Law (1955)](https://www.economist.com/news/1955/11/19/parkinsons-law)
  Original publication; publisher access blocked during review. Opening text checked in an indexed reproduction, not a complete publisher audit.

- [W3C: Timing Adjustable](https://www.w3.org/WAI/WCAG22/Understanding/timing-adjustable.html)
  User control over content time limits, subject to defined exceptions.

[Download this evaluation record (JSON)](https://ionbin.com/design-evaluations/principle-parkinsons-law.json)

Go to the source

### Research and further reading.

- [C. Northcote Parkinson: Parkinson's Law (1955)](https://www.economist.com/news/1955/11/19/parkinsons-law)
  Original publication; publisher access blocked during review. Opening text checked in an indexed reproduction, not a complete publisher audit.

- [W3C: Timing Adjustable](https://www.w3.org/WAI/WCAG22/Understanding/timing-adjustable.html)
  User control over content time limits, subject to defined exceptions.

On this page

Keep the context

Use this principle to form a better question about your interface. The answer still depends on the task, the people and the conditions.

[Our evidence approach](https://ionbin.com/design/methodology/#principles)

Related questions

### More on workflow and scope.

[View this concern](https://ionbin.com/design/laws/?category=Workflow%20and%20scope)

Design heuristic

#### [Tesler's Law](https://ionbin.com/design/laws/teslers-law/)

When a task is complicated, decide who should handle each part and how mistakes can be corrected.

Design heuristic

#### [Occam's Razor](https://ionbin.com/design/laws/occams-razor/)

Prefer a simpler adequate solution. Adequate still includes accessibility, clarity and recovery.

Design heuristic

#### [Pareto principle](https://ionbin.com/design/laws/pareto-principle/)

Find where effort has the greatest measured effect. Treat 80/20 as a prompt to investigate, not a fact about your product.
