Progressive Disclosure
Complexity on Demand
Instead of overwhelming all options upfront or hiding them behind chat syntax, the UI reveals advanced controls behind expansion — beginner mode, advanced mode, or layered accordions. Depth stays available without being default.
Framing
The problem
AI tools often overwhelm novices or frustrate experts when shown the same interface.
The pattern
Reveal advanced controls behind expansion — beginner mode, advanced mode, or layered accordions — so depth is available without being default.
Why chat breaks here
Chat hides advanced capability behind exact wording and prior knowledge — there is no visible path from beginner to expert.
Risks
Important capabilities may remain undiscovered if disclosure is too timid; overly tiered framings rarely match how products actually ship — and the opposite failure goes unaudited, because a tier nobody ever expands was hidden correctly, while the affordance offering it still costs attention on every visit.
Avoid when
The tool is simple enough that full visibility is clearer than layered concealment.
Use when
Novices and experts share the same tool and full visibility would overwhelm one of them.
DOPE evaluation
- Directability
- Expand or collapse complexity with one click
- Observability
- Current complexity level and available controls are always visible
- Predictability
- Each level has a defined, stable set of controls
- Explainability
- Each complexity level is labeled with what capabilities it unlocks
In the wild
- ComfyUI (Comfy.org) — Three real rungs, and the bottom one is now named: Workflow → Browse Workflow Templates, the node canvas, and App Mode (March 2026) — a one-click simplified view you can flip back out of at any time. Caveat: App Builder lets the workflow author pick which inputs App Mode shows, so the simple tier is curated, not self-service.
- Krea AI (Krea) — No easy/advanced toggle in the current product: after the March 2026 redesign, image settings sit beneath the prompt box and vary by model — Krea's own framing is controls that stay hidden until you need them. The step up in depth is a separate surface, the Nodes canvas at krea.ai/nodes, not a mode switch inside the generator.
- Stable Diffusion WebUI (Auto1111) (AUTOMATIC1111) — Top-level prompt + collapsible sections (Sampling, Hires.fix, ADetailer extensions). Accordion-style progressive disclosure as a power-user norm.
- LM Studio · User / Developer modes (LM Studio) — A named complexity mode, set once and applied app-wide: User hides everything but chat and auto-configures; Developer exposes load and inference parameters. Also the clearest evidence against a three-rung ladder — 0.4.0 (Jan 2026) called merging Power User into Developer a simplification of the previous three-mode switch.
FAQ
When should I use the Progressive Disclosure pattern?
Novices and experts share the same tool and full visibility would overwhelm one of them.
When should I avoid the Progressive Disclosure pattern?
The tool is simple enough that full visibility is clearer than layered concealment.
What problem does Progressive Disclosure solve?
AI tools often overwhelm novices or frustrate experts when shown the same interface.
Why is chat the wrong fit for this?
Chat hides advanced capability behind exact wording and prior knowledge — there is no visible path from beginner to expert.
Related patterns
- Often paired with: Property Panel — Layer the cockpit so essential controls stay calm and expert ones are nearby.
- Alternative to: Semantic Zoom — Disclose controls in layers vs disclose output depth on a single slider.
- Extends: Inline Prompt Controls — Detected fields can hide behind layers until the user wants to tune them.