Progressive-Disclosure Failure¶

Diagnose an interface's usability breakdowns as a single mistuning between its staging schedule and the readiness of the users and tasks it actually meets, read off by whether too much is hidden or too much exposed.

Core Idea¶

Progressive-disclosure failure is the interaction-design pathology in which an interface's staging schedule — the rule setting which information or controls are visible at each point of engagement — is mistuned to the actual population of users and tasks it must serve. Progressive disclosure as a principle is correct; the failure is the fit. Either too much is hidden (a needed capability cannot be found) or too much is exposed too early (optionality overwhelms and users misconfigure or abandon).

Scope of Application¶

The pathology lives across HCI wherever an interface stages visibility against a heterogeneous user-and-task population.

Medical-device interfaces — infusion pumps and ventilators burying emergency controls under routine-use menus.
Public-service wizards — benefits or tax flows hiding eligibility branches that later apply.
Education platforms — mastery gates unlocking too late for fast learners, too early for slow ones.
Control-room HMIs — alarm filtering that buries the signals an operator needs in an abnormal situation.
Consumer-software onboarding — feature tours exposing too much too early or hiding capabilities forever.

Clarity¶

The name separates two corrective directions that surface complaints blur together: "I couldn't find it" wants capability surfaced, while "there's too much going on" wants suppression. It also treats the disclosure schedule as a first-class, measurable parameter, so the unfalsifiable "is this interface intuitive?" becomes the inspectable "where does the schedule diverge from the population it serves?"

Manages Complexity¶

A motley family of usability complaints — found too late, overwhelming, abandoned mid-flow — collapses onto one design parameter, the disclosure schedule, and one tracked quantity, its gap against the user-readiness distribution. The sign of that gap selects the remedy directly, and the same parameter explains why a schedule locally optimal on the modal task can still be fatal on the long tail.

Abstract Reasoning¶

The frame licenses a diagnostic that classifies a complaint by the sign of the schedule-readiness gap, a move that makes the schedule a measurable parameter interrogated with task-flow telemetry, a predictive move anticipating long-tail failure from a modal-tuned schedule, and an interventionist move that adds escape hatches sized to the un-served tasks rather than exposing everything.

Knowledge Transfer¶

Within interaction design the frame transfers as mechanism across every interface substrate — consumer onboarding, medical devices, wizards, control-room HMIs, education platforms — because each literally has a staging schedule, a heterogeneous population, and telemetry against which the gap is measured, so the intervention toolkit moves as engineering. Beyond interaction design the portable content belongs to the parent scaffolding (support calibrated to a changing state); once there is no staged visibility, the HCI machinery has no referent and the named concept dissolves into scaffolding, with attentional_capacity and signal_decay picking up side-effects.

Relationships to Other Abstractions¶

Current abstraction Progressive-Disclosure Failure Domain-specific

Parents (1) — more general patterns this builds on

Progressive-Disclosure Failure presupposes Progressive Disclosure Prime

Progressive-Disclosure Failure presupposes an attempted Progressive Disclosure schedule whose layer exposure is mistuned to users and tasks.

Hierarchy path (1) — routes to 1 parentless root

Progressive-Disclosure Failure → Progressive Disclosure → Layering

Neighborhood in Abstraction Space¶

Progressive-Disclosure Failure sits in a crowded region of the domain-specific corpus (37^th percentile for distinctiveness): several abstractions share nearly its structure, so a description that fits it tends to fit its neighbors too.

Family — Interface Legibility & Navigability (12 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-07-12