Put common functions first and advanced functions later

What it is

Progressive disclosure initially shows the information and actions most people need for the primary task, then offers advanced, infrequent, or complex capability when people express need, enter a relevant context, or have enough experience. It is not simply hiding functions. It layers them so common paths remain clear while entries to deeper capability stay predictable.

Why it happens

Showing every option at once increases visual search, choice burden, and novice anxiety; containing everything increases discovery and repeat-access cost. Layering by task frequency, importance, and dependency lets people build a basic model first and expand it as needed. Context, stage, explicit intent, and expertise are common disclosure triggers. A good hierarchy makes a later layer feel like a natural continuation of an earlier one, not a sudden jump into an unfamiliar system.

Studying it

Analyze real function-call frequency, use sequence, user strata, and error consequence to validate which capabilities belong in the starting state. Test novice primary-path completion, expert access efficiency for advanced capability, and understanding transfer from basic to advanced separately. Observe whether people can predict where more options are and when they will appear, or incorrectly conclude a function does not exist because it is contained.

Where it stops holding

Common use is not the sole criterion: infrequent but urgent, safety-critical, or error-recovery capability must be quickly reachable when needed. Advanced users should not be forced repeatedly through teaching layers; shortcuts, pinnable panels, and preferences can reduce friction. If layering follows team-internal complexity instead of user tasks, progressive disclosure becomes an excuse to transfer product structure to users.

Applying it

• Use actual frequency, importance, time sensitivity, and expertise to choose initial, contextual, and advanced layers, rather than compressing by feature count alone.
• Give every layer stable names, predictable entries, and necessary search or shortcuts so contained advanced capability remains reachable.
• Test hierarchy in first, repeated, and exception tasks, monitoring primary-path interference, undiscovered hidden functions, and harmed expert efficiency.

Related

• Same group: B2.13.2 Layering must not make users guess entry location · B2.13.3 Excessive layering turns simplicity into concealment
• Nearby: B2.08.3 Visibility directly conflicts with simplicity and requires frequency-based tradeoffs · B2.09 Discoverability
• Search terms: progressive disclosure · feature hierarchy · expertise