Product strategy

Parkinson's Law

Work expands to fill the time available for its completion — and users' tasks expand to fill the time an interface allows.

Retention · Friction & Flow Psychology1 research source
Share
An hourglass draining while the task bar stretches to fill all the time available — an illustration of Parkinson's Law.

See it in action

The same screen without and with Parkinson's Law. Watch both sides play out, then compare the outcome.

Open-ended taskTell us about your projectWrite as much as you like…Time spent12 min

With no shape or limit, the task expands — people over-think, over-write or abandon it.

Bounded and estimated3 quick questionsAbout 1 minuteWhat are you building?Who is it for?When do you launch?Time spent1 min

A clear scope and a time estimate keep the task as small as it really is.

What to watch: the time bar — the same information gathered in a fraction of the time.

Do

Set clear scope, limits and time estimates; use smart defaults to shorten tasks.

Don’t

Leave tasks open-ended or impose deadlines so tight that quality suffers.

Key takeaways

  • Design flows to be completed faster than users expect.
  • Use smart defaults and autofill to shorten tasks.
  • Clear time expectations ('takes 2 minutes') help users commit and finish.

Quick facts

Also known as
—
Described by
Cyril Northcote Parkinson
Year
1955
Category
Product strategy

Parkinson's Law explained

Parkinson's Law states that work expands to fill the time available for its completion. If a task has a week, it tends to take a week; if it has a day, it is often done in a day.

For users, this applies to tasks inside products: an open-ended form, an unlimited trial or an unstructured setup process invites procrastination and over-thinking. Clear limits and expectations help people finish.

For teams, Parkinson's Law explains why projects without tight scope and deadlines drift, and why time-boxing research and design work keeps it focused.

Where it comes from

Coined by British naval historian C. Northcote Parkinson in a satirical 1955 essay in The Economist about the growth of bureaucracy.

How it shows up in apps

Open-ended setup flows invite users to deliberate, postpone and drop off. Constraining tasks and pre-filling what you can keeps momentum.

Parkinson's Law examples

A profile setup screen that says 'About 60 seconds' and autofills name and photo from sign-in sees more users finish it in one go.

  • Estimated completion times

    Surveys and onboarding flows that say 'takes 2 minutes' set an expectation that helps people finish quickly instead of overthinking each answer.

  • Autofill and smart defaults

    Checkout forms that autofill addresses and payment details let users complete purchases in seconds, leaving no room for the task to expand.

  • Trial lengths

    Shorter free trials with clear milestones often lead to faster product evaluation, because users know they need to explore key features within the time limit.

How to apply Parkinson's Law

  1. Tell users how long a task will take, and make sure the estimate is honest.
  2. Reduce the time needed to complete tasks with autofill, defaults and saved information.
  3. Give multi-step processes clear structure and milestones.
  4. Time-box research, design sprints and decisions within the team.
  5. Use gentle reminders and deadlines for tasks users start but do not finish.

Want Parkinson's Law checked in your own product? Our saas ux audit evaluates it alongside the other principles that shape how users decide, onboard and stay.

Common mistakes

  • Creating artificial time pressure that rushes users into decisions they regret.
  • Underestimating task length, which breaks trust when the task takes longer than promised.
  • Leaving setup and configuration open-ended with no sense of what 'done' looks like.

How to measure it

Measure time to complete key tasks and the proportion of started tasks that are finished. Test variants with time estimates, autofill or milestones and compare completion rates and time on task.

Frequently asked questions

What is Parkinson's Law?

Work expands to fill the time available for its completion — and users' tasks expand to fill the time an interface allows.

Where does Parkinson's Law come from?

Coined by British naval historian C. Northcote Parkinson in a satirical 1955 essay in The Economist about the growth of bureaucracy.

How does Parkinson's Law apply to app design?

Open-ended setup flows invite users to deliberate, postpone and drop off. Constraining tasks and pre-filling what you can keeps momentum.

Who came up with Parkinson's Law?

British historian Cyril Northcote Parkinson described it in a humorous essay in The Economist in 1955.

How does Parkinson's Law apply to UX design?

It suggests that limiting and structuring the time users need for a task, and telling them how long it will take, helps them finish rather than procrastinate.

How do you measure Parkinson's Law in a product?

Measure time to complete key tasks and the proportion of started tasks that are finished. Test variants with time estimates, autofill or milestones and compare completion rates and time on task.

Sources

  1. Parkinson, C. N. (1955). Parkinson's Law. The Economist, 19 November 1955. Find on Google Scholar ↗

View all 60 laws of UX

Keep exploring

Parkinson's Law in practice

Keep exploring

Certifications that test it

Pass it on

Teach this to your team

Share it before your next design review — a shared vocabulary makes product decisions faster.

Join free

Get the ideas, not the noise.

Sign up with Google and we’ll send you short UX psychology tips by email — why people tap, stall and leave, and what to do about it. Unsubscribe anytime. Prefer something to keep? Get the free Laws of UX guide as a PDF.

Get the free Laws of UX PDFFree · no spam · unsubscribe anytime
Free certification

Can you apply Parkinson's Law under pressure?

Test it in 18 real product scenarios in the free Product Design Science test. Score 70% and earn a founder-signed certificate anyone can verify.

  • Credential ID
  • QR verification
  • LinkedIn-ready
Free PDF · 74 pages · 2 editions

The Laws of UX, in one field guide

60 research-backed principles in 6 categories — what each one means, why it works on the human brain and how to use it on your own screens. Written by Sushant Singh, founder of Science of Apps, who has scaled consumer apps to lacs of users and spent 10+ years leading product across startups and digital businesses in the US, EU & India.

Pick your edition
Free. No card, no paywall — just your email.
Free PDF · 74 pages

Get Laws of UX by email

Choose your edition

You’ll also get occasional UX psychology tips. Unsubscribe anytime. Privacy policy

Free PDF · 90 pages · 2 editions

100+ Subscription Paywalls, decoded

110 real paywalls from top apps, taken apart, rated out of 5 and decoded with the Laws of UX — plus the frameworks, copy and checklists to ship your own. By Sushant Singh, founder of Science of Apps.

  • 110 paywalls rated
  • 34 Laws of UX
  • 12 frameworks

Which paywall scored 4.8 out of 5, and which scored 2.6? It’s all inside.

Pick your edition
Free. No card, no paywall — just your email.
Free PDF · 90 pages

Get 100+ Paywalls, Decoded by email

Choose your edition

You’ll also get occasional UX psychology tips. Unsubscribe anytime. Privacy policy