What it is
A method where participants sort items into groups, and sometimes name those groups, revealing how users expect content and features to be organized.
When to use it
During Synthesize, when designing or revising information architecture, navigation, or categories.
Why (value)
Grounds structure in users’ mental models rather than internal org charts, improving findability.
How to run it
- Choose the items to sort and write them as cards.
- Pick open (users name groups) or closed (fixed groups).
- Have participants sort and think aloud.
- Capture groupings and labels.
- Analyze agreement and build a proposed structure.
Inputs and outputs
- Inputs: A content set, participants, a sorting tool.
- Outputs: Grouping patterns, label language, a candidate IA.
Time and effort
Medium. 30 to 45 minutes per participant plus analysis.
Evidence and limitations
Yields direct-user evidence about expected grouping, but reflects categorization preference, not task success; validate the resulting structure with tree testing. See Evidence and limitations.
Tips and pitfalls
- Keep the card set manageable, roughly 30 to 60 items.
- Use open sorts to discover, closed sorts to validate.
- Follow with tree testing to confirm findability.
Variations
Open, closed, hybrid; moderated or unmoderated; in person or online.
Related methods
Need help planning research or facilitating this method?
Gumshoe helps teams connect research, collaborative workshops and service design to the decisions they need to make.
Sources and further reading
- UX Tigers, “100 UX methods.”
- 18F Methods (US government, public domain).
- NN/g, “Card Sorting: Uncover Users’ Mental Models for Better Information Architecture.”
Explore related methods
- Tree testing — Test whether people can find things in your structure, stripped of visual design.
- Taxonomy design — Design the categories and labels that organize content so people can find things.
- Sitemapping — Map the hierarchy and structure of a site or app's pages and sections.
