B2.09.1Discoverabilitydesignresearch

Discoverability is whether users can find a function on their own

Aliases: discoverability · feature discovery · independent exploration

What it is

Discoverability is whether people, without dedicated instruction, another person's help, or accidental memory of a path, can learn that a system has a function, where to enter it, and whether it relates to their current goal. It concerns the real ability to form and traverse a usable path, not merely whether an element has been placed somewhere in an interface.

Why it happens

Discovering a function usually requires several steps: recognizing a goal, noticing a potentially relevant cue, understanding its meaning, predicting the action result, and being willing to try. A break at any point can leave a capability undiscovered. Clear naming, stable position, task-relevant signifiers, search, and timely feedforward shrink the search space; hidden hierarchy, vague terminology, and false expectation make people stop searching or conclude the system lacks support.

Studying it

Give people real goals rather than specified steps. Observe whether they independently find capability within a reasonable time, which search strategy they use, where they stall, and how they explain failure. Measure discovery separately from understanding, first-use success, and later reuse. Avoid suggesting that the function exists during testing; once a researcher names the target control, the test no longer measures discoverability.

Where it stops holding

Not every function must be immediately discoverable without guidance. Very infrequent, specialized, or high-risk capability can be supported by help, training, or controlled paths, but people should at least know how to obtain it when needed. Equating discoverability with number of visible functions causes overexposure; the question is which capabilities warrant independent discovery given task value and timing.

Applying it

  • Build a coherent path from user task language to entry to result for important goals, using familiar terms rather than internal terminology.
  • Provide multiple discovery routes—navigation, local cues, search, examples, and error-recovery prompts—while keeping them aligned to one understanding.
  • Evaluate first discovery and rediscovery through unguided tasks regularly, separating unused features that are unnecessary from those people cannot find or understand.

Related

  • Same group: B2.09.2 Visible does not mean discoverable; it must also be understandable · B2.09.3 A function that depends on teaching is undiscoverable
  • Nearby: B2.08 Visibility · B2.03 Signifiers
  • Search terms: discoverability · feature discovery · unguided task

Cards in the same group

Quick Actions

Share

Share this page

ios_share

https://hci.top/en/handbook/B2.09.1