Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Design Sprints: A Non-Google Approach

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.

C. Todd Lombardo

June 14, 2017
Tweet

More Decks by C. Todd Lombardo

Other Decks in Design

Transcript

  1. DESIGN SPRINTS:
    A NON-GOOGLE APPROACH
    JUNE 14, 2017
    C. TODD LOMBARDO
    CHIEF DESIGN STRATEGIST, FRESH TILLED SOIL
    @IAMCTODD — [email protected]

    View Slide

  2. Not this one.
    This one.

    View Slide

  3. Not this one.
    This one.

    View Slide

  4. EVERYONE HAS A PROCESS
    C. TODD LOMBARDO — @IAMCTODD

    View Slide

  5. View Slide

  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

    View Slide

  7. Source: gv.com; thoughtbot.com; smashngmagazine.com

    View Slide

  8. Empathize Define Prototype Test
    Ideate
    Discovery Interpretation Experimentation Evolution
    Ideation
    Source: gv.com; thoughtbot.com; smashngmagazine.com

    View Slide

  9. Source: IBM

    View Slide

  10. Source: Design Council UK

    View Slide

  11. APPLIED DESIGN-THINKING
    C. TODD LOMBARDO — @IAMCTODD

    View Slide

  12. View Slide

  13. Source: google.com

    View Slide

  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

    View Slide

  15. Our Design Sprint Approach
    C. TODD LOMBARDO — @IAMCTODD

    View Slide

  16. Our Design Sprint Approach
    UNDERSTAND
    C. TODD LOMBARDO — @IAMCTODD

    View Slide

  17. Our Design Sprint Approach
    UNDERSTAND DIVERGE
    C. TODD LOMBARDO — @IAMCTODD

    View Slide

  18. Our Design Sprint Approach
    UNDERSTAND DIVERGE CONVERGE



    C. TODD LOMBARDO — @IAMCTODD

    View Slide

  19. Our Design Sprint Approach
    UNDERSTAND DIVERGE CONVERGE



    C. TODD LOMBARDO — @IAMCTODD

    View Slide

  20. Our Design Sprint Approach
    UNDERSTAND DIVERGE CONVERGE PROTOTYPE



    C. TODD LOMBARDO — @IAMCTODD

    View Slide

  21. Our Design Sprint Approach
    UNDERSTAND DIVERGE CONVERGE PROTOTYPE TEST



    X



    C. TODD LOMBARDO — @IAMCTODD

    View Slide

  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?

    View Slide

  23. LEAN STARTUP?
    LEAN UX?
    C. TODD LOMBARDO — @IAMCTODD

    View Slide

  24. LEARN
    BUILD MEASURE
    PRODUCT
    DATA
    IDEAS

    View Slide

  25. BUILD
    BUILD BUILD
    PRODUCT
    PRODUCT
    PRODUCT
    Credit: Wolf Bruening

    View Slide

  26. LEARN
    BUILD MEASURE
    PRODUCT
    DATA
    IDEAS
    START HERE?

    View Slide

  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

    View Slide

  28. View Slide

  29. MAKE
    THINGS
    PEOPLE
    WANT
    MAKE
    PEOPLE
    WANT
    THINGS
    >
    (OR NEED, OR LOVE!)

    View Slide

  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

    View Slide

  31. ASSUMPTIONS
    BACKGROUND INSIGHTS
    “WHO”
    JOURNEY
    PROBLEM
    STATEMENT
    REFRAME
    PHASE 2

    View Slide

  32. ASSUMPTIONS:
    WHAT YOU THINK YOU KNOW

    View Slide

  33. CONNECT 9 DOTS.
    WITH 4 OR LESS STRAIGHT LINES.
    DO NOT LIFT YOUR PEN.

    View Slide

  34. View Slide

  35. View Slide

  36. HI
    HI
    LO
    LO
    Importance
    Risk

    View Slide

  37. HI
    HI
    LO
    LO
    Importance
    Risk

    View Slide

  38. HI
    HI
    LO
    LO
    Importance
    Risk
    HIGH IMPORTANCE
    HIGH RISK
    HIGH IMPORTANCE
    LOW RISK
    LOW IMPORTANCE
    LOW RISK
    LOW IMPORTANCE
    HIGH RISK

    View Slide

  39. HI
    HI
    LO
    LO
    Importance
    Risk
    HIGH IMPORTANCE
    HIGH RISK
    HIGH IMPORTANCE
    LOW RISK
    LOW IMPORTANCE
    LOW RISK
    LOW IMPORTANCE
    HIGH RISK

    View Slide

  40. View Slide

  41. Problem Statement
    A problem statement is a challenge that
    has business value for a persona
    INSPIRED BY: SIRIUSDECISIONS

    View Slide

  42. Problem Statement
    A problem statement is a challenge that
    has business value for a persona
    INSPIRED BY: SIRIUSDECISIONS

    View Slide

  43. Problem Statement
    A problem statement is a challenge that
    has business value for a persona
    INSPIRED BY: SIRIUSDECISIONS

    View Slide

  44. Problem Statement
    A problem statement is a challenge that
    has business value for a persona
    INSPIRED BY: SIRIUSDECISIONS

    View Slide

  45. Problem Statement
    A problem statement is a challenge that
    has business value for a persona
    WHAT
    WHY WHO
    INSPIRED BY: SIRIUSDECISIONS

    View Slide

  46. Example
    INSPIRED BY: SIRIUSDECISIONS

    View Slide

  47. Example
    Human resources lacks
    recruiting software
    INSPIRED BY: SIRIUSDECISIONS

    View Slide

  48. Example
    Human resources lacks
    recruiting software
    BAD
    INSPIRED BY: SIRIUSDECISIONS

    View Slide

  49. Example
    Human resources lacks
    recruiting software
    Human resource struggles to
    hire top talent to maintain a
    competitive advantage
    BAD
    INSPIRED BY: SIRIUSDECISIONS

    View Slide

  50. Example
    Human resources lacks
    recruiting software
    Human resource struggles to
    hire top talent to maintain a
    competitive advantage
    BAD
    GOOD
    INSPIRED BY: SIRIUSDECISIONS

    View Slide

  51. Problem Statement
    Human Resources struggle to hire top
    talent to maintain a competitive advantage
    WHAT WHY
    WHO
    INSPIRED BY: SIRIUSDECISIONS

    View Slide

  52. WHAT ARE YOU SOLVING FOR?
    really

    View Slide

  53. REFRAME?

    View Slide

  54. View Slide

  55. THERE’S NO
    OPPORTUNITY,
    NOBODY IS
    WEARING ANY
    SHOES!

    View Slide

  56. THERE’S NO
    OPPORTUNITY,
    NOBODY IS
    WEARING ANY
    SHOES!
    THERE’S A HUGE
    OPPORTUNITY,
    NOBODY IS
    WEARING ANY
    SHOES!

    View Slide

  57. Title (H1)
    PROBLEM SOLUTION
    INSPIRED BY: WOLF BRUENING

    View Slide

  58. Title (H1)
    PROBLEM SOLUTION
    Water on the floor Mop
    INSPIRED BY: WOLF BRUENING

    View Slide

  59. Title (H1)
    PROBLEM SOLUTION
    Water on the floor Mop
    WHY? Leaky pipe Fix pipe
    INSPIRED BY: WOLF BRUENING

    View Slide

  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

    View Slide

  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

    View Slide

  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

    View Slide

  63. THINK LIKE A DETECTIVE

    View Slide

  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

    View Slide

  65. When ___
    I need__
    So that___
    JOB STORY SIX UP STORYBOARD

    View Slide

  66. When ___
    I need__
    So that___
    JOB STORY SIX UP STORYBOARD

    View Slide

  67. When ___
    I need__
    So that___
    JOB STORY SIX UP STORYBOARD

    View Slide

  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___

    View Slide

  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___

    View Slide

  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___

    View Slide

  71. JOB STORIES

    View Slide

  72. “JOB?”

    View Slide

  73. WHEN ___SITUATION___,
    I WANT/NEED __MOTIVATION__,
    SO THAT / BECAUSE __OUTCOME__.

    View Slide

  74. WHEN IT’S 3PM AND I’M SLEEPY,
    I NEED A PICK-ME-UP,
    SO THAT I CAN BE ALERT FOR MY TEAM.

    View Slide

  75. SIX-UPS

    View Slide

  76. View Slide

  77. MOAR IDEAS?!

    View Slide

  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

    View Slide

  79. STORYBOARDS

    View Slide

  80. View Slide

  81. DRAW FRAME 1
    HEADLINE
    FRAME 1 OPENING
    DRAW FRAME 2
    FRAME 2 MIDDLE
    FRAME 3 RESOLVE
    DRAW FRAME 3

    View Slide

  82. JOB STORY
    A
    JOB STORY
    B

    View Slide

  83. JOB STORY
    SIX-UP
    STORY BOARD

    View Slide

  84. THINK LIKE AN ARTIST

    View Slide

  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

    View Slide

  86. Process
    UNDERSTAND DIVERGE CONVERGE PROTOTYPE TEST



    X



    View Slide

  87. ASSUMPTIONS STORYBOARDS SKETCHING

    View Slide

  88. ASSUMPTION MATCHING

    View Slide

  89. Storyboards Existing
    Assumptions
    New
    Assumptions

    View Slide

  90. View Slide

  91. ASSUMPTION TABLE

    View Slide

  92. View Slide

  93. Assumption

    View Slide

  94. Test by …?
    Assumption

    View Slide

  95. Test by …? Valid if…?
    Assumption

    View Slide

  96. Storyboards Assumptions

    View Slide

  97. Storyboards Assumptions Test by …? Valid if…?

    View Slide

  98. View Slide

  99. SKETCHING &
    RITUAL DISSENT

    View Slide

  100. THINK LIKE A SCIENTIST

    View Slide

  101. PROTOTYPE
    PROTOTYPE
    Refine sketch
    Build it!
    PLAN INTERVIEWS
    Define Questions
    Define Tasks
    Confirm Interview
    WRAP-UP
    Daily Retrospective

    View Slide

  102. marshmallowchallenge.com

    View Slide

  103. View Slide

  104. View Slide

  105. View Slide

  106. View Slide

  107. View Slide

  108. PROTOTYPES ARE
    MINIMIM VIABLE CONCEPTS

    View Slide

  109. THINK LIKE AN ARCHITECT

    View Slide

  110. TEST
    INTERVIEWS
    1
    2
    WRAP-UP
    Sprint Debrief
    Daily Retrospective

    View Slide

  111. 1. PRE-ROLL QUESTIONS
    2. TEST / TASKS
    3. POST-ROLL QUESTIONS

    View Slide

  112. Interview Structure

    View Slide

  113. Interview Structure
    1. Pre Roll: Establish background questions
    (“how do you currently…”)

    View Slide

  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…”)

    View Slide

  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…?”)

    View Slide

  116. View Slide

  117. BE. @%. CURIOUS.

    View Slide

  118. THINK LIKE AN JOURNALIST

    View Slide

  119. RETROSPECTIVE
    what worked?
    ..was validated?
    ..did you learn?

    View Slide

  120. View Slide

  121. OK, NOW WHAT?

    View Slide

  122. X ?
    IT WORKED! IT DIDN’T! HMMM..
    Possible Outcomes

    View Slide

  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

    View Slide

  124. IT’S THE MINDSET…
    C. TODD LOMBARDO — @IAMCTODD

    View Slide

  125. UNDERSTAND
    DETECTIVE
    C. TODD LOMBARDO — @IAMCTODD

    View Slide

  126. UNDERSTAND
    DETECTIVE
    DIVERGE
    ARTIST
    C. TODD LOMBARDO — @IAMCTODD

    View Slide

  127. UNDERSTAND
    DETECTIVE
    DIVERGE
    ARTIST
    CONVERGE
    SCIENTIST
    C. TODD LOMBARDO — @IAMCTODD

    View Slide

  128. UNDERSTAND
    DETECTIVE
    DIVERGE
    ARTIST
    CONVERGE
    SCIENTIST
    PROTOTYPE
    ARCHITECT
    C. TODD LOMBARDO — @IAMCTODD

    View Slide

  129. UNDERSTAND
    DETECTIVE
    DIVERGE
    ARTIST
    CONVERGE
    SCIENTIST
    PROTOTYPE
    ARCHITECT
    TEST
    JOURNALIST
    C. TODD LOMBARDO — @IAMCTODD

    View Slide

  130. DESIGNER SCIENTIST
    EMPATHIC
    MAKER
    FORWARD LOOKING
    RIGOROUS
    EXPERIMENTAL
    HYPOTHESIS DRIVEN

    View Slide

  131. DESIGNTIST

    View Slide

  132. SCIENTIFIC
    METHOD
    DESIGN
    PROCESS
    AGILE
    PHILOSOPHY design
    sprint

    View Slide

  133. It’s much easier to build anything,
    than build the right thing.
    C. Todd Lombardo
    GUY WHO JUST QUOTED HIMSELF

    View Slide

  134. View Slide

  135. WHAT
    IS
    RIGHT?

    View Slide

  136. WHO
    IS
    RIGHT?
    WHAT
    IS
    RIGHT?

    View Slide

  137. Life is too short to build
    something nobody wants.
    Ash Maurya
    AUTHOR, RUNNING LEAN, & SCALING LEAN

    View Slide

  138. [email protected]
    #designsprint
    @iamctodd

    View Slide

  139. APPENDIX

    View Slide

  140. AGENDA HACKS…

    View Slide

  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

    View Slide

  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

    View Slide

  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

    View Slide

  144. MONDAY TUESDAY WEDNESDAY THURSDAY FRIDAY
    UNDERSTAND DIVERGE CONVERGE
    PROTOTYPE TEST
    Week 1
    Week 2
    PREP + RESEARCH
    DEBRIEF
    Agenda: Two-Week Hack

    View Slide

  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

    View Slide

  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

    View Slide

  147. HOW TO §@%& IT UP?

    View Slide

  148. Design Sprint
    ains

    View Slide

  149. Design Sprint
    ○ “We need Sashi, Jen, Joe, Frank, Aman, and Nadia, too!” —Two pizza rule
    ains

    View Slide

  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

    View Slide

  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

    View Slide

  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

    View Slide

  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

    View Slide