The interface, explained 01 / 05
Show less.
Help people do more.
A new user opens account setup. Before they can see any value, the form asks for permissions, preferences, and details they do not yet understand. What should appear first?
01 / The situation
The form is asking for commitment before it earns it.
Imagine an account setup flow with two fields needed to start and five optional decisions about a future workflow. Every field has a reason to exist. They do not all need an answer now.
That distinction matters: the user’s first job is to create an account. The product’s first job is to make that step understandable.
02 / Try the change
Change the order of the burden.
Switch between the two versions. The task and the available options stay the same; only their timing changes.
Set up your workspace
Get started in a few steps.
The form presents every choice before the user can start. Scan the optional fields: each creates another question the user must answer or skip.
This is an illustrative interface, not a measured completion result.
The advanced choices remain available. They move behind a clear control until they become relevant.
03 / The principle
Progressive disclosure is about sequence, not concealment.
Show the information and controls needed for the current decision. Reveal specialized choices when the user asks for them or when a previous answer makes them relevant. This gives a new user a simpler first pass while keeping depth available. Nielsen Norman Group describes this pattern as a way to defer advanced or rarely used features.
Start with the task
Keep the fields required for the immediate goal in view.
Reveal at the right time
Bring in dependent choices after the user makes the choice that needs them.
Keep a visible door
Label advanced options so experienced users can find them without hunting.
04 / Make the call
What should not be deferred?
Choose the item that should remain visible while someone completes a high-stakes form.
The rule: defer secondary complexity, but keep information needed for a safe, informed decision in view.
05 / Use it
Take the principle into your own design.
Start with a real behavior you have observed. The prompt generator will carry this principle forward as a design constraint, along with actions and ways to check the result.
Apply this principleEvidence & limits
Progressive disclosure can make an interface easier to learn, but the right timing depends on the task. Test whether people can still find deferred controls and whether critical information remains visible.
- Jakob Nielsen, “Progressive Disclosure”, Nielsen Norman Group, 2006.
- John M. Carroll and Caroline Carrithers, “Training Wheels in a User Interface”, Communications of the ACM, 1984. The study concerns a training interface; it supports staged complexity, not a universal completion-rate claim.