"If you don't like testing your product, most likely your consumers won't like to test it either."
-Anonymous
A visual depiction of people giving feedback on a test to improve it, giving the creator ideas.
The last step of the design thinking process is testing, which can be done throughout the various processes taking during a design thinking process, but it is most commonly done hand in hand with the prototyping stage. In the design thinking process, testing involves gathering user feedback that derives from the prototype models that have been developed, as well as gaining a deeper understanding of your users. When the testing stage of the project is done correctly, it can often feed into most stages of the design thinking process. This allows one to empathize and gain a better understanding of their users, gain insights that change the way one defines their problem statement, ability to generate new ideas in the ideation stage, and lead to an iteration of the prototype. Without the test phase, good products would cease to exist, as they wouldn’t be tested to know if they would work properly when completing their function. Testing is integral to make the best iteration of a product for consumers.
In the article “Stage 5 in the Design Thinking Process: Test” by Rikke Friis Dam and Teo Yu Siang, it delves in on the 5 guidelines that one should consider when conducting a test of a product. The guidelines of testing of a product is incredibly useful because when you test your ideas and prototypes with users, you gain a deeper understanding of your users and their feedback, which helps improve your designs. The first guideline that is listed is called “show, don’t tell: let your users experience the prototype”, which explains how it is important to not let people know you are the designer of the product they are testing, as they will be less honest with feedback into order to prevent them from hurt your feelings. It is also important to avoid over-explaining how your prototype works so that way the prototype testers can figure it out on their own. The other guidelines for testing include asking participants to talk through their experiences while testing the prototype, observing your participants, asking follow-up questions, and remembering that negative feedback is necessary to learn and improve.
In the article “User Research: What It Is and Why You Should Do It” by Ditte Hvas Mortensen, it explains why user research through testing is so essential, especially when it comes to UX design. There are many ways to test a product, each with its own benefits and drawbacks, but the concept “…that all user research has in common is that it helps place people at the center of your design process and your products. You use user research to inspire your design, to evaluate your solutions, and to measure your impact”. There are many good reasons to test a prototype through user research, such as to create designs that are truly relevant, designs that are easy and pleasurable to use, and to understand the return on investment of your design. When a test fits all of this criteria, you gain the best feedback to improve your product.
While testing is a crucial part of the design thinking process, there are many common issues that people experience during the testing process. According to the article “4 Common Pitfalls in Usability Testing and How to Avoid Them to Get More Honest Feedback”, some of these issues include people not wanting to hurt your feelings with their feedback, people assuming you’re testing them on their competence instead of the design, people focusing on competition instead of the journey, and lack of asking questions through an interview process to receive more feedback. By being aware of these common issues while doing the testing stage, you can avoid encountering these problems and receive more helpful feedback.