Card Sorting: Running and Analyzing a Study

Learn the practical steps to prepare, facilitate, and analyze a card sorting study to uncover user mental models. You will gain the skills to translate raw sorting data into a clear site map and content hierarchy that reduces user friction. Learning Objective: By the end of this lesson, learners will be able to execute a card sort study and synthesize results into an information architecture. Transcript Define the Study Scope and Inputs Preparation starts by defining your study scope and selecting the right sort type for your specific goals. You must decide whether your project requires an open sort where users create their own groups and titles, or a closed sort where they place items into pre-defined categories. This choice dictates how you structure the session and what kind of data you will ultimately collect. Next, audit your content source to create a comprehensive list of items for your cards. These content items might include articles, documents, videos, or photos that need organizing within your information architecture. Once your list is ready, you choose your card format, which means preparing either physical cards for in-person observation or digital equivalents for remote sessions. Your environment setup depends entirely on whether you are facilitating locally or using a remote tool configured for digital sorting. You also need to ensure your participant count is sufficient to allow common patterns to emerge statistically across multiple sessions. Without enough participants, you won't see the recurring groupings necessary to build a reliable structure. The tangible output of this phase is a ready-to-use deck of cards and a clear understanding of whether the session will be open or closed. This preparation sets the stage for data collection and ensures you are ready to observe genuine user behavior. When you walk into the facilitation phase, you will be watching how users group items and label categories to reveal their mental models. Key Points: Decide between an open sort (participants create groups/titles) or a closed sort (participants use predefined categories) Prepare content items: a list of articles, documents, videos, or photos requiring organization Set up the environment: physical cards for in-person observation or a remote tool for digital sorting Ensure participant count is sufficient to allow common patterns to emerge statistically Facilitate the Sorting Session Let's say you have a participant sitting in front of a deck of cards, ready to begin the sorting process. Your primary job is to guide them through the task while remaining completely neutral so their natural behaviors can surface without influence. Whether they are working with physical cards or digital equivalents, you must resist the urge to offer suggestions or correct their choices. You need to observe grouping logic by watching how users cluster items together to understand their mental models. This means paying close attention to which content sources, like articles or videos, they place in the same pile. Because these groupings reveal how users mentally organize information, your observational notes become the raw data for your future site map. Simultaneously, you must monitor labeling to listen to how users name their groups and reveal their specific vocabulary. When a participant creates a title for an open sort or selects a label in a closed sort, you are hearing their expectations directly. This specific language is crucial because it tells you exactly what terms your final content hierarchy should use to make sense to them. The most valuable insights often come from identifying friction where users hesitate, disagree with a category, or express confusion. Do not smooth these moments over, as they highlight exactly where the current structure fails the user. Instead, actively document these areas of disagreement because they represent common areas of confusion or disagreement that need resolution. The session concludes only when the participant has finished sorting all items and labeling their groups. At this point, you have a set of sorted cards and detailed notes on user behavior that are ready for the next phase. These observations will directly feed into your pattern recognition and conflict resolution steps to build a robust information architecture. Key Points: Observe grouping logic: Watch how users cluster items to understand their mental models without influencing choices Monitor labeling: Listen to how users name their groups to reveal their specific vocabulary and expectations Identify friction: Actively note moments where users hesitate, disagree with a category, or express confusion Conclude the session only after the participant has finished sorting all items and labeling their groups Analyze Results and Build Architecture Pause and think about the last card sort you ran. Did you notice where users hesitated, or did you smooth over their confusion? Those moments of friction are actually your most valuable data points, revealing exactly where your current structure fails the user. Now, look at your observational notes to begin pattern recognition. You need to review all sessions to find recurring groupings and labels across different participants. This isn't about one person's opinion; it's about finding the collective mental model that emerges from the data. Next, move into conflict resolution by identifying common areas of disagreement. Did users struggle to decide where specific items belonged? Documenting these points of confusion is essential because it highlights the gaps in your current information architecture. Once you have resolved these conflicts, proceed to hierarchy construction. Use the identified patterns to draft a site map that organizes your content sources into logical categories and subcategories. This step transforms your raw observations into a tangible structural design. Finally, translate these insights into a proposed information architecture that reflects the collective mental models of your user base. Your final site map should prioritize the most common user patterns while directly addressing the areas of confusion you identified. This ensures your new structure actually reduces friction for the people using it. Key Points: Pattern recognition: Review all sessions to find recurring groupings and labels across different participants Conflict resolution: Identify common areas of confusion or disagreement where users could not decide on categorization Hierarchy construction: Use identified patterns to draft a site map organizing content into categories and subcategories Translate insights: Convert the proposed information architecture into a structure reflecting collective user mental models Recover from Execution Challenges A frequent error is failing to distinguish between open sorts and closed sorts, which leads to inconsistent data where some users create categories while others use provided ones. You must clarify instructions by reiterating the specific rules of the sort before the session begins to ensure every participant understands their task. This simple step prevents the confusion that derails your entire analysis. Watch out for the tendency to smooth over moments of hesitation, because those friction points are often your most valuable insights. Instead of helping them move on, focus on friction by actively documenting where users struggle to decide how to categorize specific items. These disagreements highlight exactly where your current structure fails the user. Another critical breakdown occurs if the items you prepared do not accurately reflect the actual content source, such as a company intranet. You need to revisit content sources to verify that every card represents a real article, document, or video found in your system. Without this accuracy, your resulting site map will not match the reality users face daily. Key Points: Clarify instructions: Reiterate the rules of the sort (open vs. closed) before the session begins to ensure consistency Focus on friction: Document moments of hesitation or disagreement rather than smoothing them over, as these highlight structural failures Revisit content sources: Ensure the items being sorted accurately represent the actual content source, such as a company intranet Apply to Your Next Project In your next project, start by auditing your content source to create a comprehensive list of items for your cards. This step ensures your deck accurately represents the actual articles, documents, and videos you need to organize. Without this foundation, your data will lack the relevance needed to inform a real solution. Decide if your current project requires an open sort to explore new structures or a closed sort to validate existing categories. An open sort lets users create their own groups, while a closed sort tests how well they fit into your predefined buckets. Choosing the right type determines whether you are discovering fresh patterns or confirming what you already suspect. Conduct your sessions with a focus on observing where users struggle, then synthesize these observations into a draft site map. Prioritize the most common user patterns while addressing identified areas of confusion to build a hierarchy that truly works. By translating friction points into structural changes, you turn raw sorting data into a functional information architecture. You now have the full workflow to execute a card sort study and synthesize results into an information architecture. This process bridges the gap between user mental models and the tangible site maps that guide your design. Key Points: Audit your current content source to create a comprehensive list of items for your cards Decide if your project requires an open sort to explore new structures or a closed sort to validate existing categories Synthesize observations into a draft site map that prioritizes common user patterns while addressing identified confusion