Card Sorting for Better Information Architecture
Card sorting reveals how users naturally group and label content, helping teams build information architecture around real user mental models.

Card sorting is a research method where participants sort topics or content into categories that make sense to them, which reveals the mental models people use to understand how information relates. Researchers then build information architecture around how users actually expect content to be organized, instead of around internal assumptions that may not match.
Ever opened a menu and thought, "this looks like an org chart"? It usually is one.
When navigation mirrors the team structure and not what users expect, the damage shows up in three places: high bounce rates, the same support questions arriving again and again, and content that exists but nobody finds. Card sorting fixes that by putting evidence under the structure.
What is card sorting and what does it reveal?
Hand participants a pile of topics and ask them to sort the pile into groups that feel natural. Often they name the groups too.
What comes out is their mental models: how they connect concepts, and where they'd go looking for a given piece of information. The categories that make sense to the team that built a product aren't always the ones that make sense to its users, and card sorting shows you that gap from real behavior instead of leaving you to guess how users think.
Here's a made-up example. A software team keeps "invoices," "plan changes" and "payment methods" under three different menus, because three departments own them. Then participants in a card sort keep dropping all three into one pile and labeling it "Billing." That mismatch is exactly what the method exists to catch.
How should researchers analyze and act on card sorting results?
Start by looking for three things: groupings that repeat, labels that keep coming up, and places where participants disagree.
Agreement and disagreement are both data. A pattern that repeats points to a structure most users would recognize. Disagreement marks spots where navigation and terminology may need extra clarity, or more testing.
Don't wait for a perfect structure to fall out of the numbers; it won't. Read the findings next to other evidence, because people organize information differently depending on what they're trying to do at that moment. That's card sorting for better information architecture in practice: one strong input, read with judgment.
Next question is whether the structure you propose actually works. A related method answers it: tree testing explained.
What are the different approaches to card sorting?
Two common approaches are open and closed card sorting. Hybrid sorting combines supplied categories with the option to create new ones; choose the approach to fit the study objective.
In an open card sort, participants make up their own categories and labels from scratch. You find out how users would organize information when nothing constrains them. In a closed card sort, you supply the categories and see whether participants can place content into them correctly.
When in the project you are usually decides which to run. Early on, open sorts give you mental models that aren't colored by an existing structure. Later, once someone has proposed a structure, a closed sort tells you whether it makes sense to real users.

How should a card sorting study be designed?
Carefully. A card sort can only be as good as its setup, and a weak spot in any one place (the people, the cards, the instructions) undermines what the results can show.
Four things to get right:
- Recruit people who represent the audience the information architecture is meant to serve.
- Pick content items that reflect what people really need to find.
- Write instructions nobody can get stuck on.
- Decide whether you're discovering or validating, which tells you open or closed.
If we had to pick one, it'd be the cards. Build the set from whatever happened to be on the old site and you'll get a tidy structure for the wrong content.

How PulseLake helps
PulseLake's traditional research mode supports advanced methods like card sorting alongside surveys and qualitative research, with objectives, participant data and results kept in the same persistent study context. AI agents for research design and analysis can help structure a card sort and surface grouping patterns, while researchers keep judgment over how findings turn into navigation decisions. To plan a card sorting study, talk to our team.
Frequently asked questions
How many participants are needed for a card sorting study?
No single number is required. Many teams find that a moderate sample, often fifteen to thirty participants, is enough to see clear, recurring grouping patterns. How many you need depends on how much the content and audience vary, so watch for the point where new participants stop revealing new patterns.
What is the difference between card sorting and tree testing?
Card sorting has participants create or evaluate categories by grouping content, and it's typically used to design or refine an information architecture. Tree testing has them hunt for specific items in an existing hierarchy, with no visual design, to check whether the structure works. They're often paired: card sorting informs the structure, tree testing validates it.
How do I run a card sorting exercise remotely?
Use a digital tool that lets participants do the sort on their own devices; that's a common way to run card sorting. Remote delivery can broaden geographic reach, but representativeness depends on recruitment, coverage and participation. Remote card sorts may be moderated or unmoderated. In an unmoderated study, make instructions especially clear because no facilitator is present; a remote moderator can ask follow-up questions live.
Does card sorting work for redesigning an existing website or app?
Yes. It's commonly used both to design new information architecture and to evaluate an existing one. On an existing product you can compare how users naturally group content with the current navigation, which often points to specific areas where today's organization doesn't match what users expect.



