In a usability test a few years ago, a user explained: "When I search for something, first I look at the first three items...looking for general information and then I look for more specific items..."
In its most formal definition, progressive disclosure means "to move complex and less frequently used options out of the main user interface and into secondary screens". Progressive disclosure says: Make more information available within reach, but don't overwhelm the user with all the features and possibilities.
Seems easy enough, right? Yes it does, however, the problem with proper implementation of progressive disclosure I have found is that you have to have user intelligence to use the technique sensibly.
Here are some examples (also covered in my definition on Interaction Design encyclopedia site):
1. The best way to think about progressive disclosure on the web is: "Only show information that is relevant to the task the user wants to focus on, on any given page".
Design perspective required: What do user's really need to complete their tasks and goals?; What are their specific tasks/needs or goals relevant to this screen/page, or area?
2. Progressive disclosure can be powerful. It allows users to orient to a screen, figure out what they need to do, and do it in steps that reveal more complex information as they go along.
Design perspective required: What steps should be grouped vs. split? How much complexity can you unleash and at what point in the experience?
What's new with solving the problem of progressive disclosure? New JavaScript and AJAX interface techniques hold great promise for resolving progressive disclosure elegantly.
Source: Spillers, Frank 2008, Interaction-Design.org Encyclopedia: Progressive Disclosure definition
Frank Spillers' Comment:
Progressive disclosure is often treated as a no-brainer, because it makes so much sense. However, just like pulling weeds out of a garden makes sense, you have to know how to identify a weed from a plant to do a good job. Several years ago I led a design meeting review of a 'sign up for early access to a developer toolkit' wizard. The existing process had 8 steps. After much careful maneuvering, we reduced the process to 3 steps retaining 90% of the same content and business requirements. The usability goal was to improve perceived ease of use as much as actual ease of use. How did we achieve this? In order to "push" users through the process we created 3 core steps with many mini-steps or progressive disclosures off the main step.
Related Articles:
Progressive Disclosure- the best interaction design technique?