A function that depends on teaching is undiscoverable
Aliases: instruction-dependent feature · undiscoverable function · first use
What it is
If people can notice a function and use it successfully only after seeing a tutorial, receiving training, being told by a colleague, or knowing the exact path already, then it is undiscoverable from the standpoint of independent use. An instruction-dependent feature need not lack value, but its adoption, learning, and support costs must be part of the design judgment. The existence of training is not evidence that the interface itself is discoverable.
Why it happens
Teaching temporarily supplies missing entries, terminology, action order, and outcome expectation. People who have just learned may perform well because they remember steps, not because they can infer them again from present cues. After time, device change, or a slightly different context, that external support vanishes and the problem returns. Teams that test trained users only can overestimate a function's independent usability.
Studying it
Test people new to the product separately from people who completed instruction. Compare independent discovery, understanding, completion, delayed return, and contextual transfer. Record what each teaching element actually supplied: feature existence, entry location, action rule, or risk boundary. If people cannot explain why an action works after instruction, they may be imitating procedure rather than retaining durable understanding.
Where it stops holding
Formal training may be reasonable or necessary for highly specialized, rare, or regulated tasks; the goal is not to make every capability spontaneously discoverable. Even there, an interface should help trained people recall, inspect, and recover safely rather than demand permanent memorization. For public-facing, critical-path, or error-recovery capability, dependence on one-time teaching is generally an unacceptable risk.
Applying it
- Specify which capabilities may reasonably depend on training and which must be discoverable without guidance, then set acceptance tests accordingly.
- Bring key tutorial explanations back into the interface with clear entries, local cues, searchable help, and contextual feedforward rather than a one-time walkthrough alone.
- Test delayed return and variant tasks; when people cannot recover after forgetting instruction, improve interface cues or provide retrievable support.