Diese Präsentation wurde erfolgreich gemeldet.
Wir verwenden Ihre LinkedIn Profilangaben und Informationen zu Ihren Aktivitäten, um Anzeigen zu personalisieren und Ihnen relevantere Inhalte anzuzeigen. Sie können Ihre Anzeigeneinstellungen jederzeit ändern.

The Non-Google Design Sprint

2.781 Aufrufe

Veröffentlicht am

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

Veröffentlicht in: Design
  • Hey guys! Who wants to chat with me? More photos with me here 👉 http://www.bit.ly/katekoxx
       Antworten 
    Sind Sie sicher, dass Sie …  Ja  Nein
    Ihre Nachricht erscheint hier

The Non-Google Design Sprint

  1. 1. DESIGN SPRINTS: A NON-GOOGLE APPROACH JUNE 14, 2017 C. TODD LOMBARDO CHIEF DESIGN STRATEGIST, FRESH TILLED SOIL @IAMCTODD — CTODD@FRESHTILLEDSOIL.COM
  2. 2. Not this one. This one.
  3. 3. EVERYONE HAS A PROCESS C. TODD LOMBARDO — @IAMCTODD
  4. 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. 5. Empathize Define Prototype TestIdeate Discovery Interpretation Experimentation EvolutionIdeation Source: gv.com; thoughtbot.com; smashngmagazine.com
  6. 6. Source: IBM
  7. 7. Source: Design Council UK
  8. 8. APPLIED DESIGN-THINKING C. TODD LOMBARDO — @IAMCTODD
  9. 9. Source: google.com
  10. 10. 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
  11. 11. Our Design Sprint Approach UNDERSTAND C. TODD LOMBARDO — @IAMCTODD
  12. 12. Our Design Sprint Approach UNDERSTAND DIVERGE C. TODD LOMBARDO — @IAMCTODD
  13. 13. Our Design Sprint Approach UNDERSTAND DIVERGE CONVERGE 1º 2º 3º C. TODD LOMBARDO — @IAMCTODD
  14. 14. Our Design Sprint Approach UNDERSTAND DIVERGE CONVERGE 1º 2º 3º C. TODD LOMBARDO — @IAMCTODD
  15. 15. Our Design Sprint Approach UNDERSTAND DIVERGE CONVERGE PROTOTYPE 1º 2º 3º C. TODD LOMBARDO — @IAMCTODD
  16. 16. Our Design Sprint Approach UNDERSTAND DIVERGE CONVERGE PROTOTYPE TEST 1º 2º ✓ X 1º 2º 3º C. TODD LOMBARDO — @IAMCTODD
  17. 17. 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?
  18. 18. LEAN STARTUP? LEAN UX? C. TODD LOMBARDO — @IAMCTODD
  19. 19. LEARN BUILD MEASURE PRODUCT DATA IDEAS
  20. 20. BUILD BUILD BUILD PRODUCT PRODUCT PRODUCT Credit: Wolf Bruening
  21. 21. LEARN BUILD MEASURE PRODUCT DATA IDEAS START HERE?
  22. 22. 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
  23. 23. MAKE THINGS PEOPLE WANT MAKE PEOPLE WANT THINGS > (OR NEED, OR LOVE!)
  24. 24. 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
  25. 25. ASSUMPTIONS BACKGROUND INSIGHTS “WHO” JOURNEY PROBLEM STATEMENT REFRAME PHASE 2
  26. 26. ASSUMPTIONS: WHAT YOU THINK YOU KNOW
  27. 27. CONNECT 9 DOTS. WITH 4 OR LESS STRAIGHT LINES. DO NOT LIFT YOUR PEN.
  28. 28. HI HI LO LO Importance Risk
  29. 29. HI HI LO LO Importance Risk
  30. 30. HI HI LO LO Importance Risk HIGH IMPORTANCE HIGH RISK HIGH IMPORTANCE LOW RISK LOW IMPORTANCE LOW RISK LOW IMPORTANCE HIGH RISK
  31. 31. HI HI LO LO Importance Risk HIGH IMPORTANCE HIGH RISK HIGH IMPORTANCE LOW RISK LOW IMPORTANCE LOW RISK LOW IMPORTANCE HIGH RISK
  32. 32. Problem Statement A problem statement is a challenge that has business value for a persona INSPIRED BY: JEFF LASH
  33. 33. Problem Statement A problem statement is a challenge that has business value for a persona INSPIRED BY: JEFF LASH
  34. 34. Problem Statement A problem statement is a challenge that has business value for a persona INSPIRED BY: JEFF LASH
  35. 35. Problem Statement A problem statement is a challenge that has business value for a persona INSPIRED BY: JEFF LASH
  36. 36. Problem Statement A problem statement is a challenge that has business value for a persona WHATWHY WHO INSPIRED BY: JEFF LASH
  37. 37. Example Human resources lacks recruiting software Human resource struggles to hire top talent to maintain a competitive advantageBAD GOOD INSPIRED BY: JEFF LASH
  38. 38. Problem Statement Human Resources struggle to hire top talent to maintain a competitive advantage WHAT WHYWHO INSPIRED BY: JEFF LASH
  39. 39. WHAT ARE YOU SOLVING FOR? really
  40. 40. REFRAME?
  41. 41. THERE’S NO OPPORTUNITY, NOBODY IS WEARING ANY SHOES!
  42. 42. THERE’S NO OPPORTUNITY, NOBODY IS WEARING ANY SHOES! THERE’S A HUGE OPPORTUNITY, NOBODY IS WEARING ANY SHOES!
  43. 43. Title (H1) PROBLEM SOLUTION INSPIRED BY: WOLF BRUENING
  44. 44. Title (H1) PROBLEM SOLUTION Water on the floor Mop INSPIRED BY: WOLF BRUENING
  45. 45. Title (H1) PROBLEM SOLUTION Water on the floor Mop WHY? Leaky pipe Fix pipe INSPIRED BY: WOLF BRUENING
  46. 46. Title (H1) PROBLEM SOLUTION Water on the floor Mop WHY? Leaky pipe Fix pipe WHY? Too much pressure Lower pressure INSPIRED BY: WOLF BRUENING
  47. 47. 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
  48. 48. 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
  49. 49. THINK LIKE A DETECTIVE
  50. 50. 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
  51. 51. When ___ I need__ So that___ JOB STORY SIX UP STORYBOARD
  52. 52. When ___ I need__ So that___ JOB STORY SIX UP STORYBOARD
  53. 53. When ___ I need__ So that___ JOB STORY SIX UP STORYBOARD
  54. 54. 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___
  55. 55. 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___
  56. 56. 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___
  57. 57. JOB STORIES
  58. 58. “JOB?”
  59. 59. WHEN ___SITUATION___, I WANT/NEED __MOTIVATION__, SO THAT / BECAUSE __OUTCOME__.
  60. 60. WHEN IT’S 3PM AND I’M SLEEPY, I NEED A PICK-ME-UP, SO THAT I CAN BE ALERT FOR MY TEAM.
  61. 61. SIX-UPS
  62. 62. MOAR IDEAS?!
  63. 63. 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
  64. 64. STORYBOARDS
  65. 65. DRAW FRAME 1 HEADLINE FRAME 1 OPENING DRAW FRAME 2 FRAME 2 MIDDLE FRAME 3 RESOLVE DRAW FRAME 3
  66. 66. JOB STORY A JOB STORY B
  67. 67. JOB STORY SIX-UP STORY BOARD
  68. 68. THINK LIKE AN ARTIST
  69. 69. 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
  70. 70. Process UNDERSTAND DIVERGE CONVERGE PROTOTYPE TEST 1º 2º ✓ X 1º 2º 3º
  71. 71. ASSUMPTIONS STORYBOARDS SKETCHING
  72. 72. ASSUMPTION MATCHING
  73. 73. Storyboards Existing Assumptions New Assumptions
  74. 74. ASSUMPTION TABLE
  75. 75. Assumption
  76. 76. Test by …?Assumption
  77. 77. Test by …? Valid if…?Assumption
  78. 78. Storyboards Assumptions
  79. 79. Storyboards Assumptions Test by …? Valid if…?
  80. 80. SKETCHING & RITUAL DISSENT
  81. 81. THINK LIKE A SCIENTIST
  82. 82. PROTOTYPE PROTOTYPE Refine sketch Build it! PLAN INTERVIEWS Define Questions Define Tasks Confirm Interview WRAP-UP Daily Retrospective
  83. 83. marshmallowchallenge.com
  84. 84. PROTOTYPES ARE MINIMIM VIABLE CONCEPTS
  85. 85. THINK LIKE AN ARCHITECT
  86. 86. TEST INTERVIEWS 1 2 WRAP-UP Sprint Debrief Daily Retrospective
  87. 87. 1. PRE-ROLL QUESTIONS 2. TEST / TASKS 3. POST-ROLL QUESTIONS
  88. 88. Interview Structure 1. Pre Roll: Establish background questions (“how do you currently…”)
  89. 89. Interview Structure 1. Pre Roll: Establish background questions (“how do you currently…”) 2. Test: Determine which tasks to test prototype (“using this ____, try to…”)
  90. 90. 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…?”)
  91. 91. BE. @&#%. CURIOUS.
  92. 92. THINK LIKE AN JOURNALIST
  93. 93. RETROSPECTIVE what worked? ..was validated? ..did you learn?
  94. 94. OK, NOW WHAT?
  95. 95. X ?IT WORKED! IT DIDN’T! HMMM.. Possible Outcomes
  96. 96. } } } 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
  97. 97. IT’S THE MINDSET… C. TODD LOMBARDO — @IAMCTODD
  98. 98. UNDERSTAND DETECTIVE C. TODD LOMBARDO — @IAMCTODD
  99. 99. UNDERSTAND DETECTIVE DIVERGE ARTIST C. TODD LOMBARDO — @IAMCTODD
  100. 100. UNDERSTAND DETECTIVE DIVERGE ARTIST CONVERGE SCIENTIST C. TODD LOMBARDO — @IAMCTODD
  101. 101. UNDERSTAND DETECTIVE DIVERGE ARTIST CONVERGE SCIENTIST PROTOTYPE ARCHITECT C. TODD LOMBARDO — @IAMCTODD
  102. 102. UNDERSTAND DETECTIVE DIVERGE ARTIST CONVERGE SCIENTIST PROTOTYPE ARCHITECT TEST JOURNALIST C. TODD LOMBARDO — @IAMCTODD
  103. 103. DESIGNER SCIENTIST EMPATHIC MAKER FORWARD LOOKING RIGOROUS EXPERIMENTAL HYPOTHESIS DRIVEN
  104. 104. DESIGNTIST
  105. 105. SCIENTIFIC METHOD DESIGN PROCESS AGILE PHILOSOPHY design sprint
  106. 106. It’s much easier to build anything, than build the right thing. C. Todd Lombardo GUY WHO JUST QUOTED HIMSELF
  107. 107. WHAT IS RIGHT?
  108. 108. WHO IS RIGHT? WHAT IS RIGHT?
  109. 109. Life is too short to build something nobody wants. Ash Maurya AUTHOR, RUNNING LEAN, & SCALING LEAN
  110. 110. ctodd@freshtilledsoil.com #designsprint @iamctodd
  111. 111. APPENDIX
  112. 112. AGENDA HACKS…
  113. 113. 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
  114. 114. 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
  115. 115. 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
  116. 116. MONDAY TUESDAY WEDNESDAY THURSDAY FRIDAY UNDERSTAND DIVERGE CONVERGE PROTOTYPE TEST Week 1 Week 2 PREP + RESEARCH DEBRIEF Agenda: Two-Week Hack
  117. 117. 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
  118. 118. 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
  119. 119. HOW TO §@%& IT UP?
  120. 120. Design Sprint ains
  121. 121. Design Sprint ○ “We need Sashi, Jen, Joe, Frank, Aman, and Nadia, too!” —Two pizza rule ains
  122. 122. 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
  123. 123. 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
  124. 124. 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
  125. 125. 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

×