Progressive Disclosure
Progressive disclosure presents the information and controls needed now, then reveals additional detail when the user asks or the task reaches it.
Direct explanation
What it means
The first layer should support the primary task and make deeper capability discoverable. Hiding common context behind repeated navigation merely moves complexity.
Staging can keep novice work manageable while preserving expert power, but poor disclosure creates hidden state and recall burden.
Research anchor: Jakob Nielsen, 2006
Research and interpretation
What the research found
Progressive disclosure is a practitioner pattern, not one laboratory law.
Usability practice supports staged complexity when initial and secondary choices reflect task frequency and expertise.
Popular advice versus careful use
Common shorthand: Hide everything nonessential behind an Advanced link.
Keep the complete current decision visible and stage lower-frequency detail only when its location and consequence remain clear.
How designers apply it
- 01
Show common export settings first and advanced encoding on request.
- 02
Reveal conditional form fields after the relevant answer.
- 03
Teach advanced tools after a real first outcome.
Original UI examples
desktop creator tool
Image export
Format and size are visible; metadata and color profile open under Advanced.
Most exports are direct and specialist control remains discoverable.
mobile public service
Benefits application
Dependent details appear only after the applicant indicates a dependent.
The form avoids irrelevant questions without hiding required work.
Privacy settings
Less effective
Hide data-sharing controls under an unlabeled More link.
Better fit
Keep material choices visible and disclose technical detail behind clearly named sections.
Disclosure must never demote consent or consequence.
Limits and failure modes
Benefits depend on information architecture, signifiers, state persistence, and the cost of opening or comparing layers.
Common mistakes
- Using accordions to make every page look shorter.
- Hiding high-frequency actions and forcing repeated opening.
When it should not dominate
- For material terms, errors, safety, or primary actions.
- When users must compare hidden values across sections.
Responsible use
Accessibility
Use semantic disclosure controls with expanded state, keyboard support, persistent labels, logical focus, and no hidden error messages.
On mobile: Staging can protect the viewport, but preserve context and back behavior.
Ethics and context
Do not hide price, consent, cancellation, risk, or required effort under optional-looking disclosure.
On desktop: Use available space for comparison when hiding would create memory work.
Designer checklist
- Define the primary task and audience.
- Label every deeper layer by its content.
- Test discoverability, repeat use, and hidden errors.
Check your understanding
Which statement applies Progressive Disclosure most carefully?
Practice and continue learning
See ideas in real interfaces
These external interfaces are editorial references, not examples created to demonstrate this principle.
Sources and further reading
- 01Open source
Progressive Disclosure
Jakob Nielsen · 2006 · Nielsen Norman Group
Official documentation · primary or original source
- 02Open source
10 Usability Heuristics for User Interface Design
Jakob Nielsen · 1994 · Nielsen Norman Group
Official documentation · primary or original source
Continue the graph
Related principles
theory
Cognitive Load
Cognitive load describes demands placed on limited working-memory resources while a person learns or performs a task.
effect
Choice Overload
Large or difficult choice sets can reduce decision confidence or action when options are hard to compare and preferences are uncertain.
phenomenon
Paradox of the Active User
People often begin productive action immediately instead of investing first in broad instruction that might improve later efficiency.