Design Sprints

Design Sprints

Talk given at UX Boston held at Google's Cambridge office.

An over view of how we run design sprints from years of running them at Constant Contact's Innovation Loft

You can see a video about Design Sprints at Constant Contact here: https://vimeo.com/120843429 (It's not a video of the talk, sorry)

7cbd3f5f922d798cc312eaf596de7ae6?s=128

C. Todd Lombardo

March 17, 2015
Tweet

Transcript

  1. 2 DESIGN SPRINTS

  2. 2 RESEARCH INSIGHTS IDEATION PROTOTYPE TEST

  3. DESIGN SPRINT WHY?

  4. I FOUND IS, ALL THE TIMES, THESE ARE NOT TEAMS

    THAT HAVE ALREADY JELLED AND FORMED AND NEED TO WORK. ” Karen Cross, Design Manager Atlassian
  5. WITHOUT UNIFYING THE PARTS AND BRANDING IT A PROCESS, MAKES

    IT TO DIFFICULT FOR THE PEOPLE WITH AUTHORITY TO UNDERSTAND. ” Alex Britez, Digital Strategy Designer Macmillan Education
  6. THE LAST TWO WEEKS OF THE PROJECT ARE LESS CRAZY.

    ” Matt Bridges, CTO Intrepid Labs
  7. DESIGN SPRINT

  8. DESIGN SPIKE

  9. PRODUCT DISCOVERY

  10. DISCOVERY SESSION

  11. DEEP DIVE

  12. None
  13. None
  14. None
  15. Innovation Team Existing CTCT Team

  16. Innovation Team Existing CTCT Team MVP Minimum Viable Product Project

    Team CTCT
  17. revolution Innovation Team Existing CTCT Team MVP Minimum Viable Product

    Project Team CTCT
  18. revolution evolution Innovation Team Existing CTCT Team MVP Minimum Viable

    Product Project Team CTCT
  19. 13

  20. 13

  21. 13

  22. 13 Innovation Team Existing CTCT Team

  23. 13 Innovation Team Existing CTCT Team clarify

  24. 13 Innovation Team Existing CTCT Team MVC Minimum Viable Concept

    clarify
  25. 13 Innovation Team Existing CTCT Team MVC Minimum Viable Concept

    MVP Minimum Viable Product build clarify
  26. 13 Innovation Team Existing CTCT Team MVC Minimum Viable Concept

    MVP Minimum Viable Product build clarify integrate Project Team EXISTING PRODUCT
  27. 13 Innovation Team Existing CTCT Team MVC Minimum Viable Concept

    MVP Minimum Viable Product build clarify New Team PRODUCT pilot integrate Project Team EXISTING PRODUCT
  28. 13 Innovation Team Existing CTCT Team MVC Minimum Viable Concept

    MVP Minimum Viable Product build clarify New Team PRODUCT pilot integrate Project Team EXISTING PRODUCT
  29. 13 Innovation Team Existing CTCT Team MVC Minimum Viable Concept

    MVP Minimum Viable Product build clarify scale New Team PRODUCT pilot integrate Project Team EXISTING PRODUCT
  30. 13 revolution Innovation Team Existing CTCT Team MVC Minimum Viable

    Concept MVP Minimum Viable Product build clarify scale New Team PRODUCT pilot integrate Project Team EXISTING PRODUCT
  31. 13 evolution revolution Innovation Team Existing CTCT Team MVC Minimum

    Viable Concept MVP Minimum Viable Product build clarify scale New Team PRODUCT pilot integrate Project Team EXISTING PRODUCT
  32. Source: gv.com; thoughtbot.com; smashngmagazine.com Understand Diverge Prototype Validate Decide Understand

    Diverge Build Test Converge Define Understand Build Test Ideate Unpack Sketch Prototype Test Decide 2013 2015
  33. UNDERSTAND

  34. 16

  35. 17

  36. NEED

  37. BREAKTHROUGH NEED

  38. BREAKTHROUGH NEED what really happens

  39. BREAKTHROUGH NEED assumptions

  40. None
  41. 20

  42. 21

  43. 22

  44. 23 JOURNEY MAPS

  45. None
  46. DIVERGE

  47. 26 CHALLENGE MAPS

  48. 27

  49. 28 When ___SITUATION___ happens, ! (__PERSONA__) need(s) to ! __OBJECTIVE__

    so that (or to obtain) ! __BENEFIT__. Credit: Alan Klement
  50. 29 When ___SITUATION___ happens, ! (__PERSONA__) need(s) to ! __OBJECTIVE__

    so that (or to obtain) ! __BENEFIT__. Credit: Alan Klement
  51. SIX-UPS

  52. None
  53. CONVERGE

  54. 33

  55. None
  56. 35

  57. BUILD

  58. 37

  59. 38 Lo Hi Interactive Fidelity Hi

  60. TEST

  61. 40

  62. 41

  63. DEBRIEF

  64. TEST METHOD METRICS VALIDATION BOARD ASSUMPTIONS EXPERIMENT SETUP RESULTS CORE

    HYPOTHESIS SUCCESS CRITERIA VALIDATED TEST NAME DATE BUSINESS OBJECTIVE TEAM INVALIDATED WHERE MORE DATA CAN BE FOUND CONCLUSIONS & RECOMMENDATIONS
  65. None
  66. 45 PLUS- DELTAS

  67. JUMP START

  68. None
  69. MVP Minimum Viable Product build

  70. MVP Minimum Viable Product build 30-60 days

  71. MVP Minimum Viable Product build Test Feedback from a small

    group of customers pilot 30-60 days
  72. MVP Minimum Viable Product build Test Feedback from a small

    group of customers pilot 30-60 days 30-60 days
  73. MVP Minimum Viable Product build Test Feedback from a small

    group of customers pilot Scale or fail Grow scale 30-60 days 30-60 days
  74. MVP Minimum Viable Product build Test Feedback from a small

    group of customers pilot Scale or fail Grow scale 30-60 days 30-60 days 30-60 days
  75. MVP Minimum Viable Product build Test Feedback from a small

    group of customers pilot Move to CTCT Project Team Transition integrate Scale or fail Grow scale 30-60 days 30-60 days 30-60 days
  76. MVP Minimum Viable Product build Test Feedback from a small

    group of customers pilot Move to CTCT Project Team Transition integrate Scale or fail Grow scale 30-60 days 30-60 days 30-60 days 30-60 days
  77. } } DESIGN SPRINT JUMP START

  78. LIFE IS TOO SHORT TO BUILD SOMETHING NOBODY WANTS. ”

    Ash Maurya, Author Running Lean
  79. BE A “DESIGNTIST”

  80. LEARN MORE hello@ctodd.com @iamctodd Early Release on O’Reilly Media designsprintbook.com