Progressive disclosure

Progressive disclosure reduces initial cognitive load by showing the minimum needed for the current task while keeping deeper detail available when it becomes relevant.

Sequencing complexity — rather than hiding capability — lets actors move quickly, then inspect more when they need understanding, control, or proof.

Forces

• Simplicity vs completeness — the first view should be easy to parse, but the full system still needs to remain reachable
• Speed vs understanding — actors often want to finish the task before they want to study the logic behind it
• Reduced distraction vs explainability — extra detail can help sensemaking, but it can also interrupt flow and create doubt
• Default clarity vs accountability — concise interfaces still need a path to evidence, rationale, and contestability

Main forms

Triggered expansion

Secondary detail stays hidden behind an explicit action such as a details element, accordion, or “Show more” link.

Use when the deeper layer is optional for most actors but important for some.

Staged flows

Complexity is distributed across steps so one decision is made before the next set of controls appears.

Use when users need guidance through an ordered process, such as setup, onboarding, or multi-step configuration.

Contextual reveal / progressive enabling

Extra options appear only after a preceding choice makes them relevant, such as selecting a filter that reveals sub-filters or enabling an advanced mode that unlocks more controls.

Use when later controls depend on earlier choices and would otherwise read as noise.

Disclosure ladder

Movement between levels should usually be actor-driven and reversible. The point is not to trap people in a shallow view, but to make deeper inspection feel proportional to the current need.

0. Outcome or primary state. Show the result, current status, or core action.
1. Short reason or summary. Offer a compact explanation of what happened or why this is the current state.
2. Key factors or high-impact details. Reveal the major factors, dependencies, or advanced controls that explain most of the outcome.
3. Full explanation or inspectable evidence. Provide detailed rationale, full configuration, logs, proofs, or traceable evidence for actors who need to audit, troubleshoot, or contest the result.

When to disclose more

• The actor asks for it — explicit curiosity is the cleanest trigger for deeper explanation
• Expectation violation occurs — if the system surprises the actor, they are more likely to seek and benefit from detail
• The stakes are high — consequential, contestable, or risky decisions need a shorter path to proof
• The task shifts from doing to understanding — troubleshooting, learning, and model-building need deeper inspection than routine execution

Anti-patterns

• Hiding primary actions — progressive disclosure should defer secondary detail, not conceal core actions that most users need
• Premature exhaustiveness — exposing every factor up front can overwhelm users and undermine trust instead of improving understanding
• Silent depth — if there is no hint that more exists, users cannot form an accurate mental model of the system
• Nested tunnels — too many levels of expansion create navigation overhead and make people lose context
• Noise masquerading as transparency — showing low-signal detail is not the same as explaining what materially drove the outcome

Related components

• Details — a mechanism for triggered expansion
• Dialog — a container for disclosed content that needs more space or focus
• Popover — reveals supplementary information without an explicit expansion

Resources & references

• Springer, A., & Whittaker, S. (2020). Progressive Disclosure: When, Why, and How Do Users Want Algorithmic Transparency Information?
• Springer, A., & Whittaker, S. (2019). Progressive Disclosure: Empirically Motivated Approaches to Designing Effective Transparency
• NN/g - Progressive Disclosure
• Wikipedia - Progressive disclosure