Design Sprints: A Non-Google Approach

There's more than 1 way to skin a cat and there's more than 1 way to do a design sprint. This approach is based on the O'Reilly book I co-authored and takes a scientific approach to tackling a design challenge by identifying and challenging your assumptions, while also prototyping and building to validate or invalidate them.

Transcript

1. DESIGN SPRINTS: A NON-GOOGLE APPROACH JUNE 14, 2017 C. TODD LOMBARDO CHIEF DESIGN STRATEGIST, FRESH TILLED SOIL @IAMCTODD — CTODD@FRESHTILLEDSOIL.COM
2. Not this one. This one.
3. Not this one. This one.
4. EVERYONE HAS A PROCESS C. TODD LOMBARDO — @IAMCTODD
6. IDEO XPLANE CHESKIN BITOMI COOPER FROG FITCH MELVILLE IDEO ED Discovery Interpretation Ideation Experimentation Evolution STANFORD Empathize Define Ideate Prototype Test Prepare Form Harden Fire & Glaze
7. Source: gv.com; thoughtbot.com; smashngmagazine.com
8. Empathize Define Prototype Test Ideate Discovery Interpretation Experimentation Evolution Ideation Source: gv.com; thoughtbot.com; smashngmagazine.com
9. Source: IBM
10. Source: Design Council UK
11. APPLIED DESIGN-THINKING C. TODD LOMBARDO — @IAMCTODD
13. Source: google.com
14. Define Understand Build Test Ideate Understand Diverge Prototype Validate Decide 2013 Unpack Sketch Prototype Test Decide 2015 Understand Diverge Build Test Converge Empathize Define Prototype Test Ideate Map Sketch Build Test Decide 2016 Design Sprint Processes Understand Define Build Test Decide Diverge
15. Our Design Sprint Approach C. TODD LOMBARDO — @IAMCTODD
16. Our Design Sprint Approach UNDERSTAND C. TODD LOMBARDO — @IAMCTODD
17. Our Design Sprint Approach UNDERSTAND DIVERGE C. TODD LOMBARDO — @IAMCTODD
18. Our Design Sprint Approach UNDERSTAND DIVERGE CONVERGE 1º 2º 3º C. TODD LOMBARDO — @IAMCTODD
19. Our Design Sprint Approach UNDERSTAND DIVERGE CONVERGE 1º 2º 3º C. TODD LOMBARDO — @IAMCTODD
20. Our Design Sprint Approach UNDERSTAND DIVERGE CONVERGE PROTOTYPE 1º 2º 3º C. TODD LOMBARDO — @IAMCTODD
21. Our Design Sprint Approach UNDERSTAND DIVERGE CONVERGE PROTOTYPE TEST 1º 2º ✓ X 1º 2º 3º C. TODD LOMBARDO — @IAMCTODD
22. A DESIGN SPRINT IS A FLEXIBLE TIME-BOXED PROBLEM SOLVING FRAMEWORK THAT INCREASES THE CHANCES OF MAKING SOMETHING PEOPLE WANT What Is A Design Sprint?
23. LEAN STARTUP? LEAN UX? C. TODD LOMBARDO — @IAMCTODD
24. LEARN BUILD MEASURE PRODUCT DATA IDEAS
25. BUILD BUILD BUILD PRODUCT PRODUCT PRODUCT Credit: Wolf Bruening
26. LEARN BUILD MEASURE PRODUCT DATA IDEAS START HERE?
27. ANYTIME CUSTOMER VALIDATION IS NEEDED WHEN YOU DON’T HAVE DATA WHEN THERE ARE ASSUMPTIONS WHEN YOU ENTER NEW MARKETS WHEN YOU DESIGN SOMETHING NEW When Is A Design Sprint Used
29. MAKE THINGS PEOPLE WANT MAKE PEOPLE WANT THINGS > (OR NEED, OR LOVE!)
30. UNDERSTAND GET THE BACKGROUND Rules of the Design Sprint Parking Lot Hopes & Fears Assumptions KNOW THE USER Who / Do Personas User Journey Map DEFINE THE PROBLEM Problem Statement Problem Reframe WRAP-UP Daily Retrospective
31. ASSUMPTIONS BACKGROUND INSIGHTS “WHO” JOURNEY PROBLEM STATEMENT REFRAME PHASE 2
32. ASSUMPTIONS: WHAT YOU THINK YOU KNOW
33. CONNECT 9 DOTS. WITH 4 OR LESS STRAIGHT LINES. DO NOT LIFT YOUR PEN.
36. HI HI LO LO Importance Risk
37. HI HI LO LO Importance Risk
38. HI HI LO LO Importance Risk HIGH IMPORTANCE HIGH RISK HIGH IMPORTANCE LOW RISK LOW IMPORTANCE LOW RISK LOW IMPORTANCE HIGH RISK
39. HI HI LO LO Importance Risk HIGH IMPORTANCE HIGH RISK HIGH IMPORTANCE LOW RISK LOW IMPORTANCE LOW RISK LOW IMPORTANCE HIGH RISK
41. Problem Statement A problem statement is a challenge that has business value for a persona INSPIRED BY: SIRIUSDECISIONS
42. Problem Statement A problem statement is a challenge that has business value for a persona INSPIRED BY: SIRIUSDECISIONS
43. Problem Statement A problem statement is a challenge that has business value for a persona INSPIRED BY: SIRIUSDECISIONS
44. Problem Statement A problem statement is a challenge that has business value for a persona INSPIRED BY: SIRIUSDECISIONS
45. Problem Statement A problem statement is a challenge that has business value for a persona WHAT WHY WHO INSPIRED BY: SIRIUSDECISIONS
46. Example INSPIRED BY: SIRIUSDECISIONS
47. Example Human resources lacks recruiting software INSPIRED BY: SIRIUSDECISIONS
48. Example Human resources lacks recruiting software BAD INSPIRED BY: SIRIUSDECISIONS
49. Example Human resources lacks recruiting software Human resource struggles to hire top talent to maintain a competitive advantage BAD INSPIRED BY: SIRIUSDECISIONS
50. Example Human resources lacks recruiting software Human resource struggles to hire top talent to maintain a competitive advantage BAD GOOD INSPIRED BY: SIRIUSDECISIONS
51. Problem Statement Human Resources struggle to hire top talent to maintain a competitive advantage WHAT WHY WHO INSPIRED BY: SIRIUSDECISIONS
52. WHAT ARE YOU SOLVING FOR? really
53. REFRAME?
55. THERE’S NO OPPORTUNITY, NOBODY IS WEARING ANY SHOES!
56. THERE’S NO OPPORTUNITY, NOBODY IS WEARING ANY SHOES! THERE’S A HUGE OPPORTUNITY, NOBODY IS WEARING ANY SHOES!
57. Title (H1) PROBLEM SOLUTION INSPIRED BY: WOLF BRUENING
58. Title (H1) PROBLEM SOLUTION Water on the floor Mop INSPIRED BY: WOLF BRUENING
59. Title (H1) PROBLEM SOLUTION Water on the floor Mop WHY? Leaky pipe Fix pipe INSPIRED BY: WOLF BRUENING
60. Title (H1) PROBLEM SOLUTION Water on the floor Mop WHY? Leaky pipe Fix pipe WHY? Too much pressure Lower pressure INSPIRED BY: WOLF BRUENING
61. Title (H1) PROBLEM SOLUTION Water on the floor Mop WHY? Leaky pipe Fix pipe WHY? Too much pressure Lower pressure WHY? Pressure regulator Replace regulator INSPIRED BY: WOLF BRUENING
62. Title (H1) PROBLEM SOLUTION Water on the floor Mop WHY? Leaky pipe Fix pipe WHY? Too much pressure Lower pressure WHY? Pressure regulator Replace regulator WHY? Maintenance schedule More frequent inspection INSPIRED BY: WOLF BRUENING
63. THINK LIKE A DETECTIVE
64. DIVERGE GEAR UP Review Agenda and Rules Pitch Practice Understand Recap Job-Stories GENERATE SOLUTIONS Mind Map 6-Ups (aka Crazy Eights) Storyboard Silent critique Group critique WRAP-UP Daily Retrospective
65. When ___ I need__ So that___ JOB STORY SIX UP STORYBOARD
66. When ___ I need__ So that___ JOB STORY SIX UP STORYBOARD
67. When ___ I need__ So that___ JOB STORY SIX UP STORYBOARD
68. When ___ I need__ So that___ JOB STORY SIX UP STORYBOARD When ___ I need__ So that___ When ___ I need__ So that___ When ___ I need__ So that___
69. When ___ I need__ So that___ JOB STORY SIX UP STORYBOARD When ___ I need__ So that___ When ___ I need__ So that___ When ___ I need__ So that___
70. When ___ I need__ So that___ JOB STORY SIX UP STORYBOARD When ___ I need__ So that___ When ___ I need__ So that___ When ___ I need__ So that___
71. JOB STORIES
72. “JOB?”
73. WHEN ___SITUATION___, I WANT/NEED __MOTIVATION__, SO THAT / BECAUSE __OUTCOME__.
74. WHEN IT’S 3PM AND I’M SLEEPY, I NEED A PICK-ME-UP, SO THAT I CAN BE ALERT FOR MY TEAM.
75. SIX-UPS
77. MOAR IDEAS?!
78. Generating more ideas: S.C.A.M.P.E.R. S – Substitute C – Combine A – Adapt M – Modify P – Put to another use E – Eliminate R – Reverse
79. STORYBOARDS
81. DRAW FRAME 1 HEADLINE FRAME 1 OPENING DRAW FRAME 2 FRAME 2 MIDDLE FRAME 3 RESOLVE DRAW FRAME 3
82. JOB STORY A JOB STORY B
83. JOB STORY SIX-UP STORY BOARD
84. THINK LIKE AN ARTIST
85. CONVERGE GET STARTED Review Agenda and Rules Diverge Recap DECISION CRITERIA $100 Test Assumptions Table SKETCHING Sketching - I Ritual Dissent Team Sketching – II WRAP-UP Workshop Retrospective
86. Process UNDERSTAND DIVERGE CONVERGE PROTOTYPE TEST 1º 2º ✓ X 1º 2º 3º
87. ASSUMPTIONS STORYBOARDS SKETCHING
88. ASSUMPTION MATCHING
89. Storyboards Existing Assumptions New Assumptions
91. ASSUMPTION TABLE
93. Assumption
94. Test by …? Assumption
95. Test by …? Valid if…? Assumption
96. Storyboards Assumptions
97. Storyboards Assumptions Test by …? Valid if…?
99. SKETCHING & RITUAL DISSENT
100. THINK LIKE A SCIENTIST
101. PROTOTYPE PROTOTYPE Refine sketch Build it! PLAN INTERVIEWS Define Questions Define Tasks Confirm Interview WRAP-UP Daily Retrospective
102. marshmallowchallenge.com
108. PROTOTYPES ARE MINIMIM VIABLE CONCEPTS
109. THINK LIKE AN ARCHITECT
110. TEST INTERVIEWS 1 2 WRAP-UP Sprint Debrief Daily Retrospective
111. 1. PRE-ROLL QUESTIONS 2. TEST / TASKS 3. POST-ROLL QUESTIONS
112. Interview Structure
113. Interview Structure 1. Pre Roll: Establish background questions (“how do you currently…”)
114. Interview Structure 1. Pre Roll: Establish background questions (“how do you currently…”) 2. Test: Determine which tasks to test prototype (“using this ____, try to…”)
115. Interview Structure 1. Pre Roll: Establish background questions (“how do you currently…”) 2. Test: Determine which tasks to test prototype (“using this ____, try to…”) 3. Post-Roll: Wrap-up questions (“How does this compare to how you do it today…?”)
117. BE. @&#%. CURIOUS.
118. THINK LIKE AN JOURNALIST
119. RETROSPECTIVE what worked? ..was validated? ..did you learn?
121. OK, NOW WHAT?
122. X ? IT WORKED! IT DIDN’T! HMMM.. Possible Outcomes
123. } } } DESIGN SPRINT INTERVALS AGILE DEVELOPMENT Define Understand Build Test Ideate WEEK 1 Refine Build Test WEEK 2 Refine Build Test WEEK 3 Refine Build Test WEEK 4 Refine Build Test WEEK n SPRINT 5K MARATHON
124. IT’S THE MINDSET… C. TODD LOMBARDO — @IAMCTODD
125. UNDERSTAND DETECTIVE C. TODD LOMBARDO — @IAMCTODD
126. UNDERSTAND DETECTIVE DIVERGE ARTIST C. TODD LOMBARDO — @IAMCTODD
127. UNDERSTAND DETECTIVE DIVERGE ARTIST CONVERGE SCIENTIST C. TODD LOMBARDO — @IAMCTODD
128. UNDERSTAND DETECTIVE DIVERGE ARTIST CONVERGE SCIENTIST PROTOTYPE ARCHITECT C. TODD LOMBARDO — @IAMCTODD
129. UNDERSTAND DETECTIVE DIVERGE ARTIST CONVERGE SCIENTIST PROTOTYPE ARCHITECT TEST JOURNALIST C. TODD LOMBARDO — @IAMCTODD
130. DESIGNER SCIENTIST EMPATHIC MAKER FORWARD LOOKING RIGOROUS EXPERIMENTAL HYPOTHESIS DRIVEN
131. DESIGNTIST
132. SCIENTIFIC METHOD DESIGN PROCESS AGILE PHILOSOPHY design sprint
133. It’s much easier to build anything, than build the right thing. C. Todd Lombardo GUY WHO JUST QUOTED HIMSELF
135. WHAT IS RIGHT?
136. WHO IS RIGHT? WHAT IS RIGHT?
137. Life is too short to build something nobody wants. Ash Maurya AUTHOR, RUNNING LEAN, & SCALING LEAN
138. ctodd@freshtilledsoil.com #designsprint @iamctodd
139. APPENDIX
140. AGENDA HACKS…
141. Agenda: Shorter day - 10a to 4p Monday 10a to 4p UNDERSTAND Intro to Design Sprint Intro to Understand Problem Statement Existing research Facts & Assumptions Reframe Personas Challenge Maps Daily Retro Tuesday 10a to 4p DIVERGE Intro to Diverge Recap Day 1 Job Stories Diverge Cycle Mind Map SixUps Storyboard Critique Daily Retro
 Wednesday 10a to 4p CONVERGE Intro to Converge Recap Phase 2 Assumptions Table / $100 Test Identify Alternatives Team Sketch I Ritual Dissent Team Sketch II Daily Retro
 Thursday PROTOTYPE Build prototype Define Test Plan Confirm Interviews
 Friday TEST Interview #1 Interview #2 Interview #3 Interview #4 Interview #5 Friday RETRO & DEBRIEF Sprint Retro
