Skip to content
Design Academy My progress

Stage 3 · Lesson 3 of 10

Card sorting and tree testing

Two methods that show how people expect content to be organised.

  • Beginner
  • 40 min
  • 3 check questions
  • Exercise: 1 h 30 min

By the end of this lesson you can

  • Run an open or closed card sort to learn how users group content.
  • Run a tree test to check whether people can find items in a structure.
  • Interpret results and use them to improve a structure.

The idea

Two methods help you design and validate a structure with real users.

Card sorting

In a card sort, participants group content items written on cards. In an open sort, they create and name their own groups, which reveals how they think about the content. In a closed sort, they place cards into categories you provide, which checks whether your categories make sense. Card sorts can be run on paper or online; 15 to 30 participants give useful patterns for online sorts.

Tree testing

A tree test shows participants only the text structure (the "tree") with no visual design, and asks them to find items: "Where would you go to change your delivery address?" You measure whether they succeed, whether they went straight there, and where they went wrong. Because there is no design, it tests the structure and labels alone.

Using them together

A common sequence: open card sort to generate ideas, draft a structure, tree test it, revise, tree test again. Card sorting is generative; tree testing is evaluative.

Why it matters in real projects

Designers and stakeholders tend to organise content the way they understand it, which is rarely how users do. These methods replace opinion with evidence before anything is built, when changes are cheap. Tree tests in particular give clear success rates that are easy to share and compare between versions.

A realistic example

An outdoor clothing shop is restructuring its menu. An open card sort with 25 customers shows that people group by activity ("hiking", "running") more often than by product type ("jackets", "trousers").

The team builds a structure with activity as a main route and product type as a secondary one. A tree test with eight tasks shows strong success for most, but only 35% of people find "waterproof trousers" because they look under "Hiking" rather than "Rain wear". The team adds waterproof trousers in both places and renames "Rain wear" to "Waterproofs". A second test raises success to 78%.

Step by step

  1. Choose items

    Pick 30 to 60 representative content items, written in plain language.

  2. Run an open sort

    Ask participants to group and name cards. Use a tool or paper.

  3. Analyse groupings

    Look at which items are often grouped together and what names people choose.

  4. Draft a tree

    Build a text-only hierarchy from the results.

  5. Write tree test tasks

    Write 8 to 10 realistic tasks that do not use the exact label words.

  6. Test and iterate

    Run the tree test, find failure points, revise and test again.

Common mistakes

  • Mistake Using labels in tasks ("Find Account settings").

    Instead Describe the goal in users' words ("Change the email you log in with").

  • Mistake Treating card sort results as the final structure.

    Instead Use them as input, then test the structure with a tree test.

  • Mistake Too many cards.

    Instead Keep sorts to a manageable number so participants do not tire.

Check your understanding

Choose an answer, then check it. There is an explanation either way.

Question 1 of 3Which method reveals how users would group content themselves?
Show answer

Open card sort. In an open sort participants create their own groups.

Question 2 of 3What does a tree test evaluate?
Show answer

Whether people can find items in a structure using labels alone. Tree tests isolate structure and labels.

Question 3 of 3Why avoid label words in tree test tasks?
Show answer

Participants match words instead of thinking about meaning. Word-matching inflates success rates.

Practice exercise

Exercise · about 1 h 30 min

Card sort and tree test

Run a small card sort and tree test for a recipe website.

Steps

  1. Write 30 cards (recipes, articles, tools, account features).
  2. Run an open sort with at least five people.
  3. Build a tree and write six tasks.
  4. Run a tree test with five people and record success and paths.

Deliverable

Card sort results, your tree, task list and tree test findings.

Self-assessment

Tick each item when it is true of your exercise. Be honest; this is for you.

4 items

Summary

  • Card sorting shows how users group content.
  • Open sorts generate ideas; closed sorts check categories.
  • Tree tests check whether people can find things in a structure.
  • Use them in sequence and iterate.

Further reading

Third-party sources, chosen for reliability. They open in a new tab.

Your notes

Marking complete updates your course and roadmap progress.

Back to Information architecture Roadmap