Progressive Disclosure¶
Nielsen, J. (2006). Progressive Disclosure. Nielsen Norman Group.
Cited by¶
7 citations across 7 artifacts.
Each citation links to the sentence it supports in the citing article.
Domain-specific¶
- Progressive-Disclosure Failure
- Progressive disclosure as a design principle is correct: exposing complexity gradually, reserving advanced controls for experienced users, matching what is shown to what the user can act on at each step
This sourceDefines progressive disclosure as showing the few most important options first and deferring advanced or rarely used features to secondary screens, improving learnability, efficiency and error rate.
SupportedVerified against the source
- Progressive disclosure as a design principle is correct: exposing complexity gradually, reserving advanced controls for experienced users, matching what is shown to what the user can act on at each step
Mechanisms¶
- Drilldown Recognition Interface
- This is why a drilldown is not the same as progressive disclosure, which merely stages how much information is shown
This sourceDefines progressive disclosure as showing a small core set first and revealing secondary information or features only on request.
- This is why a drilldown is not the same as progressive disclosure, which merely stages how much information is shown
- Modular Form Schema
- Answer "self-employed" and a whole 1099-income section unfolds; answer "laid off" and a former-employer section appears instead — conditional disclosure driven by an earlier field, an application of progressive disclosure
This sourceShows that deferring seldom-needed options can spare users from scanning features they do not need.
- Answer "self-employed" and a whole 1099-income section unfolds; answer "laid off" and a former-employer section appears instead — conditional disclosure driven by an earlier field, an application of progressive disclosure
- Personalized Onboarding Path
- Run the role-relevant sequence. Each path front-loads what that segment needs and drops what it does not, cutting time-to-competence — a use of progressive disclosure
This sourceDefines progressive disclosure as revealing specialized features only when requested.
- Run the role-relevant sequence. Each path front-loads what that segment needs and drops what it does not, cutting time-to-competence — a use of progressive disclosure
- Progressive Disclosure
- Used well, it is the established remedy for interfaces that would otherwise drown the novice.
This sourcePresents progressive disclosure as a technique that defers advanced features so novice users can focus on the most common tasks.
- Used well, it is the established remedy for interfaces that would otherwise drown the novice.
- Progressive Disclosure for Load Reduction
- Progressive disclosure fits when a single audience spans a wide range of need on the same interface — most users want a simple default, a minority want full depth, and both must be served without a fork.
This sourceUses progressive disclosure to provide a simple default for most users while retaining optional depth for users with advanced needs in the same interface.
- Progressive disclosure fits when a single audience spans a wide range of need on the same interface — most users want a simple default, a minority want full depth, and both must be served without a fork.
- Progressive Disclosure Panel
- The discipline that keeps it honest is to set the split from real usage data, label the gate so it truly promises its contents, and never stage a common capability behind it.
This sourceRecommends using field research and usage data to separate frequent from secondary features, labeling the disclosure control clearly, and keeping frequently needed capabilities upfront.
- The discipline that keeps it honest is to set the split from real usage data, label the gate so it truly promises its contents, and never stage a common capability behind it.
Verification¶
Does it exist? Not checked yet. This entry carries no identifier to resolve. It was extracted from the citation as written in the article, normalized, and deduplicated against the rest of the registry.
Does it back the claim? Read against the text for 1 of 7 citations: 1 supported. Each verdict is shown under its citation below, with what in the work backs the sentence.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Registry ID ref:32afa3671322 · see in the full table