Ser Humano Interactivo
08 / Principles

Progressive Disclosure: Showing Only What the Moment Needs

Most interfaces fail by showing everything at once. Progressive disclosure is the habit of revealing detail in the order a person actually needs it, without hiding anything they will need later.

The idea

Progressive disclosure is an interaction design technique that keeps an interface simple by presenting only the information and controls needed for the current step, and moving the rest to a secondary screen or an expandable section. The term and its history are covered in Wikipedia's article on progressive disclosure.

It is not the same as hiding. Hiding removes a choice from the person using the product. Disclosure defers it, and leaves a visible way to reach it.

Why it helps

Every element on a screen has to be read, understood and either used or dismissed. That work is what designers mean by cognitive load, the amount of working memory a task occupies; the concept is summarised in Wikipedia's article on cognitive load. Load spent on dismissing irrelevant controls is load not spent on the decision at hand.

A related and frequently misquoted source is the 1956 paper on the limits of short-term memory, discussed in Wikipedia's article on the magical number seven. It is worth reading the article rather than the slogan: the finding concerns recalling lists of items from memory, not the number of links a menu may contain. A navigation bar is not a memory test, because the options stay on the screen. The honest lesson is narrower and still useful: anything a person must hold in their head while doing something else should be short.

What it looks like in practice

Where it goes wrong

The technique is easy to misuse, usually in one of four ways.

  1. Deferring the deciding fact. Price, fees, limits and conditions are not detail. If a number changes whether someone would proceed, it belongs on the screen where they proceed. Collapsing it behind a toggle is the sneaking pattern described in the field guide to dark patterns.
  2. Burying the exit. Cancellation and account closure put three levels down are not disclosed progressively; they are obstructed.
  3. Too many stages. Splitting four fields across four screens adds taps without reducing load. Each step should be a coherent question, not a fragment of one.
  4. Invisible entrances. An expandable section with no affordance — no arrow, no label, no change of colour — is simply missing.

Deciding what goes where

A practical way to sort the elements of a screen is to ask three questions of each one:

  1. Does the common case need it? If yes, it stays visible.
  2. Could its absence change the decision? If yes, it stays visible, however inconvenient that is for the business.
  3. Is it needed only after the current step? If yes, it moves — with a label saying what is behind it.

Only the third group is a candidate for disclosure. Most crowded screens are crowded because the first group was never separated from the third.

A small illustration

Imagine a settings panel with twenty controls, of which — as an illustrative figure only — perhaps three are changed by most people. Leaving all twenty on one screen makes those three harder to find and makes the other seventeen look like decisions the person is expected to make. Showing three, with a labelled link to the rest, loses nothing and makes the panel legible.

How to test it

Give someone the task without explanation and watch where they stop. Anything they looked for and could not find was hidden rather than deferred. Then check the reverse: ask what they thought the page was asking of them. If they list things that did not matter, those elements were costing attention for nothing.

The same observation applies to larger paths, such as the ones examined in the note on reading a sign-up flow. Good disclosure makes a long process feel short. Bad disclosure makes a short process feel like a search.

And the first law of placement still applies: once something is revealed, size and distance decide whether it is easy to use.

Last revised 2026-11-15