012 min
What progressive disclosure means in UX
You press Print in a word processor, and a dialog opens with a handful of choices and a few buttons for more options. Most of the time you pick a printer and go. The buttons lead to extra dialogs for settings that few people change, like scaling a page or printing the pages in reverse order. In a December 2006 article for Nielsen Norman Group, a usability research firm, the researcher Jakob Nielsen called the print dialog the classic example of progressive disclosure.
Designers call each stage a disclosure level. The first dialog is the initial level, and the extra dialogs are the secondary level. Everything depends on where the line between them falls. A feature that most people need most of the time belongs on the initial level, so the secondary level stays rare. If a common feature sits on the secondary level, many people must open it every time. If a rare one sits on the initial level, everyone has to read past it.
Nielsen sorted the gains from a good split into three of the five parts of usability: learnability, efficiency of use and error rate. Learnability is how quickly new users get going. Efficiency of use is how fast experienced users work. Error rate is how often anyone makes a mistake. The reasoning is easy to follow. A new user has fewer things to read, an experienced user doesn't scan past options they never use, and a setting that is out of sight is hard to change by accident.
Many designers add that a short first screen lowers cognitive load, the amount a person has to hold in mind at once. You can read more about that in cognitive load theory.
022 min
Where progressive disclosure came from
In April 1981 Xerox introduced the Star, an office computer. In 1989 Johnson and colleagues, several of the Star's designers, wrote a look back at the system for IEEE Computer, the magazine of the Institute of Electrical and Electronics Engineers.
Their example was the property sheet, a panel of settings for an object such as a page. On the page-layout sheet, the boxes that control running headers, the text repeated at the top of every page, stayed out of view unless the user said the document would have them. The boxes where you type your own line height or paragraph spacing stayed hidden too, until you set that property to Other. So the panel stayed short for most people and grew only when someone asked.
The designers gave this approach a name and a rule:
Progressive disclosure dictates that detail be hidden from users until they ask or need to see it.
They presented it as a principle their team applied, not as a result from an experiment. They didn't claim to be the first to hide detail. No one person is credited with the idea. It is a habit designers shared, written down by the people who used it.
Many pages credit Jakob Nielsen with inventing it. He didn't. In 2006 Nielsen wrote that progressive disclosure and staged disclosure were both more than 30 years old and had proved useful in many applications and even a few websites.

