Designing Settings: Progressive Disclosure
By Maksym Bardakh · Co-founder & President
In short
A settings screen has to serve two audiences at once: most users who want a few common options, and a minority who need advanced control. Progressive disclosure resolves the tension by showing the common settings plainly and tucking advanced ones behind a clear path, so the screen is simple for the many without removing power from the few.
Settings serve two audiences
A settings screen faces a structural problem. Most users want to adjust a handful of common things and would be overwhelmed by a long list. A smaller group needs fine-grained control and is frustrated when it is missing. Designing for one audience tends to fail the other: a minimal settings screen frustrates power users, while an exhaustive one buries the common options that most people came for.
The mistake is treating this as a single list to be ordered correctly. It is better understood as two layers of need, and the design challenge is to serve both without compromising either.
Progressive disclosure as the answer
Progressive disclosure is the technique of revealing complexity gradually, showing what most users need first and making the rest reachable for those who look. Applied to settings, it means the common options are visible and obvious, while advanced options live one clear step deeper, available but not in the way.
- Surface the settings most users actually change, prominently and plainly.
- Place advanced or rarely changed settings behind a clearly labeled path.
- Make the advanced area discoverable, so power users know it exists without it cluttering the main view.
Organize by the user’s model, not the system’s
Settings are often organized the way the software is built rather than the way the user thinks, which makes them hard to navigate. Grouping settings by what the user is trying to accomplish, and labeling those groups in the user’s language, lets a person find a setting by reasoning about their goal rather than guessing at the system’s internals.
Good defaults make settings optional
The most effective way to simplify settings is to need fewer of them. Every setting represents a decision the product declined to make and handed to the user, and many of those decisions are better made by the product with a sensible default. A good default means most users never open the setting at all, which is the simplest settings experience there is.
The combined approach is to choose strong defaults so settings are rarely needed, surface the common ones clearly for when they are, and place advanced control a clear step deeper for those who want it. Settings designed this way feel simple to most users and complete to the few who need depth, which is exactly the balance a good settings screen should strike.
Key takeaways
- Settings must serve both common users and power users without failing either.
- Progressive disclosure shows common options plainly and tucks advanced ones a step deeper.
- Keep advanced settings discoverable so power users know they exist.
- Organize and label settings around the user’s goals, not the system’s structure.
- Strong defaults reduce how many settings the user ever needs to open.
Frequently asked questions
- What is progressive disclosure in settings?
- Revealing complexity gradually: showing the settings most users change plainly while placing advanced or rarely used options one clear step deeper, so the screen stays simple without removing power.
- How should settings be organized?
- Around the user’s goals and in the user’s language, rather than mirroring the software’s internal structure, so a person can find a setting by reasoning about what they want to accomplish.
- How do good defaults help settings?
- Every setting is a decision handed to the user. Strong defaults let the product make many of those decisions well, so most users never need to open the setting at all.
References
About the author
Maksym Bardakh
Co-founder & President
Maksym is a software engineer and product strategist focused on executive-function and behavioral system design. At BBMM he leads product direction across Flowo, TextPack, and Pillow, working at the intersection of human cognition and durable interface design.