Recall or Findability Test¶
Test or assessment — instantiates Chunked Information Design
A test that checks whether users can remember or locate a chunk from realistic cues.
Recall or Findability Test is an evaluative method: given an already-built chunk structure, it starts from a user's real question — "where do I turn off overdraft alerts?", "what's the drug-dose card?" — and measures whether they can actually reach the right chunk, and how fast. It never asks users to invent groupings; it holds the grouping fixed and puts the labels and orientation cues on trial. Its defining move is to run in the retrieval direction: from a realistic cue backward to a target chunk, scoring hit, miss, or wrong-turn. That downstream, verdict-on-a-finished-artifact stance is what separates it from a discovery method.
Example¶
A wildland fire crew carries a laminated pocket field guide — burnover survival, radio frequencies, weather red-flag thresholds, medical evacuation steps — reorganized last season into labeled chunks. Before it ships to 200 crews, the training officer runs a findability test under realistic pressure. Firefighters are read a scenario cue aloud ("the fire has jumped the line and you're about to be overrun — go") and timed on how long it takes to flip to the right chunk and read the first action.
The results expose the labels, not the content. Every tester finds "Burnover / Entrapment" in under four seconds — that chunk's label matches the words a firefighter uses in the moment. But the "Fire Behavior Watch-Outs" chunk, which actually contains the pre-entrapment warning signs, is missed by most: under stress they scan for the word "danger," not "watch-outs," and the tab color gives no hint. The fix is not to regroup the guide — the grouping tested fine last season — but to relabel that tab and add a red edge-cue so it reads as urgent. The test's output is a ranked list of chunks users couldn't reach and the wrong turns they took getting there.
How it works¶
- Recruit realistic cues, not the author's headings. Cues are phrased the way a user would actually pose the question — symptom, task, or situation — never echoing the chunk's own label.
- Choose the modality. A recall test hides the structure and asks the user to reproduce or name the chunk from memory (tests learnability); a findability test leaves the structure visible and times navigation to it (tests lookup).
- Score reachability. Record hit / miss / wrong-first-turn plus time and the path taken. Wrong turns are the richest signal: they name the label users expected to work.
- Localize the failure. Attribute each miss to a specific label or missing orientation cue, so the fix is surgical rather than a full redesign.
Tuning parameters¶
- Recall vs. findability — memory reproduction versus assisted lookup. Recall tests whether chunks are learnable; findability tests whether they're reachable with the structure in front of the user.
- Cue realism — how far the prompt is allowed to drift from the label's own words. The less it echoes the heading, the more honest the score.
- Success threshold — the time or hit-rate bar a chunk must clear; set it to the real stakes (four seconds under fire vs. thirty for a settings page).
- Cue coverage — how many of the plausible entry questions you test; sparse coverage flatters findability by missing the awkward cues.
- Stress and context fidelity — testing calm at a desk vs. under time pressure; realism catches labels that only fail when it counts.
When it helps, and when it misleads¶
Its strength is that it puts the user's own question at the center and produces a precise, per-chunk verdict on whether labels and cues do their job — the direct measure of the archetype's usability invariant. It catches the classic gap between a structure that looks organized and one a stranger can actually navigate.[1]
Its central failure mode is that it validates reachability, not rightness of grouping: a structure can score beautifully on findability while resting on a grouping that fragments a real task, because the test only probes the labels you thought to test with the cues you thought to write. Author-written cues quietly leak the answer, inflating scores; and a recall test can reward memorable-but-misleading labels. The discipline is to source cues from real user language (support tickets, search logs) rather than the author's imagination, and — crucially — to run it after a grouping method has settled the boundaries, never as a substitute for one.
How it implements the components¶
Recall or Findability Test fills the evaluation-side components — the ones that judge a finished structure:
retrieval_test— it is the retrieval test: cue in, chunk out, scored for hit and speed. This is its defining component.chunk_label— every miss and wrong turn is evidence about a specific label's fitness, so the test is how labels earn or lose their wording.orientation_cue— the test reveals where users lose their place, exposing exactly which tabs, colors, or "you are here" markers are missing or misread.
This test evaluates a structure; it does not create one. It does NOT implement raw_information_unit, grouping_principle, chunk_boundary, or semantic_coherence_check — those belong to its nearest twin, Card Sort, which discovers groupings before any structure exists; this mechanism only puts the built result on trial.
Related¶
- Instantiates: Chunked Information Design — Recall or Findability Test supplies the pass/fail evidence that the archetype's usability and testability invariants demand.
- Consumes: the built artifacts it grades, e.g. Chunked Documentation, Nested Navigation Menu, and Quick Reference Card.
- Sibling mechanisms: Card Sort · Chunked Documentation · Grouped Dashboard · Interface Sectioning · Learning Module · Nested Navigation Menu · Phase-Based Checklist · Quick Reference Card
Editorial Notes¶
Form Classification¶
Form family: Experiment, Test & Rehearsal
Rationale: Recall or Findability Test operates as an active test, trial, simulation, drill, or rehearsal that generates evidence through a deliberate attempt or perturbation because it a test that checks whether users can remember or locate a chunk from realistic cues.
Independent corroboration: The frozen evidence defines Recall or Findability Test as 'A test that checks whether users can remember or locate a chunk from realistic cues', so its operative form is Experiment, Test & Rehearsal.
Nearest alternative: Assessment, Review & Assurance — Recall or Findability Test includes features of a bounded evaluation of existing evidence or work that produces a finding or disposition, but its defining operation is an active test, trial, simulation, drill, or rehearsal that generates evidence through a deliberate attempt or perturbation.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Human-Computer Interaction
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Testing whether users can retrieve information from realistic cues is a usability method.
Related originating lineages:
- Library & Information Science — Information retrieval contributes findability and known-item search evaluation.
- Psychology — Memory research contributes unaided and cued recall testing.
Review resolution: Both blind reviewers agree that human_computer_interaction is the primary origin. Explicit reconciliation of alternate origin disagreement, encyclopedia synthesis disagreement adopts reviewer_a's classification because testing whether users can retrieve information from realistic cues is a usability method. The resulting lineage records alternates=library_information_science, psychology, origin_mode=cross_disciplinary_synthesis, and domain_reach=multi_domain; these describe formative provenance separately from later applicability.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
References¶
[1] Rosenfeld, L., Morville, P., & Arango, J. Information Architecture: For the Web and Beyond (4th ed.). O'Reilly Media (2015). Treats user navigation and findability as central outcomes of information architecture. registry ↩