Page 130 - The Design Thinking Playbook
P. 130

KEY LEARNINGS



                                      Test prototype









                                                 •   Define scenarios and a clear goal before the test.
                                                 •   Involve neutral people when conducting the test; namely, people who did not build the prototype.
                                                 •   Ask simple and open questions in testing; never suggestive questions. Always ask “why” in order to find out the
                                                     underlying motivation.
                                                 •   Don’t design the test to be too long. Concentrate on what is essential.
                                                 •   Take along groups of stakeholders to the test (e.g., developers), so they can experience user feedback firsthand.
                                                 •   Let the test persons think aloud and don’t interrupt them. Don’t try to influence them by steering them in one
                                                     direction or selling the prototype as a great solution.
                                                 •   Avoid the pitfall of relating too quickly or too much about how the prototype works.
                                                 •   Document the tests, and always schedule enough time after a test to integrate the findings into a new proto-
                                                     type.
                                                 •   Use Web-based tools for simple prototypes.
                                                 •   Perform many qualitative tests with no more than five test persons in each one.

















                                                                                                                              129
   125   126   127   128   129   130   131   132   133   134   135