The important thing is that everyone is getting every solution, old and new, out of their head and onto paper at very low fidelity. – Jake Knapp
Make something good, fast
Hypothosise → Build MVP → Launch → Measure → Learn → REPEAT
- You might start with a bad idea
- Spend a lot of time building that idea
- You're commited to launch because of the time invested
- Inconclusive results
- Your enthusiam for the project dies by the end
Ideate → Build MVP → Test → REPEAT
Sketch InVision Logo: Illustrator BOX (synced)
-
If you get stuck, remember what you’re trying to learn.
-
It’s better to be done with something good enough than to be half-finished with a masterpiece. Remember that the goal is to learn from the user study tomorrow, not to have everything perfectly figured out and finished.
-
So one of the best things about the product design sprint is that it allows you to map out those decision points, and perhaps even to explore a few conflicting ideas in parallel instead of immediately committing to a safe choice.
- Time Timer
- Bit Timer
- Mind maps
- Story map
- Crazy Eights
— [VIDEO] Google I/O 2014 - The design sprint: from Google Ventures to Google
- The How Might We Method
- The 685 method