142. Agenda: Invitee Hack Core Team Exec Participation Monday 10a to 4p UNDERSTAND Intro to Design Sprint Intro to Understand Problem Statement Existing research Facts & Assumptions Reframe Personas Challenge Maps Daily Retro Tuesday 10a to 4p DIVERGE Intro to Diverge Recap Day 1 Job Stories Diverge Cycle Mind Map SixUps Storyboard Critique Daily Retro
 Wednesday 10a to 4p CONVERGE Intro to Converge Recap Phase 2 Assumptions Table / $100 Test Identify Alternatives Team Sketch I Ritual Dissent Team Sketch II Daily Retro
 Thursday PROTOTYPE Build prototype Define Test Plan Confirm Interviews
 Friday TEST Interview #1 Interview #2 Interview #3 Interview #4 Interview #5 Friday RETRO & DEBRIEF Sprint Retro Designer/Maker/Engineer
143. Day 1 UNDERSTAND Intro to Design Sprint Intro to Understand Problem Statement Existing research Facts & Assumptions Reframe Personas Challenge Maps Daily Retro Day 2 DIVERGE & CONVERGE Intro to Diverge Recap Day 1 Job Stories Diverge Cycle Assumptions Table / $100 Test Identify Alternatives Team Sketch I Ritual Dissent Day 3 PROTOTYPE Build prototype Define Test Plan Confirm Interviews
 Day 4 TEST Interview #1 Interview #2 Interview #3 Interview #4 Interview #5 Day 4 or Day 5 RETRO & DEBRIEF Sprint Retro Agenda: Four Day Hack