032 min
Training wheels studies and progressive disclosure
In 1984 John Carroll and Caroline Carrithers published a paper on a training wheels interface in Communications of the ACM, the journal of the Association for Computing Machinery. A training wheels design lets new users work with only a few core features at first. Jakob Nielsen, a usability researcher writing for Nielsen Norman Group, later summarised two studies by Carroll and colleagues. In each one, a group of new users got the limited version, and another group had every feature from the first minute.
In the first sessions, the limited group did better.
| Initial use | Study 1 | Study 2 |
|---|---|---|
| Time on task | 26% faster | 21% faster |
| Facts learned about the system | 69% more | 21% more |
| Satisfaction rating | 28% higher | not measured |
In Study 2 the limit was then lifted, and both groups used the full system. The people who had started with the limited version were 52% faster on advanced tasks and had learned 10% more facts about the system. You might expect the group that saw every feature from day one to do better. They didn't. People who began with a small core did better on the advanced features.
Some pages say these studies prove progressive disclosure works. They don't, because the design is related but different. In the studies the extra features were blocked for new users, not one click away. The studies also involved new users only. They support the idea that a small core helps people learn. They don't show what happens when a button hides a feature from an experienced user.
041 min
Progressive disclosure example: GOV.UK's driving guide
Open GOV.UK's step-by-step page on learning to drive a car, and you don't get a long article. As captured in November 2026, you get a short line of introduction and then a numbered list of steps, among them checking you're allowed to drive, getting a provisional licence and having driving lessons and practice. Each step shows only its title and a Show link. A single link above the list reads Show all steps.
The whole journey fits on one screen. You can scan the titles, find the step you're on and open only that one. This is progressive disclosure in a plain form. The titles are the initial level and tell you what exists. The detail of each step is the secondary level and waits until you ask for it.
051 min
Progressive disclosure in a hotel booking form
While researching the usability of 46 web-based applications, Nielsen Norman Group's team tested a hotel reservation system that squeezed every stage of a booking onto one screen. For choosing a room, the screen worked well. It showed availability and prices for several room categories across several dates, which many hotel sites spread over several pages.
The same screen also had a section for the guest's address and credit card details. Hotels need an address and credit card details to finish a booking, but a person who is still comparing rooms and dates doesn't need them yet. Jakob Nielsen, a usability researcher, judged that this caused usability problems. He recommended staged disclosure, a variant in which people step through a fixed sequence of options and see only some of them at each step. In this case the payment details would move to a second screen. He concluded that the design would have been better as two screens, room comparison first and payment second.
Compare this with the print dialog, whose scaling and reverse-order settings are hidden because few people use them. The payment fields in the hotel form are needed by everyone who books, only later. So the question of what to hide depends on the order people work in, not only on how often they use a feature.
061 min
Progressive disclosure in AI interfaces
In 2018 Aaron Springer and Steve Whittaker at the University of California, Santa Cruz, ran two studies of a writing tool called E-meter. Volunteers wrote at least 100 words about an emotional experience, and the tool rated the emotion of their text. One version showed only an overall rating. Another highlighted individual words.
In the second of the two studies, six writers saw word-level feedback only after they finished, by pressing a button that asked how the rating was calculated. Before using the tool, people tended to expect the word-level version to be more accurate. After using both, they split evenly in their preference, and some said the step-by-step feedback gave more information than they needed. The authors suggested showing simplified feedback first and the detail on request. They proposed progressive disclosure as a way to make intelligent systems understandable to the people who use them, a goal the field calls explainability. Their paper is a preprint, a version shared before peer review.
The same two words now also name something different. Since 2026, many pages use them for a technique in which an AI agent reads a short description of each skill or document first and loads the detail only when a task needs it. This article is about the interface principle for people.
072 min
When progressive disclosure goes wrong
Hiding too much is one way for progressive disclosure to fail. In June 2016, Kara Pernice and Raluca Budiu of Nielsen Norman Group reported a study of hidden navigation, where the main menu sits behind an icon such as a hamburger, three stacked lines. They worked with WhatUsersDo, a company that runs remote usability tests. 179 participants did tasks on 6 live sites, on smartphones and on desktops. The sites used hidden navigation, visible navigation or a combination. On desktop, participants opened a hidden menu in just 27% of cases, compared with 48% for visible navigation and 50% for combined navigation. Tasks also took at least 39% longer on desktop when the menu was hidden. The authors concluded that hiding a site's main navigation cuts discoverability, the chance that people find a feature at all, almost in half.
Pages sometimes call a hamburger menu progressive disclosure. It isn't, because the principle covers advanced or rarely used features, and main navigation is what most visitors need.
Putting too much on the first level is the opposite mistake. Jakob Nielsen, a usability researcher, noted in 2006 that print dialogs, the windows that open when you print, had grown bloated over the previous decade. Some applications put detailed options on the first dialog that belonged on a secondary one. Then the first dialog is as crowded as if every option sat on one screen.
Stacking levels is a third mistake. Nielsen warned that a design with three or more levels usually becomes hard to use, because people lose their way moving between them.
082 min
Progressive disclosure vs. nearby concepts
People often mix progressive disclosure up with ideas that sound close to it. This table gives the main difference for each one.
| Concept | The main difference |
|---|---|
| This pageProgressive Disclosure | |
| Not in the library yetStaged Disclosure | |
| Not in the library yetProgressive Enabling | |
| DesignRecognition rather than Recall | |
| DesignHick's Law |
Jakob Nielsen, a usability researcher, separates progressive disclosure from staged disclosure by their navigation. Progressive disclosure is a hierarchy, where you start at the initial display and move to the secondary one only if you need to. Staged disclosure is a linear sequence. The memory row is covered in recognition rather than recall, and the row on decision time in Hick's Law.
092 min
Progressive disclosure patterns in UI design
Wikipedia's mobile article on Typography shows a common pattern, closed headings. The opening paragraphs are open. Below them the rest of the article is a stack of ten one-line headings, beginning with Etymology, each closed and marked with a small down chevron. You see the outline first and open only the part you want.
Other patterns hide different things.
| Pattern | What stays hidden | Fits when |
|---|---|---|
| Closed headings with a chevron | The body of each section | A long page where most readers want one part |
| A Show link on each step | The detail of each step | A journey with several steps, such as learning to drive |
| A button to a second dialog | Rarely used settings | A form whose common case needs few choices, as in a print dialog |
| Fields that appear after a choice | Boxes that matter only once another setting is chosen | A panel where one setting switches others on, such as the Xerox Star's page-layout panel, where the boxes for your own line height appear only after you pick Other |
| A sequence of steps | Everything except the current step's options | Work that happens in a fixed order, such as a hotel booking |
Designers sometimes call the fourth pattern, showing a field only after a choice makes it relevant, conditional disclosure.
101 min
Progressive disclosure and accessibility
A control that reveals more content is a button that changes the page, so it has to work even if you can't see the screen or can't use a mouse. Two things matter.
The first is that a screen reader, software that reads a page aloud, can tell the person what the control is and whether it is open or closed. The Web Content Accessibility Guidelines (WCAG) 2.2, published by the World Wide Web Consortium (W3C), cover this in success criterion 4.1.2, Name, Role, Value, at Level A. It requires that every interface component has a name and role that software can read. It also requires that software can change the control's state, such as open or closed, just as the user can. The W3C notes that standard HTML controls already meet this criterion when they are used as the specification describes. A built-in control is therefore a safer start than a custom script.
The second is that the control works from a keyboard alone. People with motor impairments, and many screen reader users, can't point and click, so a reveal control that only responds to a mouse locks them out of the secondary level.
112 min
How to apply progressive disclosure
Here is how to put progressive disclosure to work on a design you own.
- Step 1List the features and rank them by how often people use them.
- Step 2Check the ranking against what you see people do, because usage numbers can mislead when someone opens a page by mistake.
- Step 3Put the most used features on the initial level and the rest behind one clearly labelled control.
- Step 4Label the way in so people can tell what's behind it. A label that gives a reliable hint has strong information scent.
Picture a product designer reviewing an export panel with many settings. Usage data shows that nearly every export changes only the file format and the page range, so they show those two and put the rest behind a control labelled More export options. A month later, support tickets show that one group of customers needs a compression setting on every export. The designer moves it to the first level for them, because the split was wrong for that group.
Two limits stop the design from hiding too much. Stop at two levels, and keep main navigation and anything people need right now in plain view. The principle backfires when the hidden control is one someone needs now. A power user who needs a setting every day takes the extra step every day. It also backfires when the label doesn't say what is behind it.
121 min
How to spot progressive disclosure going wrong
You can check a design for these signs in a session recording, an analytics report or a support queue.
Tick each statement that is true of your design:
?7 questions
Questions people ask
What is progressive disclosure in UX?
What is progressive disclosure vs progressive enabling?
Is progressive disclosure the same as staged disclosure?
How do I use progressive disclosure in forms?
Does progressive disclosure remove features?
Does progressive disclosure reduce cognitive load?
Is progressive disclosure a law or a rule of thumb?
§7 sources
Sources for progressive disclosure
Show all 7 sourcesHide sources
Johnson and colleagues (1989), The Xerox Star: A Retrospective, IEEE Computer.
Nielsen (2006), Progressive Disclosure, Nielsen Norman Group.
Nielsen (2006), Training Wheels User Interface, Nielsen Norman Group.
Pernice and Budiu (2016), Hamburger Menus and Hidden Navigation Hurt UX Metrics, Nielsen Norman Group.
Springer and Whittaker (2018), Progressive Disclosure: Designing for Effective Transparency, arXiv:1811.02164.
W3C, Understanding Success Criterion 4.1.2: Name, Role, Value (WCAG 2.2).
UXPin, What Is Progressive Disclosure in UX? Definition, Examples & Best Practices.







