tezvyn:

Card Sorting: Let Users Design Your Navigation

AI-drafted, machine-checkedSource: Wikipedia: Card sortingadvanced

Card sorting reveals your users' mental models by having them group topics. Use this to design intuitive navigation menus and information architecture. The footgun is testing with internal teams instead of actual users or subject matter experts.

WHY IT EXISTS Designers and internal teams often develop an 'expert's curse,' organizing information in a way that makes sense to them but is confusing to new users. A logical internal structure might not match how a customer thinks. Card sorting was created to bridge this gap by directly sourcing the navigational structure from the user's perspective.

THE MENTAL MODEL Think of card sorting as handing someone a messy pile of your books and asking them to organize them into piles on the floor. You're not just getting an organized library; you're learning how they think about categories. Do they group by author, genre, or publication date? That insight into their mental model is the real goal.

HOW IT WORKS Individual concepts or features are written on cards, either physical or digital. Participants, who should be representative users or subject matter experts, sort these cards into groups that make sense to them. In an 'open' card sort, participants also create names for their groups. In a 'closed' card sort, they sort cards into predefined categories. The results are analyzed to identify common groupings and naming conventions, which can be visualized in a dendrogram (a tree diagram) to reveal the information hierarchy.

WHEN TO USE IT Use card sorting early in the design process for a new website, app, or intranet to build a user-centered information architecture from the ground up. It is also valuable when redesigning a site where analytics show users are getting lost. It helps define menu structures, workflow steps, and website navigation paths.

WHEN NOT TO USE IT Card sorting is not for testing the usability of an existing navigation design; that's a different method called tree testing. It's also less effective for very small sets of content where the structure is obvious. Its purpose is to discover how to structure information, not to validate a specific, pre-built structure.

ONE CANONICAL EXAMPLE A university redesigning its website writes key pages on cards: 'Financial Aid,' 'Course Catalog,' 'Campus Map,' 'Admissions,' 'Student Housing.' They run an open card sort with prospective students. They discover students consistently group 'Financial Aid' and 'Admissions' under a label like 'Getting Started,' a grouping the internal team hadn't considered. This insight directly informs the new main navigation menu.

Read the original → en.wikipedia.org

Get five bites like this every day.

Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.