Progressive Disclosure
Progressive Disclosure
One-Sentence Definition
Show essential information first, then reveal complex information as needed.
What Problem Does It Solve
It helps you design clearer user paths, choice structures, and information hierarchies.
More specifically, Progressive Disclosure is suited for answering questions like: Is what I’m seeing a fact, an assumption, or a habitual practice? To make a better choice, which variable, path, or constraint should I look at first?
When to Use
- When a problem becomes complex and intuitive judgment is no longer reliable.
- When the team disagrees on the next step and needs a shared analytical framework.
- When you need to turn abstract judgments into concrete actions, checklists, or experiments.
- When current practices are losing effectiveness and the underlying logic needs re-examination.
When Not to Use
- The problem is simple, and direct execution is more important than analysis.
- Basic facts are missing, and you are just spinning concepts.
- The model is used only to justify existing conclusions, not to help correct judgment.
- The cost is extremely high, trial and error is impossible, and there are no additional verification methods.
Steps to Use
- Write down the current problem: Describe in one sentence what you need to judge or solve.
- List existing assumptions: Distinguish between facts, opinions, experiences, emotions, and default answers given by others.
- Identify key variables: Find the 1-3 factors that most influence the outcome.
- Form actionable options: Propose several different approaches based on the key variables.
- Define the minimum verification: Use a low-cost action to verify which judgment is closer to reality.
Mini Case Study
Suppose a team finds that new user conversion rates are declining. Using Progressive Disclosure, instead of immediately asking designers to change a button or asking operations to increase the budget, they first break it down: Where do users come from, what information do they see, at which step do they hesitate, what do they lose when they abandon, and are there stronger alternatives? After the breakdown, the team might discover the real problem is not insufficient traffic, but that users don’t understand what problem the product solves on the first screen. The minimum action, therefore, is not to redesign the entire product, but to first test a clearer value proposition.