Show Less, Then Let Them Ask for More

When a product does a lot, there's a strong pull to show all of it at once. Every option on the screen, every setting visible, every piece of information laid out so nothing is missed. It feels thorough. To the person using it, it looks like a wall.

People can only take in so much at a time. A screen with forty options doesn't feel powerful. It feels confusing, and the three options someone actually needs get lost among the thirty-seven they don't.

Sequencing, not hiding

Progressive disclosure means showing what people need first and making the rest available when they ask for it. The word that matters is sequencing. Nothing is removed. It's arranged in the order people need it.

A good example is a search page. Most people type a word and press enter. A few want to filter by date, category or price. The search box comes first, and the filters are one click away. Everyone gets what they need, and nobody is overwhelmed.

Deciding what comes first

The hard part is deciding what goes up front. We base it on what most people do most often. If nearly everyone uses three features, those three are visible. The rest sit behind a clear link, an expandable section or a second step.

This needs real information. We look at analytics on existing products, talk to the people who use them and test early designs. Guessing tends to put the features the team is proudest of at the front, which isn't always the same thing.

Patterns we use

There are several ways to reveal more. Expandable sections, such as accordions, work well for FAQs and long pages where people want to scan headings and open the one they need. "Show more" links let a list start short. Advanced settings can sit in their own section, clearly labelled. Multi-step forms reveal questions gradually, often showing follow-up questions only when an earlier answer makes them relevant.

Each pattern has a cost. Every click to reveal something is a small effort, and hidden content is easy to miss. So we keep the number of levels low. One extra step is usually fine. Three levels of nested menus is a maze.

Making it obvious there's more

Disclosure only works if people know there's something to reveal. A link that says "More options" or "Advanced settings" makes it clear. A small arrow on an expandable section shows it can open. What doesn't work is content tucked behind an unlabelled icon or a gesture nobody knows about.

The label should also describe what's behind it. "Delivery and returns" is better than "More info", because people can tell whether it's worth opening.

Where it goes wrong

Progressive disclosure can be overdone. Hiding essential information, like prices or key terms, behind extra clicks frustrates people and erodes trust. Content in collapsed sections can also be overlooked by visitors who never think to open it. We're careful about what we tuck away: anything people need to make a decision stays visible.

Calmer products

Done well, progressive disclosure makes complex products feel simple without making them less capable. New users see a calm starting point and learn gradually. Experienced users know where everything is and can get to it quickly. It's one of the most useful tools we have in app development, and it's just as valuable on content-heavy websites.

If your product or site feels crowded, the answer might not be cutting features. It might be choosing a better order. We'd be glad to help.