HCD Guide Series

Design operations guide

How to design solutions based on discovery research
Web designer and illustrator at work on a computer

Testing your designs

How to test and evaluate the designs you have prototyped

Reading time: 5 minutes

Now that you’ve created three different versions of your design expression to test with participants, it’s time to test those designs. It’s absolutely normal to feel like your designs will not be well received, or that you’ve missed the mark on this version; you probably have! This first version is just the starting point for your design. You may wish to reread the iteration and feedback sections in the design concept guide to ground yourself in this work.

Construct your test

Treat design phase testing as a small version of the HCD interviews from the discovery phase. As you move through testing rounds and learn more about what participants want and need from your design, your testing questions will narrow.

Ask open ended questions; don’t fill in silence for the participant; get them to vocalize their experience with the design to let you know how they perceive it. Review these interview techniques if you need a refresher on how to ask open-ended questions.

Note the qualities of the participants’ interactions with the design. Do they pause and have to think for a long time when they’re trying to understand a theme? Do they have to search around for a button in your interface design, or ask questions about the instructions you wrote? Record all of these interactions in your testing notes: they are called points of failure in a design, and you want to find them!

Testing frameworks

Prepare for testing by planning out what part of the design you’re testing, how you will introduce the test, and the questions or prompts you will provide. An outline for testing from each of the “making” activities is provided in this section.

We also provide a framework for planning and recording the results of your tests. If you start planning out your test and realize that you haven’t quite broken down your design into the simplest component parts yet, don’t worry. Revisit your design analysis, break it down further, and then replan your test.

Test: Cardsorting

Who: Test with people who will most likely use your product, service, or system if it is eventually built. They can be people you’ve spoken to during the discovery phase, but they don’t have to be.

Refer to this guidance on recruiting testers if needed.

Scheduling: Your card sort should take 30 to 45 minutes, depending on the complexity of the information.

How: Lay your card sort out on a table. If there was an information hierarchy that emerged from your discovery research, organize the card sort according to that hierarchy. If you are doing this test digitally, ensure you’re using a collaborative interface that allows people to freely and easily move the cards around.

Depending on how prescriptive you need to be, follow either an open-ended or guided approach:

In open-ended card sorting, you let the users organize the cards however they see fit. You do not provide structure, guidance, or directions.

In guided card sorting, you provide a small amount of guidance and instruction to the user, and you introduce a structure. Examples include:

  • Importance Spectrum: Invite participants to organize topics along a spectrum, such as “critical to somewhat critical to unnecessary” or “immediate to somewhat immediate to not immediate”.
  • Categorization: Invite participants to organize topics by group (likeness) and then organize the groups in relationship to each other.
  • Sequence: Invite participants to organize topics by sequence as in, “This goes first, then this, and then this…”

Whichever type of card sort you choose, ask participants to organize the cards the way they think best, and to think out loud as they organize. Take notes of what they say. If they fall silent, prompt them by asking questions like “What makes you move that card?” or “Why does this card make more sense here?”

Test: Storyboards

Share your story with those who’ll likely enact, administer, and/or use your concept. They can be people with whom you’ve spoken during the discovery phase, but they don’t have to be.

Refer to this guidance on recruiting testers if needed.

Scheduling: Allot 30 minutes to share your story and answer questions about it.

How: Generate a list of substantive questions to guide the conversation, such as:

  1. Do you recognize yourself in this story?
  2. What does this story get right? Where does it ring true?
  3. Where does it not ring true, and why?
  4. What critical elements does this story capture? Overlook?
  5. What questions do you have after reading this story?
  6. What questions does this story answer for you, if any?

Consider this interview similar to a “mini” discovery interview. Review these interview techniques if you need a refresher on how to structure a discovery interview. Take careful notes as you talk with participants about your design concept story. These notes will help you decide where and when to revise your concept.

Test: Storywriting

Share your story with those who’ll likely enact, administer, and/or use your concept. They can be people with whom you’ve spoken during the discovery phase, but they don’t have to be.

Refer to this guidance on recruiting testers for guidance on recruiting people who can help test the viability of your design concept.