Design Sprints: The methods, outcomes and pitfalls.

1. A brief rundown of what a Design Sprint is.
2. When to Sprint.
3. Deciding what to do next.

Transcript

1. DESIGN SPRINTS The methods, outcomes and pitfalls. Hayden Slaughter & Tom Prior ProductTank Brighton 22 March 2018
2. OUR EXPERIENCE Facilitated and participated in Design Sprints Made some mistakes Run a lot of Sprint style design phases Learned a lot
3. JAKE KNAPP
5. A MISNOMER When is a Sprint not a Sprint?
6. A DISCLAIMER
7. WHAT WE WILL COVER 1. A brief rundown of what a Design Sprint is. 2. When to Sprint. 3. Deciding what to do next.
8. 1. The GV Design Sprint
9. How to Solve Big Problems and Test New Ideas in Just Five Days 1. The GV Sprint
10. 1. The GV Sprint
11. Jump forward in time. 1. The GV Sprint
12. Structured days, proven formula 1. The GV Sprint
13. SET THE STAGE 1. The GV Sprint
14. Assemble the team 1. The GV Sprint
15. Find a Facilitator 1. The GV Sprint
16. Nominate a Decider 1. The GV Sprint
17. Get a room 1. The GV Sprint
19. MONDAY Map 1. The GV Sprint
22. TUESDAY Sketch 1. The GV Sprint
25. WEDNESDAY Decide 1. The GV Sprint
28. THURSDAY Prototype 1. The GV Sprint
31. FRIDAY Test 1. The GV Sprint
34. 1. The GV Sprint Let’s go
35. WOAH THERE 1. The GV Sprint
36. 2. When to Sprint
37. The Product Manager says.. “We should do a design Sprint for every feature!” 2. When to Sprint
38. Don’t waste a Sprint on business as usual 2. When to Sprint
39. The CEO says.. “That’s an exciting idea, but too risky” 2. When to Sprint
40. Sprint the big stuff 2. When to Sprint
41. The Developer says.. “We can start developing this straight after the Sprint” 2. When to Sprint
42. Sprints are not reliable product design 2. When to Sprint
43. “We don’t know whether this idea is worth financial investment” The CFO says.. 2. When to Sprint
44. Use a Sprint to unlock budget 2. When to Sprint
45. “The Sprint will validate what we think about our customers” The Marketing Manager says.. 2. When to Sprint
46. Sprints don’t replace proper research work 2. When to Sprint
47. You avoided pitfalls and picked the right thing to Sprint on. 2. When to Sprint
48. You went from idea to tested prototype in just five days. 2. When to Sprint
49. You gathered valuable feedback and identified patterns. 2. When to Sprint
50. Your team developed a shared vision. 2. When to Sprint
51. 3. What next?
52. It depends! 3. What next?
53. There were some unexpected wins The outcome was… 3. What next?
54. Get them into your backlog 3. What next?
55. It bombed The outcome was… 3. What next?
56. Bin it 3. What next?
57. It went well, but there were unanswered questions The outcome was… 3. What next?
58. Sprint again 3. What next?
59. We discovered a bigger problem The outcome was… 3. What next?
60. Go deep 3. What next?
61. The idea tested well The outcome was… 3. What next?
62. Start your design process 3. What next?
63. WHAT WE SHARED 1. A brief rundown of what a Design Sprint is. 2. When to Sprint. 3. What to do after a Sprint.
64. THANKS FOR LISTENING! Hayden Slaughter www.haydenslaughter.com @haydenslaughter Tom Prior www.thomasprior.co.uk @tomprior