Progressive disclosure

What it is

The term was formalised by Jakob Nielsen in the 1990s but the underlying practice is older — Alan Cooper described the pattern in About Face and it appears in Apple's Human Interface Guidelines and Google's Material Design as a foundational recommendation. The core idea: complexity has to live somewhere, but it doesn't have to live on the primary screen.

Progressive disclosure operates at multiple scales: at the field level (a form that reveals conditional fields only when relevant), at the section level (an accordion that expands to reveal detail), at the screen level (a wizard that shows one step at a time), and at the app level (advanced modes that unlock as users demonstrate readiness for them).

Why it matters

Interfaces that surface every possible option overwhelm new users, slow experienced users, and add cognitive load for everyone. Interfaces that hide too much frustrate users who can't find what they need. Progressive disclosure is the middle path — it lets the interface stay calm on first encounter while preserving access to complexity when it's needed.

When to use it

Any product with genuine depth: enterprise software, developer tools, creative applications, complex forms, admin interfaces, configuration systems. Less useful for shallow tools where the entire feature set fits on one screen — hiding what should be visible adds friction without corresponding gain.

What it looks like in practice

A booking form that shows 'Add extras' as a collapsed section, expanding to reveal 12 options only when the user opts in, uses progressive disclosure well. The 80% of users who don't want extras aren't slowed by them; the 20% who do get access.

A code editor that shows a minimal preferences panel with 'More options' or 'Advanced' revealing the full 200-setting configuration honours progressive disclosure. Sublime Text's early success owed much to this pattern — the interface felt simple even though the depth was enormous.

A multi-step checkout that shows one section at a time (shipping, then payment, then review) uses temporal progressive disclosure — spreading complexity across time so no single screen is overwhelming.

Contextual help follows the same principle: don't front-load explanations, but make them available on hover/tap when the user shows uncertainty.

What people get wrong

• Hiding things users need. If 60% of users need an option, don't hide it behind a 'more' toggle — it's not advanced, it's primary.
• Fragmenting related decisions. Splitting one logical decision across three progressive screens forces the user to remember earlier choices while making later ones — that's not disclosure, that's memory tax.
• Using accordions everywhere. When every section is collapsed, users can't scan; they have to open each in turn. Progressive disclosure is a tool, not a default.
• Not signalling what's hidden. A collapsed section with no hint of what's inside is worse than fully visible content — the user doesn't know whether to expand it.
• Confusing progressive disclosure with hiding failures. If an interface has a lot to disclose, examine whether all of it needs to exist first.

Learn next

Progressive disclosure sits inside the wider cognitive-load framework, works alongside chunking (grouping what remains visible), and supports affordance decisions (advanced controls should still signal they exist).

Reviewed 29 September 2026 · Editorial standards