Skip to content

Instantly share code, notes, and snippets.

@droom
Last active August 29, 2015 14:09
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save droom/6092a9928db8976a7966 to your computer and use it in GitHub Desktop.
Save droom/6092a9928db8976a7966 to your computer and use it in GitHub Desktop.
Sprint (Tips)

Design Sprint Methodology

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

THEORY

Traditional Model, Months+

Hypothosise → Build MVP → Launch → Measure → Learn → REPEAT

Problems
  1. You might start with a bad idea
  2. Spend a lot of time building that idea
  3. You're commited to launch because of the time invested
  4. Inconclusive results
  5. Your enthusiam for the project dies by the end

Sprint Model, 5-days

Ideate → Build MVP → Test → REPEAT

Sprint Toolset

Sketch InVision Logo: Illustrator BOX (synced)

Sprint Tips

  1. If you get stuck, remember what you’re trying to learn.

  2. 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.

  3. 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.

Materials

  • Time Timer
  • Bit Timer
  • Mind maps
  • Story map
  • Crazy Eights

Resources

— [VIDEO] Google I/O 2014 - The design sprint: from Google Ventures to Google

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment