“People ignore designs that ignore people” Frank Chimero
Staged vs Progressive Disclosure
When should we use progressive or staged disclosure? Do you use a flexible system or one more rigid than a stone?
Progressive disclosure is a strategy that has been in use for more than 30 years, the sister of the Wizard. Its purpose is the feature management, creating a flexible system adapted to junior users who do not know how to use the application or web itself, minimizing the errors rate and giving the possibility to the most experienced users in the form of a very powerful toolbox.
Look at your Chrome browser, if you go to settings, you will see a limited amount of options, which thanks to card sortings and % of use are the most used, but we always have clearly available the advanced options, this is the progressive disclosure, offers power and simplicity, while improving the principles of usability of learnability, efficiency of use and error rate.
On the other hand, the staged disclosure (like the Wizard), shows initially one step of the process, divides the information in equally important fragments, has a linear progression and improves the usability principle of simplicity; while the progressive disclosure shows initially the most important functionalities, its navigation is hierarchical, hides the secondary functionalities and improves the learnability. A good example of staged progression would be Typeform.
Use staged progression when the interaction is simple and information can be divided or semantically grouped.
What should I consider? Divide the information carefully by using card sortings, links and self-describing labelled buttons of what is going to happen in the interaction, and be very cautious when using more depth levels or several secondary levels.
You can practice by looking for three applications/webs that use the progressive disclosure pattern and another three that use staged disclosure.