The Non-Google Design Sprint
•
38 likes•3,636 views
You'll learn: All the activities required for realistic design sprints How to modify your agenda and activities for different timelines How to incorporate quantitative and qualitative data into design sprints
Recommended
More Related Content
What's hot
What's hot (20)
Similar to The Non-Google Design Sprint
Similar to The Non-Google Design Sprint (20)
More from uxpin
More from uxpin (20)
Recently uploaded
Recently uploaded (20)
The Non-Google Design Sprint
- 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. EVERYONE HAS A PROCESS C. TODD LOMBARDO — @IAMCTODD
- 4. 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
- 5. Empathize Define Prototype TestIdeate Discovery Interpretation Experimentation EvolutionIdeation Source: gv.com; thoughtbot.com; smashngmagazine.com
- 6. Source: IBM
- 7. Source: Design Council UK
- 8. APPLIED DESIGN-THINKING C. TODD LOMBARDO — @IAMCTODD
- 11. Define Understand Build TestIdeate Understand Diverge Prototype ValidateDecide 2013 Unpack Sketch Prototype TestDecide 2015 Understand Diverge Build TestConverge Empathize Define Prototype TestIdeate Map Sketch Build TestDecide 2016 Design Sprint Processes Understand Define Build TestDecideDiverge
- 12. Our Design Sprint Approach UNDERSTAND C. TODD LOMBARDO — @IAMCTODD
- 13. Our Design Sprint Approach UNDERSTAND DIVERGE C. TODD LOMBARDO — @IAMCTODD
- 14. Our Design Sprint Approach UNDERSTAND DIVERGE CONVERGE 1º 2º 3º C. TODD LOMBARDO — @IAMCTODD
- 15. Our Design Sprint Approach UNDERSTAND DIVERGE CONVERGE 1º 2º 3º C. TODD LOMBARDO — @IAMCTODD
- 16. Our Design Sprint Approach UNDERSTAND DIVERGE CONVERGE PROTOTYPE 1º 2º 3º C. TODD LOMBARDO — @IAMCTODD
- 17. Our Design Sprint Approach UNDERSTAND DIVERGE CONVERGE PROTOTYPE TEST 1º 2º ✓ X 1º 2º 3º C. TODD LOMBARDO — @IAMCTODD
- 18. 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?
- 19. LEAN STARTUP? LEAN UX? C. TODD LOMBARDO — @IAMCTODD
- 23. 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
- 25. 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
- 27. ASSUMPTIONS: WHAT YOU THINK YOU KNOW
- 28. CONNECT 9 DOTS. WITH 4 OR LESS STRAIGHT LINES. DO NOT LIFT YOUR PEN.
- 33. HI HI LO LO Importance Risk HIGH IMPORTANCE HIGH RISK HIGH IMPORTANCE LOW RISK LOW IMPORTANCE LOW RISK LOW IMPORTANCE HIGH RISK
- 34. HI HI LO LO Importance Risk HIGH IMPORTANCE HIGH RISK HIGH IMPORTANCE LOW RISK LOW IMPORTANCE LOW RISK LOW IMPORTANCE HIGH RISK
- 36. Problem Statement A problem statement is a challenge that has business value for a persona INSPIRED BY: JEFF LASH
- 37. Problem Statement A problem statement is a challenge that has business value for a persona INSPIRED BY: JEFF LASH
- 38. Problem Statement A problem statement is a challenge that has business value for a persona INSPIRED BY: JEFF LASH
- 39. Problem Statement A problem statement is a challenge that has business value for a persona INSPIRED BY: JEFF LASH
- 40. Problem Statement A problem statement is a challenge that has business value for a persona WHATWHY WHO INSPIRED BY: JEFF LASH
- 41. Example Human resources lacks recruiting software Human resource struggles to hire top talent to maintain a competitive advantageBAD GOOD INSPIRED BY: JEFF LASH
- 42. Problem Statement Human Resources struggle to hire top talent to maintain a competitive advantage WHAT WHYWHO INSPIRED BY: JEFF LASH
- 43. WHAT ARE YOU SOLVING FOR? really
- 44. REFRAME?
- 45. THERE’S NO OPPORTUNITY, NOBODY IS WEARING ANY SHOES!
- 46. THERE’S NO OPPORTUNITY, NOBODY IS WEARING ANY SHOES! THERE’S A HUGE OPPORTUNITY, NOBODY IS WEARING ANY SHOES!
- 47. Title (H1) PROBLEM SOLUTION INSPIRED BY: WOLF BRUENING
- 48. Title (H1) PROBLEM SOLUTION Water on the floor Mop INSPIRED BY: WOLF BRUENING
- 49. Title (H1) PROBLEM SOLUTION Water on the floor Mop WHY? Leaky pipe Fix pipe INSPIRED BY: WOLF BRUENING
- 50. Title (H1) PROBLEM SOLUTION Water on the floor Mop WHY? Leaky pipe Fix pipe WHY? Too much pressure Lower pressure INSPIRED BY: WOLF BRUENING
- 51. 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
- 52. 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
- 53. THINK LIKE A DETECTIVE
- 54. 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
- 55. When ___ I need__ So that___ JOB STORY SIX UP STORYBOARD
- 56. When ___ I need__ So that___ JOB STORY SIX UP STORYBOARD
- 57. When ___ I need__ So that___ JOB STORY SIX UP STORYBOARD
- 58. 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___
- 59. 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___
- 60. 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___
- 61. JOB STORIES
- 62. “JOB?”
- 63. WHEN ___SITUATION___, I WANT/NEED __MOTIVATION__, SO THAT / BECAUSE __OUTCOME__.
- 64. WHEN IT’S 3PM AND I’M SLEEPY, I NEED A PICK-ME-UP, SO THAT I CAN BE ALERT FOR MY TEAM.
- 65. SIX-UPS
- 67. MOAR IDEAS?!
- 68. 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
- 69. STORYBOARDS
- 71. DRAW FRAME 1 HEADLINE FRAME 1 OPENING DRAW FRAME 2 FRAME 2 MIDDLE FRAME 3 RESOLVE DRAW FRAME 3
- 74. THINK LIKE AN ARTIST
- 75. 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
- 76. Process UNDERSTAND DIVERGE CONVERGE PROTOTYPE TEST 1º 2º ✓ X 1º 2º 3º
- 81. ASSUMPTION TABLE
- 82. Assumption
- 84. Test by …? Valid if…?Assumption
- 86. Storyboards Assumptions Test by …? Valid if…?
- 89. THINK LIKE A SCIENTIST
- 90. PROTOTYPE PROTOTYPE Refine sketch Build it! PLAN INTERVIEWS Define Questions Define Tasks Confirm Interview WRAP-UP Daily Retrospective
- 97. PROTOTYPES ARE MINIMIM VIABLE CONCEPTS
- 98. THINK LIKE AN ARCHITECT
- 100. 1. PRE-ROLL QUESTIONS 2. TEST / TASKS 3. POST-ROLL QUESTIONS
- 101. Interview Structure 1. Pre Roll: Establish background questions (“how do you currently…”)
- 102. Interview Structure 1. Pre Roll: Establish background questions (“how do you currently…”) 2. Test: Determine which tasks to test prototype (“using this ____, try to…”)
- 103. 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…?”)
- 105. BE. @&#%. CURIOUS.
- 106. THINK LIKE AN JOURNALIST
- 107. RETROSPECTIVE what worked? ..was validated? ..did you learn?
- 109. OK, NOW WHAT?
- 110. X ?IT WORKED! IT DIDN’T! HMMM.. Possible Outcomes
- 111. } } } 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
- 112. IT’S THE MINDSET… C. TODD LOMBARDO — @IAMCTODD
- 113. UNDERSTAND DETECTIVE C. TODD LOMBARDO — @IAMCTODD
- 114. UNDERSTAND DETECTIVE DIVERGE ARTIST C. TODD LOMBARDO — @IAMCTODD
- 116. UNDERSTAND DETECTIVE DIVERGE ARTIST CONVERGE SCIENTIST PROTOTYPE ARCHITECT C. TODD LOMBARDO — @IAMCTODD
- 117. UNDERSTAND DETECTIVE DIVERGE ARTIST CONVERGE SCIENTIST PROTOTYPE ARCHITECT TEST JOURNALIST C. TODD LOMBARDO — @IAMCTODD
- 119. DESIGNTIST
- 121. It’s much easier to build anything, than build the right thing. C. Todd Lombardo GUY WHO JUST QUOTED HIMSELF
- 122. WHAT IS RIGHT?
- 124. Life is too short to build something nobody wants. Ash Maurya AUTHOR, RUNNING LEAN, & SCALING LEAN
- 126. APPENDIX
- 127. AGENDA HACKS…
- 128. 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
- 129. 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
- 130. 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
- 131. MONDAY TUESDAY WEDNESDAY THURSDAY FRIDAY UNDERSTAND DIVERGE CONVERGE PROTOTYPE TEST Week 1 Week 2 PREP + RESEARCH DEBRIEF Agenda: Two-Week Hack
- 132. 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
- 133. 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
- 134. HOW TO §@%& IT UP?
- 135. Design Sprint ains
- 136. Design Sprint ○ “We need Sashi, Jen, Joe, Frank, Aman, and Nadia, too!” —Two pizza rule ains
- 137. 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
- 138. 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
- 139. 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
- 140. 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