From the course: UX Foundations: Information Architecture

Unlock the full course today

Join today to access over 22,600 courses taught by industry experts or purchase this course individually.

Deciding what goes on the cards

Deciding what goes on the cards

From the course: UX Foundations: Information Architecture

Start my 1-month free trial

Deciding what goes on the cards

There isn't much space on each card. And we don't want our card sort participants to have to read too much text. We also don't want the card information to lead people to a certain answer. Take the list of items you've created; and make sure that every item is phrased either in terms of the content, or in terms of the tasks that people can perform. But not both. That sounds hard. But as an example, if you choose to go the tasks route, you can convert content into tasks quite easily. For instance, content on caring for orchids, can become a task to find out how to care for an orchid. It's harder to turn tasks into content, which is why I tend to write my card sort card as tasks. This also has an advantage later when we look at reverse sorting. because the reverse sort activity uses these same tasks as its input. It's important to phrase the tasks in users' terms. What I mean by that is that tasks should be realistic and believable. If we were writing tasks for a card sort on a…

Contents