Card Sorting
What Is Card Sorting in UX?
Card sorting is a UX research method in which people group and label cards representing content, features, or tasks. It helps teams create clearer website navigation, app menus, settings, and information architecture. Cards can represent pages, help topics, features, or tasks. The results reveal users' mental models, including the language and groupings they expect, rather than the structure assumed by the product team. NN/G's overview of card sorting explains this value.
Types of Card Sorting: Open, Closed, and Hybrid
Choose a type based on whether you are discovering a structure or checking an existing one.
| Type | Participant task | Best use | Main caution |
|---|---|---|---|
| Open | Create groups and name them. | Discovering natural categories. | Names can vary widely. |
| Closed | Place cards in provided groups. | Testing a proposed navigation. | Provided labels can steer choices. |
| Hybrid | Use provided groups or add new ones. | Refining a partial structure. | Review new groups carefully. |
How to Perform Card Sorting
Start with one navigation decision, such as structuring account settings.
- Define the menu, sitemap, or feature taxonomy to improve.
- Select representative cards, not every page or feature.
- Write neutral labels for one item each.
- Recruit people who resemble intended users.
- Run an open, closed, or hybrid sort.
- Review recurring clusters, labels, and disagreements.
- Draft navigation from the strongest patterns.
- Validate it with task-based testing.
How to Organize Cards and Write Better Labels
Keep card scope consistent. Each card should cover one capability or content item, not “billing and account help.” Avoid internal jargon, duplicate concepts, and labels requiring prior knowledge. An optional “unsure” group prevents forced choices. Billing, password reset, two-factor authentication, and profile details may belong in different groups because users distinguish payments, access, security, and personal information.
Benefits of Card Sorting
Card sorting gives design discussions evidence from intended users.
- Improves information architecture before expensive development begins.
- Suggests menu labels that match user language.
- Can make features and help content easier to discover.
- Replaces opinion-led debates with observable patterns.
- Supports planning during app design and development.
Practical Limits of Card Sorting
A sort is directional research, not proof that navigation works.
- Small or unrepresentative groups can mislead.
- Ambiguous card wording can distort results.
- People may categorize an item differently by goal.
- Aggregate results can hide minority needs.
- Sorting alone does not show whether users can complete a real task.
Card Sorting vs. Tree Testing
These methods work together because they answer different questions.
| Method | Question answered | Best time to use it |
|---|---|---|
| Card sorting | How should content be grouped and labeled? | When creating or revising a structure. |
| Tree testing | Can users find an item in this structure? | After drafting navigation categories. |
Using Card-Sorting Results in App Development
Turn strong clusters into a draft sitemap, navigation hierarchy, settings structure, or feature taxonomy. Prototype the structure and test realistic tasks before shipping. An AI app builder can quickly create an interface for iteration, while Emergent can build and refine full-stack applications from user-centered requirements. Build user-centered app navigation with Emergent.
on Emergent today

