Latest / 5 Minute UX / Card Sorting: Open, Closed, and Hybrid Methods
Transcript
- 0:08This lesson is Card Sorting: Open, Closed, and Hybrid
- 0:11Methods. Let's get started.
- 0:21What if you've spent weeks building a website, only to
- 0:23realize users can't find anything because you organized
- 0:26it by your departments instead of their needs? Without card
- 0:28sorting, information architectures often default to
- 0:31internal departmental structures like Human Resources or Legal,
- 0:33rather than how people actually seek information. This mismatch
- 0:36creates immediate frustration and drives users away before
- 0:39they even engage with your content. Card sorting reveals
- 0:41common patterns in how users mentally categorize information
- 0:44to prevent exactly this kind of confusion. By watching
- 0:46participants sort cards into groups, you uncover the natural
- 0:49mental models that drive their behavior. This technique is
- 0:51essential for content-heavy platforms like intranets and
- 0:54websites to move from subjective guesses to data-driven
- 0:56decisions. Imagine giving users topics or content pieces on
- 0:59cards and asking them to create their own categories without any
- 1:02bias. This process exposes where your internal assumptions clash
- 1:05with user expectations, allowing you to fix the structure before
- 1:08development begins. You will learn to identify the three card
- 1:10sorting approaches: open, closed, and hybrid, so you can
- 1:13choose the right one for your specific challenge.
- 1:21We dive straight into the three specific approaches you'll use
- 1:24to organize content. The first method is the open sort, where
- 1:26participants create their own categories and labels from
- 1:29scratch. This approach is ideal for generating new structures
- 1:32without the bias of an existing organizational model. Next, you
- 1:34have the closed sort, where participants place items into
- 1:37predefined categories provided by your team. This method is
- 1:39best for validating existing structures or testing the
- 1:42clarity of current navigation labels. You use this when you
- 1:44already have a proposed hierarchy and need to confirm it
- 1:47aligns with user mental models. The third option is the hybrid
- 1:50sort, which combines the previous two approaches into a
- 1:52single session. Here, participants can utilize
- 1:54predefined categories but are also permitted to create new
- 1:57groups if the provided options do not fit. This balances the
- 1:59need to test specific structural assumptions with the flexibility
- 2:02to uncover unexpected user mental models. Choosing the
- 2:05right method depends entirely on whether you need to generate a
- 2:07new structure or validate a proposed one. If your goal is to
- 2:10create a site map from scratch, the open sort reveals how users
- 2:13naturally conceptualize content. If you are refining a current
- 2:15system, the closed sort pinpoints areas of confusion
- 2:18before you commit to development. You should also
- 2:20apply the three to four week timeline framework to plan a
- 2:22card sorting study effectively. This schedule breaks down into
- 2:25one week for planning and preparation, one week to conduct
- 2:28the research, and one to two weeks to analyze and report
- 2:30results. Following this timeline ensures your insights are
- 2:33integrated into the design process before significant
- 2:35resources are wasted.
- 2:42Let's say you have a finished website and want to know if
- 2:45users can find a specific article. You would run usability
- 2:47testing to see how they interact with that existing navigation
- 2:50system. However, if your project requires creating a structure
- 2:53from scratch, usability testing won't work because there is no
- 2:55finished product to evaluate yet. This is where card sorting
- 2:58becomes your primary tool, because it defines what the
- 3:00navigation should be rather than testing how users move through
- 3:03it. You use this method to generate a new structure with an
- 3:05open sort, or to validate a proposed one with a closed sort.
- 3:08It prevents you from testing a navigation system that is
- 3:10fundamentally misaligned with how users actually think about
- 3:13your content. So when you are determining which topics to
- 3:15include and how to structure them, you apply the three-to-
- 3:17four week timeline to plan your study. This approach ensures
- 3:20your final site map reflects common user behavior instead of
- 3:23just internal assumptions. By choosing the right method now,
- 3:25you avoid the costly mistake of building a flawed hierarchy
- 3:28before development begins.
- 3:35In your next project, begin by identifying whether your work
- 3:37requires generating a new structure, validating a proposed
- 3:40one, or exploring a mix of both. This decision dictates whether
- 3:42you apply an open sort, a closed sort, or a hybrid sort to
- 3:45address your specific structural needs. You must align the method
- 3:48with your goal, because using the wrong approach will yield
- 3:50data that cannot guide your design decisions. If your
- 3:52topics are undefined, you should use an open sort to generate new
- 3:55site maps and hierarchies from scratch. Participants will
- 3:57create their own groups and labels, which reveals how users
- 4:00naturally conceptualize your content without the bias of
- 4:02existing models. This approach is essential when you need to
- 4:05move beyond internal organizational silos to discover
- 4:07genuine user mental models. When you have a proposed
- 4:09structure ready, apply a closed sort to validate that it aligns
- 4:12with user expectations before development begins. Participants
- 4:15place content items into your predefined categories, which
- 4:17tests the clarity of your navigation labels and your
- 4:19assumed hierarchy. This step prevents you from committing
- 4:22significant development resources to a structure that
- 4:24users might find confusing or illogical. To make this
- 4:26actionable tomorrow, schedule a three to four week window to
- 4:29plan, conduct, and analyze your entire study. You will need one
- 4:31week for planning and preparation, one week to conduct
- 4:34the research, and one to two weeks to analyze and report your
- 4:36results. This timeline ensures you have a clear set of content
- 4:39items ready and that insights are integrated before coding
- 4:41starts. Use the resulting patterns to draft your final
- 4:43site map, ensuring the design reflects commonalities in user
- 4:46behavior rather than internal assumptions. By applying this
- 4:48three to four week timeline framework, you transform a vague
- 4:51research idea into a disciplined study that delivers real value.
- 4:54Your final hierarchy will be grounded in data, not just the
- 4:56team's internal guesses about how information should be
- 4:58organized.
- 5:05Pause and think about your last project where you organized
- 5:08complex content into a hierarchy. Did you generate a
- 5:10brand new structure, validate a proposed one, or explore a mix
- 5:13of both? You must begin by identifying whether your project
- 5:16requires an open sort, a closed sort, or a hybrid sort to match
- 5:19your specific structural needs. Consider the primary risk of
- 5:22skipping this research entirely, which is organizing information
- 5:25by internal silos rather than user mental models. When you
- 5:28apply the three to four week timeline framework, you ensure
- 5:31your final design reflects commonalities in user behavior
- 5:33instead of internal assumptions. This schedule gives you one week
- 5:36for planning, one week to conduct the research, and one to
- 5:39two weeks to analyze and report results. Recall the specific
- 5:42scenario where a hybrid sort becomes necessary, such as when
- 5:45you need to test assumptions while allowing flexibility for
- 5:48new groups. By selecting the appropriate method now, you
- 5:51prevent the costly mistake of building a navigation system
- 5:53that users cannot intuitively understand. You have now
- 5:56connected the right sorting approach to your project goals,
- 5:59completing your journey from confusion to clarity.
- 6:04Welcome to The Take. I'm joined by a fellow practitioner and
- 6:08together we're going to dig into Card Sorting: Open, Closed, and
- 6:11Hybrid Methods — what it means in practice and what's worth
- 6:14remembering.
- 6:16[HOST] The distinction between generating a new structure
- 6:19versus validating an existing one really hits home when you
- 6:22consider the cost of being wrong. [LEARNER] Absolutely.
- 6:25I've seen teams burn months building a navigation menu based
- 6:28on internal silos only to realize users can't find the
- 6:30content. [HOST] That's exactly why the closed sort is so
- 6:33critical before you commit to development, yet it feels risky
- 6:36to test a hierarchy you haven't fully proven yet. [LEARNER] It's
- 6:40risky, but the hybrid approach offers a safety net by letting
- 6:43participants create new groups if your predefined categories
- 6:46fail them. [HOST] I wonder how often we actually use that
- 6:49flexibility or if we just force users into our boxes because
- 6:52we're afraid of the unknown. [LEARNER] We do force them
- 6:54sometimes, but AI tools are starting to change how we
- 6:57analyze those outliers in the data during the hybrid sessions.
- 7:00[HOST] How so? Do they help identify the mental models that
- 7:03don't fit your proposed structure? [LEARNER] Yes, they
- 7:06can instantly cluster the "other" items and suggest labels
- 7:09based on semantic similarity, saving us days of manual
- 7:12analysis. [HOST] That speeds up the reporting phase, but it
- 7:15doesn't replace the need to understand why those items
- 7:17didn't fit in the first place. [LEARNER] True, the AI gives you
- 7:21the pattern, but you still have to decide if that pattern is a
- 7:24user insight or just a data anomaly. [HOST] So the real
- 7:26value isn't in the speed of the analysis, but in having the time
- 7:30to challenge our assumptions before coding starts. [LEARNER]
- 7:33Exactly, and that three-to-four week timeline forces that
- 7:36reflection instead of letting us rush into a flawed design.
- 7:39[HOST] It seems the method we choose defines not just the data
- 7:42we get, but the confidence we've in the final site map.