Tokyo-Tech 2017 EDP-A #3 Prototype and Test

1. Prototype & Test
Engineering Design Project A
2017.07.22
KADO Masanori (@kdmsnr)
Specially Appointed Lecturer
Tokyo Institute of Technology

2. #realtime-20170722

3. Design Process of This Class
☓

4. The Purpose of This Class
EDP-A is designed as a preparation / training for EDP-B/C
• The sponsor companies will expect "WOW" solutions
• "Design Thinking" (w/ plain prototype) is not enough to make that happen
• You should go into "Engineering Design" (w/ rich prototype) instead,
so we'd like you to learn what the DTF class did not cover
• Sorry for students who won't take EDP-B/C ...

5. EDP-A schedule

6. Prototype and Test to Learn
Prototype Test
Learn
Make Your Ideas Tangible
Find something new, you didn't know

7. Stages of Prototypes
Schindlholzer, Bernhard, Falk Uebernickel, and Walter Brenner. "A method for the management of service innovation projects in mature organizations." (2011).

8. P1:Critical Function Prototype 💡
• to ideate critical functional requirements
of a potential solution with paper or so
P2: Darkhorse Prototype 🐴
• to broaden the solution space
P3: FunKtional (Integrated)
Prototype 🐒
• to combine the different prototypes that
have been developed in the previous
stage
P4: Functional Prototype 🛩
• to define the scope of the final solution
that will be delivered at the end of the
project
P5: X-is-Finished Prototype ✈
• to finish one functionality or feature of
the final solution
P6: Final Prototype 🚀
• to integrate into a coherent concept, in
order to go into mass-production
Schindlholzer, Bernhard, Falk Uebernickel, and Walter Brenner. "A method for the management of service innovation projects in mature organizations." (2011).
Stages of Prototypes

9. P1:Critical Function Prototype 💡
• to ideate critical functional requirements
of a potential solution with paper or so
P2: Darkhorse Prototype 🐴
• to broaden the solution space
P3: FunKtional (Integrated)
Prototype 🐒
• to combine the different prototypes that
have been developed in the previous
stage
P4: Functional Prototype 🛩
• to define the scope of the final solution
that will be delivered at the end of the
project
P5: X-is-Finished Prototype ✈
• to finish one functionality or feature of
the final solution
P6: Final Prototype 🚀
• to integrate into a coherent concept, in
order to go into mass-production
Schindlholzer, Bernhard, Falk Uebernickel, and Walter Brenner. "A method for the management of service innovation projects in mature organizations." (2011).
Stages of Prototypes
up to here in EDP-A

10. How to test with Functional Prototype
Final Prototype Functional Prototype

11. How to test with Functional Prototype
Final Prototype Functional Prototype
User's Imagination

12. Exploit User's Imagination 💭
- Carefully choose imaginative users (Early Adapters)
- Test with plural (at least 5) users
- Use "Wizard of Oz" 💫
- Prepare various types of prototypes
• Users cannot do absolute evaluation, so let users choose better one
• [TIP] separate one prototype into two different prototypes ➡

13. Two types of Prototypes
Work-Like prototype 🤖
• with little-to-no resemblance to the intended final product
Look-Like prototype 🎨
• with little-to-no intended functionality

14. Test & Improve * 5 times, then Presentation
, - .
/ 0

15. How to Test With Users
1. Set the context.
• Put users in the situation where the prototype is appropriately used.
2. Show don’t tell about the prototype.
• Put your prototypes in the user’s hands and give just the minimum explanation.
3. Actively observe.
• Watch how they use (and misuse!) what you have given them. Don’t “correct” what user is doing.
4. Follow up with questions.
• Choose questions which can decide whether you should improve or change the prototype.
• Use "Value Proposition Statement" as reference ➡
https://dschool.stanford.edu/resources/the-bootcamp-bootleg

16. Value Proposition Statement
You should break this down to sub value propositions.
User Test should include falsifiable hypothesis

17. Decision-making is difficult, but important
😄 If the hypothesis is true ...
• You should improve the prototypes and continue tests
😩 If the hypothesis is false ...
• You should think where to fix, then change and continue tests
(function? looking? user? hypothesis? context? usage?)
• If all of the hypothesis are false, it's no problem. You should learn a lot.

18. Use "Feedback Capture Grid" to get Feedback
https://dschool.stanford.edu/resources/the-bootcamp-bootleg
It's easy to use, but ... observation is more important

19. There is no "RIGHT" user test
You should get
"convincing" testimonials

20. REFLECTION
- Take a LARGE sticky note. (or combine two 75x75 post-it notes)
- Write down your name and dept on the top
- Write about today's class and/or yourself (Japanese is OK) :
• Keep (Good thing)
• Problem (Bad thing)
• Try (Improvement)
- Post on the whiteboard.
Name and Dept
- Keep
- Problem
- Try