B2.09.2Comprehensible discoverabilitydesignresearch

Visible does not mean discoverable; it must also be understandable

Aliases: comprehensibility · discoverability · meaningful cue

What it is

An element that exists on screen—even a conspicuous one—does not automatically let people discover that it helps them meet their goal. Comprehensible discoverability requires them not only to notice an entry, but also to interpret its name, form, location, and current state as relevant to what they need and as something whose next result they can anticipate. Visibility answers “was it seen?”; understanding answers “what does it mean, and can it help?”

Why it happens

People filter visual information by goal rather than read every element. An unfamiliar icon, internal term, vague category, or context-free control can be judged irrelevant, unavailable, or risky even when in plain sight. Understanding depends on semantics, signifiers, mapping, and feedforward together. Increasing contrast or size normally raises the chance of being noticed, but does not establish a correct action prediction.

Studying it

In goal-driven tasks, ask participants to identify elements they notice, explain what each is, and say what they would use it for, then observe actual choice. Record separately the shares who did not see it, saw but misunderstood it, understood but did not trust it, or did not wish to try. Compare icons, text labels, examples, and contextual explanation to identify which information connects a goal to an entry correctly.

Where it stops holding

Understanding does not require writing a long explanation for every control. Familiar conventions, clear grouping, and suitable placement can support comprehension with little information; the key is verifying that target users share those premises. Overexplanation can submerge primary content and make a simple action feel complex. For novel or consequential actions, it is better to supply needed feedforward than to hope people guess correctly.

Applying it

  • Name entries in user task language and support them with form, icon, and adjacent context that convey action or outcome, rather than relying on visual prominence alone.
  • Add a short example, preview, or state explanation beside ambiguous or consequential functionality so people can assess relevance and result before acting.
  • Diagnose “seen,” “correctly interpreted,” “tried,” and “used successfully” as separate measures, then repair the broken link.

Related

  • Same group: B2.09.1 Discoverability is whether users can find a function on their own · B2.09.3 A function that depends on teaching is undiscoverable
  • Nearby: B2.08 Visibility · B2.03 Signifiers
  • Search terms: discoverability · comprehension · meaningful cue

Cards in the same group

Quick Actions

Share

Share this page

ios_share

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