by Dan Matiaudes

1. Design Sprints
Pioneered by IDEO, the d.school at Stanford and Google Ventures.

3. Design Sprints
A framework for how to solve and test big hairy design
challenges in 5 days or less.

4. What you’ll need.

5. What you’ll need.
1. A design problem.

7. 1. A design problem.
The problem needs to be quantifiable.

8. 1. A problem.
2. A multi-disciplinary team.
What you’ll need.

10. 2. A multi-disciplinary team.
The team needs to represent the business, who will
build it and who interacts with the user.

11. 1. A problem.
2. A multi-disciplinary team.
What you’ll need.
3. A war room and provisions.

14. 3. A war room and provisions.
Keep it simple - writing supplies and a whiteboard.

15. Context Diverge Converge Prototype Test
1 2 3 4 5
How does it work?

16. Context
1

17. Context1
What’s the business opportunity?

18. Context1
What does the problem “look” like?

19. Context1
What existing research do we have?

20. Context1
What analytics do we have?

21. Context1
What do WE know about this problem?

22. Context1
You’re successful coming out of this meeting if you
have a list of constraints to help guide you.

24. Diverge
2

25. Wait!
Before you can continue, schedule user interviews.

26. Diverge2
Using constraints, design quick solutions individually.

28. Diverge2
You know you’re successful after this stage if each
person has 1 solution they’re ready to present.

29. Converge
3

30. Converge3
Present your best ideas and decide which to build.

32. Converge3
When presenting, point to constraints and how you’re
solving the problem.

33. Converge3
You know you’re successful after this stage if you
have a storyboard outline for your solution.

34. Prototype
4

35. Prototype4
Build the least to learn the most.

36. Prototype4
Use tools like Power Point, Keynote, even sketches.

38. Prototype4
At the end of this stage, you know you’re successful
if you have a working prototype and a test script.

39. Prototype4
Your test script should use non leading questions to
elicit responses from users that relate to the problem.

40. Test
5

41. Test5
1-1 user interviews.

43. Test5
Listen to learn.

44. Test5
Take notes as a team or record your sessions.

45. Test5
Not every prototype will be a resounding success.

47. Test5
Learn without building.

48. Rinse & Repeat
Iterate.

49. The end.
Hit me up on Twitter or LinkedIn.
https://twitter.com/dmatiaudes
https://www.linkedin.com/in/dmatiaudes

50. Resources:
http://www.gv.com/sprint/
https://developers.google.com/design-sprint/downloads/DesignSprintMethods.pdf
http://www.fastcodesign.com/1672889/from-google-ventures-the-6-ingredients-you-need-to-run-a-design-sprint
http://www.fastcodesign.com/1672905/the-first-step-in-a-design-challenge-build-team-understanding
http://bokardo.com/archives/1-hour-of-research-saves-10-hours-of-development-time/