Progressive Disclosure
CanonicalConfidence
Cognitive Load
Low
Evidence
production validated
Impact
component
Ethical Guardrail
Never hide required compliance or safety fields behind progressive disclosure. Compliance-critical information must always be visible.
Design Intent
Complexity should only appear when the user or agent is ready for it. Progressive Disclosure shows the minimum necessary information at each stage, expanding as confidence and context grow.
Psychology Principle
Reveal complexity only when the user or agent is ready for it, reducing cognitive overload at every step.
Description
Show only essential elements by default, reveal advanced options when contextually relevant, and provide a clear way to expand or collapse.
When to use
Any form, workflow, or interface with more than 5 fields or decision points -- especially when novice and expert users share the same UI.
Example
Notion Page Editor: Starts with basic text block; advanced blocks and properties expand only when the user types / or the agent detects need.
Autonomy Compatibility
Behavioral Objective
Users see only what they need at each moment and expand only when ready.
- Reduced cognitive load
- Higher task completion rates
- Natural progression from novice to expert usage
Target Actor
role
Everyday user
environment
Complex forms or multi-step workflows
emotional baseline
Easily overwhelmed by too many options
ai familiarity
medium
risk tolerance
low
Execution Model
default_minimal_view
Show only the essential fields or controls.
User feels overwhelmed on first view.
contextual_expansion
Reveal more when the user or agent signals readiness.
User misses needed options or sees too much too soon.
easy_collapse
Allow users to hide advanced sections again.
Interface stays cluttered after expansion.
Failure Modes
Critical fields hidden
Never hide legal safety or compliance items
Expansion trigger is unclear
Use explicit labels and agent suggestions
Too many disclosure layers
Limit nesting depth
User forgets what was expanded
Add subtle visual indicators
Agent over-expands
Respect user preference overrides
Agent Decision Protocol
Triggers
- Form or interface has >5 fields
- User shows signs of overload
- Agent detects novice vs. expert behavior
Escalation Strategy
L1: Diagnose the failing element via behavioral_signals
L2: Nudge -- adjust copy, timing, or visual salience
L3: Restructure -- simplify flow, add progressive disclosure, restructure form
L4: Constrain -- lock Autonomy Dial to confirm_execution, add Strategic Friction
L5: Yield -- flag for human designer or domain expert review
Example
Issue form starts with 3 core fields -> agent detects complex project and offers Show advanced options with one-tap expansion.
Behavioral KPIs
Primary
- Task completion rate with vs. without progressive disclosure
- Time to first expansion
- Cognitive load self-report scores
Risk
- Missed critical fields
- Over-expansion complaints
Trust
- User-reported the interface stays simple until I need more
Decay Monitoring
Revalidate when
- Feature complexity grows
- New user segments onboard
- Interface paradigms change
Decay signals
- Rising abandonment in complex views
- Users requesting simple mode
- Feedback that everything is hidden when I need it
Pattern Relationships
Supports
Amplifies
Conflicts with