Card sorting

Illustration that represents a light bulb

1. Understand

On the first we stay in the problem space, challenging our understanding of the problem.This is some text inside of a div block.

Illustration that represents some working tools

2. Ideate

On the second day we gather inspiration, ideate and sketch solutions together.

Illustration that represents a futuristic mobile interface

3. Prototype

On the third day we turn the most voted sketches into a prototype and prepare to meet the users.

Illustration that represents some bubble talks

4. Test

On the fourth and final day we test the prototype with users and round off the sprint together.

How it works

Card sorting is a great way to uncover users’ mental models in regards to how they believe and expect processes should work.

Card sorting is a great way to uncover users’ mental models in regards to how they believe and expect processes should work. It is also a great way to help users and stakeholders prioritise.

Validate

Understand

25-55 minutes

Product Manager and/or Product Owner, Business Analyst, UX Designer, Developer, Quality assurer

Before

1. Recruit users early. It might take 2-3 weeks to make schedules work with your card sorters. Like in usability testing, you only need around 5-8 card sorting sessions to uncover common patterns in mental models.

2. Define the process, task, user flow or selection you wish to get input on and prepare digital notes or physical pieces of paper that clearly illustrate them.

3. Include empty notes. By including some empty notes you enable the user to ideate and include e.g. steps in a process that you haven’t considered.

‍

During

4. Give an introduction. Introduce the user to the process you wish to get input on, without getting into how it works today or how you believe it should work. Avoiding bias is important to get the most authentic input from the user. Let them know that they don’t have to use all the notes and that they can add their own.

5. Observe. Ask the user to think aloud as they put the notes in the order they feel makes the most sense.

6. Ask questions when you want to learn more about the users’ thought process and reasoning.

7. Take notes like you would during a usability test in order to go back and understand the users’ reasoning after the session.

‍

After

8. Document and compare the different results. Look for patterns that can inform your design process.

9. Prototype. Use the input you got from the users to prototype a new solution.

10. Run usability tests. Usability test the prototype with some of the users who participated in the card sorting sessions and some users who didn’t. Iterate the prototype based on their feedback.

‍

Tips

Have multiple notes with the same information on it available to the user. This can help highlight if they feel a need to recheck certain information or do something in a process more than once.

Learn more

Card Sorting: Uncover users’ mental models for better information architecture - Nielsen Norman Group (article)
Remote card sorting - Nielsen Norman Group (video)
Open vs. Closed card sorting - Nielsen Norman Group (video)
How to avoid bias in card sorting - Nielsen Norman Group (video)

This is some text inside of a div block.

What’s a Rich Text element?

The rich text element allows you to create and format headings, paragraphs, blockquotes, images, and video all in one place instead of having to add and format them individually. Just double-click and easily create content.

A rich text element can be used with static or dynamic content. For static content, just drop it into any page and begin editing. For dynamic content, add a rich text field to any collection and then connect a rich text element to that field in the settings panel. Voila!

Headings, paragraphs, blockquotes, figures, images, and figure captions can all be styled after a class is added to the rich text element using the "When inside of" nested selector system.

No items found.

Before

1. Recruit users early. It might take 2-3 weeks to make schedules work with your card sorters. Like in usability testing, you only need around 5-8 card sorting sessions to uncover common patterns in mental models.

2. Define the process, task, user flow or selection you wish to get input on and prepare digital notes or physical pieces of paper that clearly illustrate them.

3. Include empty notes. By including some empty notes you enable the user to ideate and include e.g. steps in a process that you haven’t considered.

‍

During

4. Give an introduction. Introduce the user to the process you wish to get input on, without getting into how it works today or how you believe it should work. Avoiding bias is important to get the most authentic input from the user. Let them know that they don’t have to use all the notes and that they can add their own.

5. Observe. Ask the user to think aloud as they put the notes in the order they feel makes the most sense.

6. Ask questions when you want to learn more about the users’ thought process and reasoning.

7. Take notes like you would during a usability test in order to go back and understand the users’ reasoning after the session.

‍

After

8. Document and compare the different results. Look for patterns that can inform your design process.

9. Prototype. Use the input you got from the users to prototype a new solution.

10. Run usability tests. Usability test the prototype with some of the users who participated in the card sorting sessions and some users who didn’t. Iterate the prototype based on their feedback.

‍

Tips

Have multiple notes with the same information on it available to the user. This can help highlight if they feel a need to recheck certain information or do something in a process more than once.

Learn more

Card Sorting: Uncover users’ mental models for better information architecture - Nielsen Norman Group (article)
Remote card sorting - Nielsen Norman Group (video)
Open vs. Closed card sorting - Nielsen Norman Group (video)
How to avoid bias in card sorting - Nielsen Norman Group (video)

Templates

Ultimately, the choice of design tool depends on the specific needs of the designer and the project at hand. Each tool has its strengths and weaknesses, and designers must consider factors such as cost, ease of use, and collaboration features when selecting the best tool for their needs.

Design Sprint 2.0 board

Follow this day-by-day exercise schedule for a meaningful and efficient Design Sprint.

Design Sprint Plan

Usability test script

Score card

Design Sprint 2.0 board

Usability testing tips and tricks

Video intro

Tool recommendations

Below you will find some tool recommendations, but please note that you are free to choose whatever tool you prefer. For some tools we have group wide licenses, in which case access can be requested via licenses@visma.com. Remember that you always need cost approval from your immediate manager.