VOCABULARY / ENTRY

Recognition Rather Than Recall

recognition

Add to comparison +

Principles & cognitionScope: Flowrecognition · v0.1.0

Make objects, actions, and options visible so people need to retrieve less operating information from memory.

Interactive specimen · Fictional product FIELDNOTES

Choose a note category

Recognizing it

Explicit option names
Cues near the relevant task
No requirement to memorize internal codes

Concept boundary

This does not mean showing every option at once. Visibility still needs suitable grouping, search, or disclosure.

When to consider it

People are unfamiliar with commands, category codes, or action names
Tasks span steps and earlier information is easily forgotten

When to be cautious

Showing many low-relevance options at once and making scanning harder
Assuming experienced people never benefit from command shortcuts

Tradeoff

It reduces reliance on memory but takes display space and adds scanning effort.

Conditional rules · Editorial advice

When People need to choose a categoryRecommendedShow human-readable choices instead of requiring an internal code alone.

Related entries

Progressive Disclosure ↗Works with · Primary options are visible and secondary options have clear entry points

Balances visibility with the amount of information shown.

Inclusive Design ↗Explains · Considering differences in memory and cognition

Visible cues can be one inclusive-design strategy.

Sources and what they support

NN/g · Memory Recognition and Recall ↗

Recognition uses cues; recall retrieves information from memory. Visible interface information can reduce memory demands.

Retrieved: 2026-09-15

Definitions reference these sources. Digital specimens, selection advice, relationships, and recipes are editorial work and have not been validated through user research.

Type extensions and implementation notes

Capability tags describe this specimen only; verify the implementation again in a real product.

{
  "evidenceType": "A usability heuristic and explanation of memory mechanisms",
  "limit": "Does not establish that every selection list is faster than text input."
}

Full Agent entry JSON

{
  "id": "recognition",
  "type": "principle",
  "name": {
    "zh": "识别优于回忆",
    "en": "Recognition Rather Than Recall"
  },
  "aliases": [
    "Recognition over Recall",
    "识别而非记忆",
    "减少记忆负担"
  ],
  "granularity": "flow",
  "intents": [
    "find-option",
    "reduce-complexity"
  ],
  "tags": [
    "memory",
    "visible options",
    "beginners",
    "finding",
    "cues"
  ],
  "definition": "Make objects, actions, and options visible so people need to retrieve less operating information from memory.",
  "boundary": "This does not mean showing every option at once. Visibility still needs suitable grouping, search, or disclosure.",
  "signature": [
    "Explicit option names",
    "Cues near the relevant task",
    "No requirement to memorize internal codes"
  ],
  "when": [
    "People are unfamiliar with commands, category codes, or action names",
    "Tasks span steps and earlier information is easily forgotten"
  ],
  "when_not": [
    "Showing many low-relevance options at once and making scanning harder",
    "Assuming experienced people never benefit from command shortcuts"
  ],
  "tradeoff": "It reduces reliance on memory but takes display space and adds scanning effort.",
  "comparison": {
    "focus": "Whether people need to remember information",
    "mechanism": "Providing recognizable cues and options",
    "cost": "Space and scanning costs of visible information"
  },
  "sources": [
    {
      "id": "nng-recognition",
      "title": "NN/g · Memory Recognition and Recall",
      "url": "https://www.nngroup.com/articles/recognition-and-recall/",
      "claim": "Recognition uses cues; recall retrieves information from memory. Visible interface information can reduce memory demands.",
      "checkedAt": "2026-09-15",
      "archive": {
        "lookupUrl": "https://web.archive.org/web/20260915*/https://www.nngroup.com/articles/recognition-and-recall/",
        "status": "available",
        "checkedAt": "2026-09-15T16:51:46.175Z",
        "jobId": "spn2-4737f90b20212bd3fcf7ceac62283e1adde76b31",
        "url": "https://web.archive.org/web/20260915165213/https://www.nngroup.com/articles/recognition-and-recall/",
        "timestamp": "20260915165213"
      }
    }
  ],
  "relations": [
    {
      "target": "progressive-disclosure",
      "kind": "composes_with",
      "condition": "Primary options are visible and secondary options have clear entry points",
      "reason": "Balances visibility with the amount of information shown.",
      "basis": "editorial"
    },
    {
      "target": "inclusive-design",
      "kind": "informs",
      "condition": "Considering differences in memory and cognition",
      "reason": "Visible cues can be one inclusive-design strategy.",
      "basis": "editorial"
    }
  ],
  "rules": [
    {
      "when": "People need to choose a category",
      "instruction": "Show human-readable choices instead of requiring an internal code alone.",
      "strength": "recommend",
      "basis": "editorial"
    }
  ],
  "principle": {
    "evidenceType": "A usability heuristic and explanation of memory mechanisms",
    "limit": "Does not establish that every selection list is faster than text input."
  },
  "demo": "recognition",
  "version": "0.1.0",
  "editorialStatus": "sample-reviewed",
  "requirements": [],
  "demoCapabilities": [
    "keyboard",
    "reduced_motion"
  ],
  "implementationNote": "Capability tags describe this specimen only; verify the implementation again in a real product.",
  "searchTerms": [
    "记忆",
    "可见选项",
    "新手",
    "查找",
    "提示"
  ]
}