Test
Testing is your chance to gather feedback, refine solutions, and continue to learn about your users. The test mode is an iterative mode in which you place low-resolution prototypes in the appropriate context of your user’s life. Build a prototype like you know you’re right, but test is if you know you’re wrong.
Let’s dig in
-
Once you determine what to prototype, the time has come to get out there and start testing. You identified what you needed to learn about your concepts, and these questions should be your kick-off point now. Remember that prototypes are meant only to convey an idea not be perfect. The aim is to get feedback from the people you’re designing for in a quick and rapid way, quickly move through a variety of iterations, and build on what you learn.
-
…you are craving a faster way to learn about the potential impact of solutions (especially projects that are mid-stream or already exploring an idea).
…you want to test your assumptions with what you believe will address user pain points.
…you are at the early stages of concept development and want to accelerate the rate of success or failure.
-
Create authentic experiences for users to test your prototypes.
Learn more about your user: Testing is another opportunity to build empathy through observation and engagement — often yielding unexpected insights.
Refine your prototype and solutions: Testing informs the next iterations of prototypes. Sometimes this means going back to the drawing board.
Test and refine your Point of View: Testing may reveal that, not only did you get the solution wrong, but you also frame the problem incorrectly.
-
