Google I/O 2014 - The design sprint: from Google Ventures to Google[x]
HTML-код
- Опубликовано: 2 июн 2024
- Speaker(s):
Daniel Burka, Jake Knapp, Nadya Direkova
Description:
The design sprint is a process for prototyping and testing any product in 5 days. Using real-world examples, we'll show how to move faster and increase the overall effectiveness (and happiness!) of your whole team. And we'll offer techniques for teams of any size, from two-person startup to giant enterprise.
Watch all Google I/O 2014 videos at: g.co/io14videos 
Наука
Its 2022 and still is a great talk.
Interesting that at dollar value per day both Daniel and Jake's wife paid almost the same amount. Daniel paid about $2.15 per day ($179 divided by 79 days according to the chart) and Jake's wife paid $2 per day ($4 for 2 days). Good thing Daniel enjoyed his time with it :)
I would LOVE to be in a Bay Area for these sprints :-/ Have a gr8 time guys :)
Great talk, indeed inspiring.
Thank you for the help!
Great talk ;)
Daniel you sound like Mr. Gates! ;)
"Some of you are also old?" Exactly what do you call old???
What does a Hack means in this context? Minute 33:47
+Martino Liu A quick tip that doesn't take much time or effort to implement.
Isn't it risky to kill a design based on 5 data points only? You're leaving a lot up to chance... you could simply have been unlucky and fallen on 5 people who don't like it whereas the next 15 would have loved it. I love the design sprint concept but I'm concerned about the statistical significance of the data on day 5...
To put it more simply.. if you flip a coin 5 times and get tails 5 times, does it really mean you have 100% chance of always falling on tails?
This is a widely accepted model for finding usability mistakes
www.nngroup.com/articles/why-you-only-need-to-test-with-5-users/
In 5 real life tests you'll have more than enough qualitative information to decide where a design is failing
Just remember, this is not a replacement for a full design process, it is just a fast approach to gather valuable data prior to development only. Of course some tradeoffs will be made but risk is reduced.
Yep. And the usability argument is around usability, not product decisions. So if you're opening a concept store and 3 out of 5 users trip over the entrance rug, they've found a usability issue. Just cos they're not interested in the tickets for heaven you've got behind the counter, doesn't mean you should pivot away.
17x10≠250
Who else is here from T Blake!!
me lol