What you'll understand by the end of this lesson
- Why fewer steps and shorter time estimates make tasks feel more achievable
- How progress indicators that show fewer steps convert better than identical flows that show more
- Why displaying a time estimate on a form or survey changes completion behaviour
- How to audit whether your flows are making tasks feel bigger than they need to be
The principle in plain English
Parkinson's Law was coined by Cyril Northcote Parkinson in a 1955 essay: "Work expands so as to fill the time available for its completion."
The original observation was about bureaucracy — give a task a week and it takes a week; give it a day and it takes a day. The work doesn't change. The container changes, and the work fills the container.
In digital experience design, the same pattern holds — but from the user's perspective. If a form has 10 fields, it feels like a 10-field form. If a checkout shows 5 steps, users expect to spend time on 5 steps. The number of steps and the time container define how heavy the task feels before it begins.
Short time windows and fewer visible steps don't just reduce friction — they prevent the task from feeling as large as it might otherwise seem. The perception of task size changes what users are willing to start.
A simple example
Two versions of the same survey are tested:
Version A: "Please complete our annual customer survey."
Version B: "Answer 3 quick questions — takes less than 2 minutes."
Both surveys contain the same 3 questions. Version B completes at a substantially higher rate.
Version A offers no time container — the user has to imagine how long it will take, and imagination is rarely optimistic. Version B names the container explicitly: 3 questions, under 2 minutes. The task feels bounded and achievable before the user starts.
Checkout progress indicators and step count
A checkout that shows a 7-step progress indicator creates a task that feels like 7 things to do. The same checkout, redesigned to show 3 steps by combining stages, feels like 3 things to do — even if the number of form fields is identical.
Users who see "Step 1 of 7" are evaluating whether 7 steps is worth what they're about to buy. Users who see "Step 1 of 3" are evaluating whether 3 steps is worth it. The psychological container — the step count — changes the perceived effort before a single field is filled.
This is why progress indicators that show fewer, broader steps convert better than identical flows that expose every micro-step. The total effort is the same. The apparent size of the task is not.
When designing a multi-step flow, name your steps at the highest level of abstraction that is still honest. "Your details, delivery, payment" is three steps. "Name, email, address line 1, address line 2, city, postcode, delivery method, payment method, billing address" is nine. The information collected is the same. The task you are presenting to the user is not.
Time estimates that create urgency without pressure
A time estimate on a task does two things simultaneously:
- It bounds the task — "this will take 4 minutes" tells the user the container is small, making the decision to start easier.
- It creates a soft commitment — users who start a "4-minute task" feel some internal pressure to finish within that window, which reduces mid-task abandonment.
Neither of these effects requires any change to the task itself. The same content, with a time estimate added to the prompt, converts and completes differently.
The key is accuracy. A task described as "2 minutes" that actually takes 8 creates distrust — the user feels misled, and distrust of the time estimate transfers to distrust of the product. Underestimating task length is worse than no estimate at all.
Long forms that feel hard vs short forms that feel easy
The field count on a form is one input into perceived difficulty. But it's not the only one — visible step count, page length, and estimated time all contribute to the perceived size of the task.
A form with 6 required fields shown on a single long page with lots of optional fields visible may feel harder than a 6-required-field form shown across 3 short steps. The information collected is the same. The container each form presents is different.
Parkinson's Law suggests that users fill the container they're given. A large-looking form invites large-feeling responses — including the response to not start at all. A compact, clearly bounded form presents a small container, and users approach it with correspondingly lower resistance.
The temptation when applying this principle is to hide the true length of a task — making a 10-minute form appear to be 2 minutes, or compressing a 6-step checkout into a misleadingly short-looking 3-step indicator. This creates a worse experience: users who reach the end of what they thought was a short task and find more steps or longer fields than expected feel deceived and are more likely to abandon at that point than if the true length had been communicated upfront. Compress the container only if you can actually deliver within it.
The CRO audit
Look at your forms, onboarding flows, and checkout processes and ask:
1. What step count do you show on your checkout or onboarding progress indicator?
Is it the actual number of micro-steps, or a grouped set of broader stages? If your checkout is showing 7 steps when it could honestly show 3 grouped stages, you're presenting a larger task container than you need to.
2. Do your survey or form prompts include a time estimate?
Every survey and long form should include an accurate time estimate in the prompt. Check whether your prompts include one, and whether the estimate is accurate.
3. Are optional fields visible before required fields?
Optional fields that are visible on page load expand the apparent size of the form. Consider placing them behind a "show optional details" link, or after the required fields, so the form's visible container represents the minimum required effort.
Two versions of an NPS survey are tested. Version A prompt: 'Please complete our customer satisfaction survey.' Version B prompt: 'Share your experience in 2 questions — takes under 90 seconds.' Both have the same 2 questions. Which completes at a higher rate, and why?
You've seen how the size of the container changes how hard a task feels. Now — what happens when confidence and competence are completely misaligned? Why do beginners feel certain while experts feel unsure?