Tokyo-Tech 2017 EDP-A #2 Ideate & Prototype
•
3 likes•1,360 views
This document outlines an engineering design project class that skips the problem definition step and focuses on ideation and prototyping. It provides instructions for students to observe situations, brainstorm ideas, and create low-fidelity prototypes. Students are encouraged to think creatively and come up with unconventional ideas. They use a SIPOC model to map out the elements of their prototype concepts. The goal is to generate innovative solutions and get students building tangible prototypes early in the process through an experimental "think-while-prototyping" approach.
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Tokyo-Tech 2017 EDP-A #2 Ideate & Prototype
Similar to Tokyo-Tech 2017 EDP-A #2 Ideate & Prototype (20)
More from Masanori Kado
More from Masanori Kado (20)
Recently uploaded
Recently uploaded (20)
Tokyo-Tech 2017 EDP-A #2 Ideate & Prototype
- 1. Ideate & Prototype Engineering Design Project A 2017.07.08 KADO Masanori (@kdmsnr) Specially Appointed Lecturer Tokyo Institute of Technology
- 2. We won't define problem (at first) ☓
- 3. How to skip the "DEFINE" step? I don't know ... 👻
- 4. We're "prototyping" this class ... It's An Experiment !!
- 6. First of all, make team's "Inspiration Wall" Be creative to make it w/ 2+ panels of cardboard Decorate with team name & fancy stuff, not to be thrown away!! After that, stick your field notes on the wall 15 min. Do you have printed field notes? If not, ask for TA to print it out)
- 7. "Thoughtless Acts?" by Fulton Suri (IDEO) https://www.ideo.com/people/jane-fulton-suri
- 13. other examples
- 26. These are all about "Unintended Use" They do just for FUN / EASY / CONVENIENCE They aren't aware of "WHY" (i.e. Thoughtless Acts) [Related Keywords] Bricolage, Tinkering, User-based Innovation
- 27. Share your observations with the team Use post-it to take notes as needed 20 min.
- 28. We won't define problem (at first) ☓
- 29. Creative confidence is the notion that you have big ideas, and that you have the ability to act on them. ― David Kelley (Founder, IDEO)
- 30. 1-1. IDEATE, IDEATE, IDEATE Ideate 8+ different solutions DRAW the concept image (doodle!!) on Post-it notes Is that an idea you cannot come up with before the observations? • Bad Example: "Automatic peeler machine", "Washroom cleaning gadget", "Entry door with fancy LED" 8 min. for ideation by yourself & 8 min. for sharing with the team
- 31. Group all ideas into categories • Anyone can push up • No one else can push down (The person who pushed up can do) 10 min. 1-2. "so-so", "Like", and "WOW!!" → so-so😐 → Like😊 → WOW!!😆 → sorry
- 32. 1-3. «Quality» of Design What's the diff between "WOW!!" and "Like"? (or between "Like" and "so-so"?) Describe the differences as Keywords They're «Quality» criteria for your team 10 min.
- 33. What's a Good Idea? 👓 🌟 🗑 😜 High «Quality»Low «Quality» Highly User-Centric Poorly User-Centric
- 34. How to create "Star" ideas? Basic rule: "step to the right, then up" How to step to the right? • Exploit the «Quality» • Scale Up / Down (Extremely big or small) • Reverse / Deny / Invert
- 35. 2-1. Exploit the «Quality» 1. Ideate with Scaled Up/Down «Quality» • Think EXTREMELY big or small / fast or slow • 10 min. 2. Ideate with Reversed/Denied/Inverted «Quality» • 10 min.
- 37. 2-2. Prototyping 1. Get into groups of 2 or 3 2. Choose the most attractive idea from all of the previous exercises (including "so-so" ideas) 3. Start prototyping!! 15 min. 13:20
- 39. Artifact of the day 1. Low-Fi Prototype 2. Product Sheet • Product Name • Value Proposition • User Test Plan
- 40. 3-1. Low-Fi prototype After this lecture, you'll have a lecture of Arduino Keep some micro-controllers in mind Start prototyping!! ... I know it's difficult
- 41. Use SIPOC model
- 42. SIPOC model This is ... ah ...umm, please read wikipedia: • https://en.wikipedia.org/wiki/SIPOC [Suppliers] make some [Inputs] Arduino etc. [Process] the inputs and make [Outputs] [Customers] receive the outputs and get outcome
- 43. Example of SIPOC - TeGaKaO (EDP 2016) Supplier Input Process Output Customer Nodding Members of meeting Waving Micro Servo Remote Worker Relieved💓 ESP-WROOM-02 Detect & Notify
- 44. Example of SIPOC - KiduKalAid (EDP 2016) Supplier Input Process Output Customer Worker Exhaustion LED Colleagues Care 💓 Detect & Notify
- 45. Example of SIPOC - ChukokuBashira (EDP 2016) Supplier Input Process Output Customer Senior Farmers Neighbours Help 💓 Detect & Notify Losing balance Buzzer
- 46. SIPOC model and AEIOU Supplier Input Process Output Customer
- 47. 3-2. Make your SIPOC diagram Supplier Input Process Output Customer 15 min(come up with as many elements as possible)
- 48. 3-3. Low-Fi prototype (again) Choose the most attractive combination Start prototyping!! 15 min.
- 49. 3-4. Product Sheet Complete your product sheet 10 min.
- 50. Why skip the "DEFINE" step? Students tend to engage in wordplay • It narrows your point-of-view 👀 • It takes TOO LONG, ending up a huge waste of time ⌛ Users don't always have "Problems" • You as designer should show some solutions in first Students have to make something tangible in the end • First thing first (i.e. making something first) is reasonable • "Think-While-Prototyping" style broadens your point-of-view
- 51. Chris Dixon says: > the next big thing always starts out being dismissed as a “toy.” http://cdixon.org/2010/01/03/the-next-big-thing-will-start-out-looking-like-a-toy/
- 52. Show & Tell (2-3 teams?) 1. Low-Fi Prototype 2. Product Sheet • Product Name • Value Proposition • User Test Plan
- 53. 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