I think that the experts are very close to create a unique methodology to Innovate, it means a generic method that can available as a strucured knowledge. Congratulations to Stanford for this webinar.
6 years late, there are a lot of modifications integrated into design thinking and lean startup approach. Personally, I plan to integrate product architecture into the ideation and prototype or MVP phase to have a more structured approach in defining the concept and the functions and features inside it.
I think with "prototype" the key difference, as you mention, is the resolution or fidelity of the prototype. Within the design thinking realm - it's typically very low res/analog and you may build a few as talking points - just enough to help your target audience visualize the potential solution. Within MVP it typically has to pass for a real "thing" in front of that same audience.
Sarah Gallimore depending on who you talk to, there is much confusion on this subject. I like to run simulations even before the PRE proto type is built, so that I can have more testing traction with the preprototype, knowing that there are some testers (early users) that would see a low res as viable. Usually this is to see what features are a priority. Many founders want to rush and call a product a product, using a push method without any customer discovery. And the context of prototypes get lost in translation
I see a lot of wisdom in the distinction between Lean and Design Thinking but could see the matchmaker prototype (around 36:30) being a MVP test because that is your biggest assumption, that people want to be matchmakers.
I never can stress this enough. Don't expect many views for this video. Because your approach implies actual work and teams want to stay in lala land where pipe dream live
I think that the experts are very close to create a unique methodology to Innovate, it means a generic method that can available as a strucured knowledge. Congratulations to Stanford for this webinar.
6 years late, there are a lot of modifications integrated into design thinking and lean startup approach.
Personally, I plan to integrate product architecture into the ideation and prototype or MVP phase to have a more structured approach in defining the concept and the functions and features inside it.
I think with "prototype" the key difference, as you mention, is the resolution or fidelity of the prototype. Within the design thinking realm - it's typically very low res/analog and you may build a few as talking points - just enough to help your target audience visualize the potential solution. Within MVP it typically has to pass for a real "thing" in front of that same audience.
Sarah Gallimore depending on who you talk to, there is much confusion on this subject. I like to run simulations even before the PRE proto type is built, so that I can have more testing traction with the preprototype, knowing that there are some testers (early users) that would see a low res as viable. Usually this is to see what features are a priority. Many founders want to rush and call a product a product, using a push method without any customer discovery. And the context of prototypes get lost in translation
I see a lot of wisdom in the distinction between Lean and Design Thinking but could see the matchmaker prototype (around 36:30) being a MVP test because that is your biggest assumption, that people want to be matchmakers.
Looking forward to see more!!Nice! Thank you!
I never can stress this enough. Don't expect many views for this video. Because your approach implies actual work and teams want to stay in lala land where pipe dream live
16:32