144. MONDAY TUESDAY WEDNESDAY THURSDAY FRIDAY UNDERSTAND DIVERGE CONVERGE PROTOTYPE TEST Week 1 Week 2 PREP + RESEARCH DEBRIEF Agenda: Two-Week Hack
145. MONDAY TUESDAY WEDNESDAY THURSDAY FRIDAY UNDERSTAND DIVERGE CONVERGE PROTOTYPE TEST Week 1 Week 2 Week 3 Week 4 PREP + RESEARCH BUILD, BUILD, BUILD! DIGEST DEBRIEF Agenda: Four Week Hack
146. Preparation / Research IDEA BRIEF USER INTERVIEWS INTERNAL INTERVIEWS PLAN PREP MONDAY TUESDAY WEDNESDAY THURSDAY FRIDAY Design Sprint UNDERSTAND DIVERGE CONVERGE PROTOTYPE TEST Iteration 1 ASSUMPTIONS DIVERGE/CONVERGE PROTOTYPE TEST DEBRIEF Final Iteration ASSUMPTIONS FINAL PROTOTYPE TEST FINAL DEBRIEF GO / NO-GO Agenda: Four Week Hack Alternate
147. HOW TO §@%& IT UP?
148. Design Sprint ains
149. Design Sprint ◦ “We need Sashi, Jen, Joe, Frank, Aman, and Nadia, too!” —Two pizza rule ains
150. Design Sprint ◦ “We need Sashi, Jen, Joe, Frank, Aman, and Nadia, too!” —Two pizza rule ◦ “Let’s focus on this textbox.” — More ambiguous = better ains
151. Design Sprint ◦ “We need Sashi, Jen, Joe, Frank, Aman, and Nadia, too!” —Two pizza rule ◦ “Let’s focus on this textbox.” — More ambiguous = better ◦ “We’ll use our normal conference room” — Book it in advance (offsite preferable) ains
152. Design Sprint ◦ “We need Sashi, Jen, Joe, Frank, Aman, and Nadia, too!” —Two pizza rule ◦ “Let’s focus on this textbox.” — More ambiguous = better ◦ “We’ll use our normal conference room” — Book it in advance (offsite preferable) ◦ “I can only be there for half of day 2” — Clear schedules ains
153. Design Sprint ◦ “We need Sashi, Jen, Joe, Frank, Aman, and Nadia, too!” —Two pizza rule ◦ “Let’s focus on this textbox.” — More ambiguous = better ◦ “We’ll use our normal conference room” — Book it in advance (offsite preferable) ◦ “I can only be there for half of day 2” — Clear schedules ◦ “Can we do it in one day?” — No. Just….NO! ains