Progressive Disclosure: Show, Don't Overwhelm

Progressive disclosure is a guided tour for your UI, revealing information only as needed. It simplifies complex forms and setup wizards by deferring advanced options, making apps easier to learn.
Why it exists
Interfaces with too many options, fields, and bits of information presented at once can overwhelm a user, leading to decision paralysis or errors. Progressive disclosure was created to manage this complexity, making applications feel simpler and easier to learn by presenting only what's necessary for the current task.
The mental model
Think of it as a guided tour. Instead of handing a user a massive, unfolded map of the entire city (your full UI), you give them turn-by-turn directions. You reveal the next step only when they reach the current landmark. This keeps them focused on the immediate task and prevents them from getting lost in details that aren't yet relevant.
How it works
Progressive disclosure works by creating a clear information hierarchy. The most common or essential information and actions are visible by default. Less common, advanced, or context-specific options are hidden behind a user-initiated trigger, such as an "Advanced Settings" link, a "Show More" button, or an accordion panel. When the user interacts with the trigger, the secondary information is revealed. This allows the interface to adapt to the user's needs, revealing complexity only when requested.
When to use it
Use this pattern for complex configuration screens, multi-step wizards, or long forms. It's ideal for separating primary tasks from advanced or rarely-used features. For example, in a user profile, basic information is visible, while options like "Deactivate Account" might be placed in an "Advanced" section.
When not to use it
Avoid progressive disclosure for core, high-frequency tasks. Hiding a button that 90% of users click every session just adds friction. The biggest footgun is hiding information that is critical for making a decision on the visible part of the UI. For instance, hiding shipping costs or key terms of service behind an extra click can mislead users and destroy trust.
One canonical example
A classic example is the Wi-Fi connection dialog on a computer or phone. The primary interface shows a list of networks and asks for a password—the essentials. A link or button labeled "Advanced Options" or "Details" reveals a secondary screen with settings for IP configuration (DHCP vs. Static), DNS servers, and proxy settings. Most users never need these, so hiding them keeps the main task clean and simple.
Interview question
When is it generally NOT advisable to use progressive disclosure in a UI?
- a.To hide critical information necessary for a user's immediate decision.Correct
- b.When designing a complex setup wizard with many optional steps.
- c.When separating primary tasks from secondary, less common features.
- d.For displaying advanced settings that most users rarely interact with.
Why? this is the answer
The card explicitly warns against using progressive disclosure for "hiding information that is critical for making a decision on the visible part of the UI." Options A, B, and D describe scenarios where progressive disclosure is recommended to manage complexity.
Just read this? Test yourself on what you have been reading.
Read the original → en.wikipedia.org
- #ux
- #ui
- #interaction design
- #copywriting
Put your scrolling time to good use
Learn one idea, try a quiz and save useful cards for revision. Tezvyn makes it easy to learn and stay current in your tech field, a few minutes at a time.
The iPhone app is on the way
We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.
Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.
We are hiring for this. Open roles that interview on ux — each one lists the topics its interview covers.
See open roles