Card sorting is a technique where users are asked to organize information into logical groups. Card sorting is a qualitative user experience design technique where an individual tests a group of users to generate category trees and other classification systems.
Aspect
Explanation
Concept Overview
Card Sorting is a user-centered design technique used in information architecture, usability testing, and user experience (UX) design to organize and structure information on websites, applications, or physical products. It involves participants categorizing and sorting content, concepts, or items into groups based on their mental models and preferences. Card Sorting helps designers create more intuitive and user-friendly navigation systems and content hierarchies.
Types of Card Sorting
-There are two primary types of Card Sorting: 1. Open Card Sorting: Participants group items into categories they create themselves. 2. Closed Card Sorting: Participants sort items into predefined categories provided by the researcher or designer. Hybrid approaches combining open and closed sorting are also used.
Procedure
The Card Sorting process typically includes the following steps: 1. Preparation: Define the objectives, select participants, and create a set of cards representing the items to be sorted. 2. Instructions: Provide clear instructions to participants, explaining the task and goals. 3. Sorting: Participants physically or digitally arrange the cards into groups, expressing their mental models. 4. Analysis: Analyze the collected data to identify patterns, common groupings, and insights. 5. Implementation: Use the results to inform the design of information architecture or navigation menus.
Benefits
Card Sorting offers several benefits in UX and information architecture: 1. User-Centered Design: Ensures that information structures align with users’ mental models. 2. Improved Navigation: Helps create intuitive navigation systems, reducing user frustration. 3. Enhanced Usability: Improves the findability of content, leading to a better user experience. 4. Data-Driven Design: Relies on user input and preferences to inform design decisions. 5. Cost-Efficient: Identifies potential issues early in the design process, reducing the need for costly revisions later.
Challenges and Risks
Challenges in Card Sorting include recruiting appropriate participants, interpreting subjective data, and the potential for bias in the way participants categorize items. Care must be taken to avoid influencing participants’ choices during the sorting process.
Applications
Card Sorting is applied in various fields, including web design, software development, content organization, library science, and product design. It is particularly valuable in designing website menus, e-commerce product categories, and content management systems.
Tools and Techniques
Card Sorting can be conducted using physical cards, software tools, or online platforms that facilitate digital sorting. Software tools like OptimalSort and Trello are commonly used for online Card Sorting studies.
Card sorting is a straightforward process, with users asked to group individual labels written on cards according to criteria that make sense to them.
The approach clarifies how a target audience structures domain knowledge, with these insights used to create workflows, menu structures, and website navigation paths that meet user expectations.
For practitioners, there are three different card sorting techniques to choose from:
Open card sorting
Where participants sort cards into categories and label each category themselves in a way they deem most accurate.
Closed card sorting
Where participants sort cards into predetermined categories.
This approach does not reveal how users conceptualize multiple topics.
Instead, it is used to evaluate how well an existing category framework supports the content.
Hybrid card sorting
A combination of open and closed card sorting.
Conducting a card sort
A general overview of card sorting is detailed below:
Choose the topics
Write each topic on an individual index card, but avoid using topics that share common words as participants tend to group these topics together.
For best results, the study should incorporate 40-80 topics.
Organize the topics
The cards should then be shuffled and given to study participants.
Cards should be grouped into category piles, with topics the participant is unsure about left to one side.
Name the groups
Once participants are satisfied, they should be handed blank cards to name each pile if conducting open card sorting.
While this step helps reveal the user’s mental model, study organizers should not expect the labels to be perfect.
Debrief the user
Ask the participants to explain the rationale behind their groupings.
Take the time to ask probing questions.
Did any items belong to two or more categories?
What are your thoughts regarding the items put to one side? Were any of the items especially easy or difficult to sort?
Ask for more practical group sizes
An optional step if larger categories need to be broken down into smaller groups, or vice versa.
Repeat the process
The process must then be repeated with around 15-20 others to detect patterns in user mental models.
Analyze the data
Once the data has been compiled, look for commonalities in groups, category names, or themes.
Also look for items frequently paired with each other or put in the too-hard basket, so to speak.
Combine the identified patterns with any pre-existing qualitative insights to design a better user experience.
Note that the card sorting process can also be performed digitally using specialized software.
Digital card sorting is less labor-intensive since the software can easily determine commonly grouped items.
However, the same software can also be restrictive and prevent participants from creating the exact groups they desire.
Key takeaways
Card sorting is a technique where users are asked to organize information into logical groups. The straightforward process involves users grouping individual labels written on cards according to criteria that make sense to them.
There are three general types of card sorting: open, closed, and hybrid. Open card sorting allows the individual to sort cards according to personal criteria, while closed card sorting instructs the users to sort content into predetermined categories. The latter is used to evaluate how well an existing category framework supports the content.
Card sorting can be performed on paper or digitally. Using paper, the process involves choosing a topic, organizing the topics, naming the groups, debriefing the users, creating more practical group sizes (optional), repeating the process with more participants, and analyzing the data.
Key Concepts in Card Sorting:
Definition: Card sorting is a qualitative user experience design technique where users organize information or labels into logical groups. It helps understand how users conceptualize and categorize information, aiding in designing intuitive workflows, menu structures, and navigation paths.
Techniques of Card Sorting:
Open Card Sorting: Participants sort cards into categories and label each category themselves.
Closed Card Sorting: Participants sort cards into predetermined categories, evaluating the effectiveness of existing category structures.
Hybrid Card Sorting: A combination of open and closed card sorting.
Process of Card Sorting:
Choose Topics: Write individual topics on index cards, avoiding common words.
Organize Topics: Shuffle and distribute cards to participants for grouping into categories.
Name Groups: Participants label category piles (open card sorting).
Debrief User: Participants explain grouping rationale and answer probing questions.
Practical Group Sizes: Optional step to adjust category sizes based on user feedback.
Repeat and Analyze: Repeat the process with more participants, analyze groupings, category names, and patterns.
Design Improvement: Combine patterns and insights to enhance user experience.
Digital Card Sorting: The process can also be performed digitally using specialized software. Digital card sorting is less labor-intensive but may restrict users’ grouping flexibility.
Related Frameworks
Description
When to Apply
Closed Card Sorting
– A method where participants organize predefined cards into predetermined categories or groups. Closed Card Sorting is useful for evaluating existing information architectures or validating predefined category structures.
– When evaluating the effectiveness of existing information structures or validating predefined category taxonomies. – Conducting Closed Card Sorting exercises to assess how users categorize information according to predefined categories, informing decisions about information architecture and taxonomy design effectively.
Open Card Sorting
– A method where participants organize content cards into groups or categories based on their own mental models and perceptions. Open Card Sorting is useful for discovering how users naturally organize information and designing intuitive information architectures.
– When designing or evaluating information architectures without predefined categories. – Performing Open Card Sorting sessions to understand how users mentally categorize information, uncovering insights into user mental models and preferences to inform information architecture design effectively.
Reverse Card Sorting
– A method where participants categorize predefined content cards by placing them into predetermined categories or groups. Reverse Card Sorting is useful for evaluating the clarity and intuitiveness of category labels or taxonomy structures.
– When assessing the clarity and effectiveness of category labels or taxonomy structures. – Employing Reverse Card Sorting exercises to evaluate how users interpret and assign content cards to predefined categories, identifying potential mismatches or ambiguities in category labels and taxonomy structures effectively.
Hybrid Card Sorting
– A combination of Closed and Open Card Sorting methods where participants initially sort cards into predefined categories and then create their own categories for uncategorized cards. Hybrid Card Sorting combines the benefits of both approaches for evaluating and designing information architectures.
– When seeking insights into both predefined and user-generated category structures. – Utilizing Hybrid Card Sorting techniques to assess how users organize content into predefined categories and explore additional categories they create, providing comprehensive insights into information architecture design and taxonomy refinement effectively.
Tree Testing
– A usability testing method where participants navigate hierarchical information structures (trees) to find specific items or complete tasks. Tree Testing evaluates the findability and navigability of information architectures independently of visual design.
– When evaluating the effectiveness of information structures or navigation paths. – Conducting Tree Testing sessions to assess how users navigate hierarchical information structures, identifying navigation challenges and opportunities for improving information architecture and content organization effectively.
Closed-Ended Questionnaires
– Surveys or questionnaires where participants select responses from predefined options or categories. Closed-Ended Questionnaires are useful for gathering structured feedback and quantifying user preferences or opinions.
– When collecting quantitative feedback on information structures or category preferences. – Administering Closed-Ended Questionnaires to gather structured feedback on user perceptions of information structures, category labels, and navigation preferences, quantifying user preferences and informing information architecture decisions effectively.
Think-Aloud Protocol
– A research technique where participants verbalize their thoughts, observations, and actions while performing tasks or interacting with a system. Think-Aloud Protocol provides insights into users’ cognitive processes and decision-making rationale.
– When understanding user perceptions, behaviors, and decision-making processes. – Applying Think-Aloud Protocol techniques to observe and capture users’ thoughts and behaviors during card sorting activities, gaining insights into their mental models, preferences, and decision-making processes effectively.
Affinity Diagramming
– A collaborative method for organizing and synthesizing qualitative data, such as ideas, insights, or observations, into meaningful groups or categories. Affinity Diagramming facilitates consensus-building and pattern recognition in complex datasets.
– When synthesizing and analyzing qualitative data from card sorting exercises. – Employing Affinity Diagramming techniques to collaboratively organize and categorize insights, themes, or patterns derived from card sorting activities, facilitating consensus-building and prioritization of design recommendations effectively.
User Persona Development
– The process of creating fictional characters or representations based on user research and demographic data to embody user archetypes and behaviors. User Persona Development helps teams empathize with and design for target user groups.
– When creating user-centered design solutions or understanding user needs and goals. – Leveraging User Persona Development to distill insights from card sorting exercises into representative user personas, informing design decisions and prioritizing features based on user needs effectively.
Usability Testing
– A method for evaluating the usability and user experience of a product or system by observing users’ interactions and collecting feedback in real-world scenarios. Usability Testing helps identify usability issues and gather insights for iterative improvements.
– When assessing the usability and effectiveness of information architectures or navigation structures. – Conducting Usability Testing sessions to observe how users interact with information architectures, navigation menus, or content hierarchies, identifying usability issues and informing iterative design improvements effectively.
AIOps is the application of artificial intelligence to IT operations. It has become particularly useful for modern IT management in hybridized, distributed, and dynamic environments. AIOps has become a key operational component of modern digital-based organizations, built around software and algorithms.
Agile started as a lightweight development method compared to heavyweight software development, which is the core paradigm of the previous decades of software development. By 2001 the Manifesto for Agile Software Development was born as a set of principles that defined the new paradigm for software development as a continuous iteration. This would also influence the way of doing business.
Agile Program Management is a means of managing, planning, and coordinating interrelated work in such a way that value delivery is emphasized for all key stakeholders. Agile Program Management (AgilePgM) is a disciplined yet flexible agile approach to managing transformational change within an organization.
Agile project management (APM) is a strategy that breaks large projects into smaller, more manageable tasks. In the APM methodology, each project is completed in small sections – often referred to as iterations. Each iteration is completed according to its project life cycle, beginning with the initial design and progressing to testing and then quality assurance.
Agile Modeling (AM) is a methodology for modeling and documenting software-based systems. Agile Modeling is critical to the rapid and continuous delivery of software. It is a collection of values, principles, and practices that guide effective, lightweight software modeling.
Agile Business Analysis (AgileBA) is certification in the form of guidance and training for business analysts seeking to work in agile environments. To support this shift, AgileBA also helps the business analyst relate Agile projects to a wider organizational mission or strategy. To ensure that analysts have the necessary skills and expertise, AgileBA certification was developed.
Agile leadership is the embodiment of agile manifesto principles by a manager or management team. Agile leadership impacts two important levels of a business. The structural level defines the roles, responsibilities, and key performance indicators. The behavioral level describes the actions leaders exhibit to others based on agile principles.
The andon system alerts managerial, maintenance, or other staff of a production process problem. The alert itself can be activated manually with a button or pull cord, but it can also be activated automatically by production equipment. Most Andon boards utilize three colored lights similar to a traffic signal: green (no errors), yellow or amber (problem identified, or quality check needed), and red (production stopped due to unidentified issue).
Bimodal Portfolio Management (BimodalPfM) helps an organization manage both agile and traditional portfolios concurrently. Bimodal Portfolio Management – sometimes referred to as bimodal development – was coined by research and advisory company Gartner. The firm argued that many agile organizations still needed to run some aspects of their operations using traditional delivery models.
Business innovation is about creating new opportunities for an organization to reinvent its core offerings, revenue streams, and enhance the value proposition for existing or new customers, thus renewing its whole business model. Business innovation springs by understanding the structure of the market, thus adapting or anticipating those changes.
Business modelinnovation is about increasing the success of an organization with existing products and technologies by crafting a compelling value proposition able to propel a new business model to scale up customers and create a lasting competitive advantage. And it all starts by mastering the key customers.
A consumer brand company like Procter & Gamble (P&G) defines “Constructive Disruption” as: a willingness to change, adapt, and create new trends and technologies that will shape our industry for the future. According to P&G, it moves around four pillars: lean innovation, brand building, supply chain, and digitalization & data analytics.
That is a process that requires a continuous feedback loop to develop a valuable product and build a viable business model. Continuous innovation is a mindset where products and services are designed and delivered to tune them around the customers’ problem and not the technical solution of its founders.
A design sprint is a proven five-day process where critical business questions are answered through speedy design and prototyping, focusing on the end-user. A design sprint starts with a weekly challenge that should finish with a prototype, test at the end, and therefore a lesson learned to be iterated.
Tim Brown, Executive Chair of IDEO, defined design thinking as “a human-centered approach to innovation that draws from the designer’s toolkit to integrate the needs of people, the possibilities of technology, and the requirements for business success.” Therefore, desirability, feasibility, and viability are balanced to solve critical problems.
DevOps refers to a series of practices performed to perform automated software development processes. It is a conjugation of the term “development” and “operations” to emphasize how functions integrate across IT teams. DevOps strategies promote seamless building, testing, and deployment of products. It aims to bridge a gap between development and operations teams to streamline the development altogether.
Product discovery is a critical part of agile methodologies, as its aim is to ensure that products customers love are built. Product discovery involves learning through a raft of methods, including design thinking, lean start-up, and A/B testing to name a few. Dual Track Agile is an agile methodology containing two separate tracks: the “discovery” track and the “delivery” track.
eXtreme Programming was developed in the late 1990s by Ken Beck, Ron Jeffries, and Ward Cunningham. During this time, the trio was working on the Chrysler Comprehensive Compensation System (C3) to help manage the company payroll system. eXtreme Programming (XP) is a software development methodology. It is designed to improve software quality and the ability of software to adapt to changing customer needs.
Feature-Driven Development is a pragmatic software process that is client and architecture-centric. Feature-Driven Development (FDD) is an agile software development model that organizes workflow according to which features need to be developed next.
A Gemba Walk is a fundamental component of lean management. It describes the personal observation of work to learn more about it. Gemba is a Japanese word that loosely translates as “the real place”, or in business, “the place where value is created”. The Gemba Walk as a concept was created by Taiichi Ohno, the father of the Toyota Production System of lean manufacturing. Ohno wanted to encourage management executives to leave their offices and see where the real work happened. This, he hoped, would build relationships between employees with vastly different skillsets and build trust.
GIST Planning is a relatively easy and lightweight agile approach to product planning that favors autonomous working. GIST Planning is a lean and agile methodology that was created by former Google product manager Itamar Gilad. GIST Planning seeks to address this situation by creating lightweight plans that are responsive and adaptable to change. GIST Planning also improves team velocity, autonomy, and alignment by reducing the pervasive influence of management. It consists of four blocks: goals, ideas, step-projects, and tasks.
The ICE Scoring Model is an agile methodology that prioritizes features using data according to three components: impact, confidence, and ease of implementation. The ICE Scoring Model was initially created by author and growth expert Sean Ellis to help companies expand. Today, the model is broadly used to prioritize projects, features, initiatives, and rollouts. It is ideally suited for early-stage product development where there is a continuous flow of ideas and momentum must be maintained.
An innovation funnel is a tool or process ensuring only the best ideas are executed. In a metaphorical sense, the funnel screens innovative ideas for viability so that only the best products, processes, or business models are launched to the market. An innovation funnel provides a framework for the screening and testing of innovative ideas for viability.
According to how well defined is the problem and how well defined the domain, we have four main types of innovations: basic research (problem and domain or not well defined); breakthrough innovation (domain is not well defined, the problem is well defined); sustaining innovation (both problem and domain are well defined); and disruptive innovation (domain is well defined, the problem is not well defined).
The innovation loop is a methodology/framework derived from the Bell Labs, which produced innovation at scale throughout the 20th century. They learned how to leverage a hybrid innovation management model based on science, invention, engineering, and manufacturing at scale. By leveraging individual genius, creativity, and small/large groups.
The Agile methodology has been primarily thought of for software development (and other business disciplines have also adopted it). Lean thinking is a process improvement technique where teams prioritize the value streams to improve it continuously. Both methodologies look at the customer as the key driver to improvement and waste reduction. Both methodologies look at improvement as something continuous.
A startup company is a high-tech business that tries to build a scalable business model in tech-driven industries. A startup company usually follows a lean methodology, where continuous innovation, driven by built-in viral loops is the rule. Thus, driving growth and building network effects as a consequence of this strategy.
As pointed out by Eric Ries, a minimum viable product is that version of a new product which allows a team to collect the maximum amount of validated learning about customers with the least effort through a cycle of build, measure, learn; that is the foundation of the lean startup methodology.
Kanban is a lean manufacturing framework first developed by Toyota in the late 1940s. The Kanban framework is a means of visualizing work as it moves through identifying potential bottlenecks. It does that through a process called just-in-time (JIT) manufacturing to optimize engineering processes, speed up manufacturing products, and improve the go-to-market strategy.
Jidoka was first used in 1896 by Sakichi Toyoda, who invented a textile loom that would stop automatically when it encountered a defective thread. Jidoka is a Japanese term used in lean manufacturing. The term describes a scenario where machines cease operating without human intervention when a problem or defect is discovered.
The PDCA (Plan-Do-Check-Act) cycle was first proposed by American physicist and engineer Walter A. Shewhart in the 1920s. The PDCA cycle is a continuous process and product improvement method and an essential component of the lean manufacturing philosophy.
RAD was first introduced by author and consultant James Martin in 1991. Martin recognized and then took advantage of the endless malleability of software in designing development models. Rapid Application Development (RAD) is a methodology focusing on delivering rapidly through continuous feedback and frequent iterations.
Retrospective analyses are held after a project to determine what worked well and what did not. They are also conducted at the end of an iteration in Agile project management. Agile practitioners call these meetings retrospectives or retros. They are an effective way to check the pulse of a project team, reflect on the work performed to date, and reach a consensus on how to tackle the next sprint cycle. These are the five stages of a retrospective analysis for effective Agile project management: set the stage, gather the data, generate insights, decide on the next steps, and close the retrospective.
Scaled Agile Lean Development (ScALeD) helps businesses discover a balanced approach to agile transition and scaling questions. The ScALed approach helps businesses successfully respond to change. Inspired by a combination of lean and agile values, ScALed is practitioner-based and can be completed through various agile frameworks and practices.
The SMED (single minute exchange of die) method is a lean production framework to reduce waste and increase production efficiency. The SMED method is a framework for reducing the time associated with completing an equipment changeover.
The Spotify Model is an autonomous approach to scaling agile, focusing on culture communication, accountability, and quality. The Spotify model was first recognized in 2012 after Henrik Kniberg, and Anders Ivarsson released a white paper detailing how streaming company Spotify approached agility. Therefore, the Spotify model represents an evolution of agile.
As the name suggests, TDD is a test-driven technique for delivering high-quality software rapidly and sustainably. It is an iterative approach based on the idea that a failing test should be written before any code for a feature or function is written. Test-Driven Development (TDD) is an approach to software development that relies on very short development cycles.
Timeboxing is a simple yet powerful time-management technique for improving productivity. Timeboxing describes the process of proactively scheduling a block of time to spend on a task in the future. It was first described by author James Martin in a book about agile software development.
Scrum is a methodology co-created by Ken Schwaber and Jeff Sutherland for effective team collaboration on complex products. Scrum was primarily thought for software development projects to deliver new software capability every 2-4 weeks. It is a sub-group of agile also used in project management to improve startups’ productivity.
Scrumban is a project management framework that is a hybrid of two popular agile methodologies: Scrum and Kanban. Scrumban is a popular approach to helping businesses focus on the right strategic tasks while simultaneously strengthening their processes.
Scrum anti-patterns describe any attractive, easy-to-implement solution that ultimately makes a problem worse. Therefore, these are the practice not to follow to prevent issues from emerging. Some classic examples of scrum anti-patterns comprise absent product owners, pre-assigned tickets (making individuals work in isolation), and discounting retrospectives (where review meetings are not useful to really make improvements).
Scrum at Scale (Scrum@Scale) is a framework that Scrum teams use to address complex problems and deliver high-value products. Scrum at Scale was created through a joint venture between the Scrum Alliance and Scrum Inc. The joint venture was overseen by Jeff Sutherland, a co-creator of Scrum and one of the principal authors of the Agile Manifesto.
Six Sigma is a data-driven approach and methodology for eliminating errors or defects in a product, service, or process. Six Sigma was developed by Motorola as a management approach based on quality fundamentals in the early 1980s. A decade later, it was popularized by General Electric who estimated that the methodology saved them $12 billion in the first five years of operation.
Stretch objectives describe any task an agile team plans to complete without expressly committing to do so. Teams incorporate stretch objectives during a Sprint or Program Increment (PI) as part of Scaled Agile. They are used when the agile team is unsure of its capacity to attain an objective. Therefore, stretch objectives are instead outcomes that, while extremely desirable, are not the difference between the success or failure of each sprint.
The Toyota Production System (TPS) is an early form of lean manufacturing created by auto-manufacturer Toyota. Created by the Toyota Motor Corporation in the 1940s and 50s, the Toyota Production System seeks to manufacture vehicles ordered by customers most quickly and efficiently possible.
The Total Quality Management (TQM) framework is a technique based on the premise that employees continuously work on their ability to provide value to customers. Importantly, the word “total” means that all employees are involved in the process – regardless of whether they work in development, production, or fulfillment.
The waterfall model was first described by Herbert D. Benington in 1956 during a presentation about the software used in radar imaging during the Cold War. Since there were no knowledge-based, creative software development strategies at the time, the waterfall method became standard practice. The waterfall model is a linear and sequential project management framework.
Gennaro is the creator of FourWeekMBA, which reached about four million business people, comprising C-level executives, investors, analysts, product managers, and aspiring digital entrepreneurs in 2022 alone | He is also Director of Sales for a high-tech scaleup in the AI Industry | In 2012, Gennaro earned an International MBA with emphasis on Corporate Finance and Business Strategy.
