Progressive Disclosure

Version

v2 · 2026-09-28 · History

Prime #

1090

Domain group

Professional & Organizational Practice

Origin domain

Human-Computer Interaction (HCI)

Subdomain

Information Architecture → Human-Computer Interaction (HCI)

Core Idea

Reveal information or options in stages calibrated to the receiver's current need-to-know, each stage sufficient to act on, with deeper layers reachable on demand behind a visible affordance — the visible path down is what separates disclosure from concealment.

How would you explain it like I'm…

Lift-the-Flap

A good menu shows you a few simple choices first, with a little arrow that says 'more here' if you want it. You don't have to see every single option all at once — that would be too much. You get just enough to choose, plus a clear way to peek deeper if you need to.

A Little at a Time

Progressive Disclosure means showing information or choices a little at a time, matched to what you need right now, instead of dumping everything on you at once. Each step is complete enough to act on, and deeper details are tucked behind a visible button or arrow that says 'there's more this way.' The big idea is the difference between what's *available* and what's *shown*: everything can still be there, just revealed in stages. That visible path down is the key part — it's what separates this from simply hiding things, because you always know more exists and how to reach it.

Layers With a Visible Path

Progressive Disclosure is the structural move of revealing information or options in stages, calibrated to the receiver's current need-to-know, rather than presenting the whole space at once. Each stage is complete enough to act on, while deeper layers stay hidden behind a recognizable affordance that lets the receiver descend on demand. Two parts are load-bearing: the *layering* (a sequence of self-contained surfaces, each adequate for one coherent decision) and the *affordance* (a visible signal that more exists and roughly what kind). The essential commitment is the distinction between information *available* and information *presented* — a system can be fully transparent yet progressively disclosed, showing only what's needed at each stage. This is exactly what separates it from *omission*: omission hides without an affordance, leaving you unaware anything is missing, whereas progressive disclosure hides *with* a visible path down. Remove that path and the layering degrades into concealment.

 

Progressive Disclosure is the structural move of revealing information or options in stages, calibrated to the receiver's current need-to-know, rather than presenting the full space at once. Each stage is complete enough to act on; deeper layers exist but are hidden behind a recognizable affordance that lets the receiver descend on demand. The pattern is a layered surface whose visible layer is always the minimum sufficient for the present task, paired with a clear path to the next layer. Two parts are load-bearing: the layering — a sequence of self-contained surfaces, each adequate for a coherent unit of decision — and the affordance — a visible signal that more exists and roughly what kind, so the receiver can choose to go deeper without being forced to. The essential commitment is the distinction between information *available* and information *presented*, two things that everyday talk of 'transparency' and 'completeness' tends to collapse: a system can be fully transparent — everything is disclosable — while being progressively disclosed, so only what is needed shows at each stage. The move is therefore not withholding information but sequencing its presentation against need, which is what separates it from mere omission: omission hides without an affordance, leaving the receiver unaware anything is missing, whereas progressive disclosure hides *with* a visible path down, so the receiver knows more exists and how to reach it. The visible path is structurally indispensable, because without it the receiver does not know what they do not know and the layering degrades into concealment. The full skeleton: a layered surface; each layer self-contained and sufficient for a coherent task; a visible affordance from each layer to the next; defaults chosen so that not descending is itself reasonable; complexity hidden but reachable, not removed; and a characteristic failure mode where the layers are arbitrary, the affordances weak, or the hidden content consequential.

Broad Use

• Human-computer interaction: Menus that show common options first with "More…", wizards that ask one question per screen.
• Teaching: Spiral curricula that introduce a concept simply, then return with added structure, then with full formal apparatus.
• Legal communication: Plain-language summaries layered on statutes; "key terms" boxes atop full contracts.
• Software architecture: High-level facade calls delegating to lower-level primitives reachable only when needed.
• Scientific writing: Abstract, then introduction, then methods, then full detail — each layer self-contained.
• Onboarding: New hires meet procedures, then policies, then exceptions, then underlying reasoning, on a schedule matched to need.

Clarity

Separates information available from information presented, so a system can be fully transparent while disclosing progressively — and makes the dark pattern of burying consequential content nameable.

Manages Complexity

Sizes each layer to a coherent unit of decision and defers the rest, so the receiver's working memory is spent only on what the current task needs.

Abstract Reasoning

Reasoning becomes layered sufficiency: the audit discipline is test by stopping — if a receiver who halts at a layer is materially worse off, it is truncation, not disclosure.

Knowledge Transfer

• UI → curriculum: "Layer by task, not topic" applies identically to a menu, a course module, a contract section, and an API surface.
• Software → legal documents: "Make the affordance honest" — hidden tabs, missing "advanced" controls, and unmarked exceptions break the contract everywhere.
• UI defaults → curriculum core: "Default well" carries from sensible UI defaults to a curriculum's "what every student must know."

Example

A spiral curriculum on recursion: a first pass ("a function that calls itself") is sufficient to trace a countdown, "we will return to this" is the honest affordance down, and the full formalism is hidden-but-reachable in later passes.

Relationships to Other Abstractions

Current abstraction Progressive Disclosure Prime

Parents (1) — outgoing typed relations

• Progressive Disclosure is a kind of Layering Prime

  Progressive_disclosure is 'the specific, receiver-facing SPECIES of layering' defined by three added constraints (per-layer sufficiency, minimum-sufficient visible layer, a visible affordance down) generic layering lacks.

Children (2) — abstractions linked here by typed relations

• Social penetration theory Domain-specific is a kind of Progressive Disclosure

  It remains its own entry because its identity is fixed by the relationship and participants, communication medium and period, disclosure topic, breadth and depth coding, reciprocity, rewards and costs, intimacy outcome, temporal sequence, culture and privacy and competing causal explanation.

• Progressive-Disclosure Failure Domain-specific presupposes Progressive Disclosure

  Progressive-Disclosure Failure presupposes an attempted Progressive Disclosure schedule whose layer exposure is mistuned to users and tasks.

Hierarchy path (1) — routes to 1 parentless root

• Progressive Disclosure → is a kind of Layering

Not to Be Confused With

• Progressive Disclosure is not Information Hiding because disclosure keeps deeper content advertised and reachable, whereas information hiding encapsulates internals the consumer should never need to see.
• Progressive Disclosure is not Layering because it is the receiver-facing species with per-layer sufficiency and a visible affordance, whereas generic layering needs none of those.
• Progressive Disclosure is not Abstraction because it defers detail that remains fully present, whereas abstraction discards detail to form a simpler concept.