Interpretation boundary

A card sort is evidence for a draft, not approval for a navigation.

Short answer: a card sort observes how participants group and label a selected card set under a specific task. It does not test whether users can find real content in a hierarchy, understand navigation in context, complete tasks, use the interface with assistive technology, or succeed after implementation.

What card sorting can illuminate

What it does not directly test

ClaimWhy the card sort is insufficientPossible follow-up
Users can find item XGrouping does not require navigating a hierarchy under a realistic task.Tree testing or task-based usability testing
The label is clearA participant-created or frequently used phrase can remain vague in navigation context.Comprehension, first-click, or usability testing
The hierarchy is accessibleThe sort does not test implemented semantics, focus, announcements, zoom, or assistive technology.Accessibility review and assistive-technology testing
The structure scalesThe study uses a bounded selected card set, not every future content type or governance change.Content modelling and governance stress test
The result generalizesSample, recruitment, task, language, and inclusion choices bound the evidence.Research design review and additional studies
The cluster is correctLinkage and threshold choices can change cluster membership.Method-sensitivity reporting and follow-up validation

Why the candidate structure is separate

The field lab copies one cluster cut into a new editable structure. Renaming, moving, parking, splitting, and merging cards changes only the draft. The source analysis fingerprint remains attached. This prevents a polished draft from being mistaken for the exact computed result.

A stronger decision chain

  1. Frame the question and recruit for the actual audience.
  2. Run and review the card sort.
  3. Compare raw evidence and analysis methods.
  4. Draft an information structure with content, business, and governance constraints.
  5. Test findability with realistic tasks.
  6. Prototype and test navigation in context.
  7. Review accessibility, content quality, analytics, support evidence, and operational ownership.
  8. Document what changed and why.
Avoid outcome language the study cannot support. Say “seven included responses grouped A and B together in six cases” rather than “users expect A and B together.” Say “candidate draft” rather than “validated IA.”