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

Building Products Using Design Sprints

Building Products Using Design Sprints

An introduction to why you need to validate your product ideas and provides an overview of Design Sprints that are used at Google Ventures and other leading product companies.

Abb84091c48db0687e73dd7b147db2af?s=128

Jeff Mikres

August 17, 2016
Tweet

Transcript

  1. Music City Agile 2016 - @jeffmikres 1

  2. Music City Agile 2016 - @jeffmikres 2 BUILDING PRODUCTS USING

    DESIGN SPRINTS @jeffmikres
  3. Music City Agile 2016 - @jeffmikres 3 Worked on, led,

    or managed agile teams for 12 years My experience is in Extreme Programming and Scrum Discovered Agile after reading Kent Beck’s XP Explained book in 2004 Started the Nashville Agile Users Group in 2007 agile background
  4. Music City Agile 2016 - @jeffmikres Web Application Development !

    " # Mobile App Development Cloud API Development consumer platforms team
  5. Music City Agile 2016 - @jeffmikres 5 agile gets us

    only so far $ Traditionally, Agile helps us deliver working software with its proven principles & practices
  6. Music City Agile 2016 - @jeffmikres 6 We embraced the

    Agile Manifesto
  7. None
  8. Music City Agile 2016 - @jeffmikres 8 Manifesto was about

    developing software
  9. Music City Agile 2016 - @jeffmikres 9 And it worked…

  10. Music City Agile 2016 - @jeffmikres 10 But what makes

    a product successful?
  11. Music City Agile 2016 - @jeffmikres Is it using all

    of these?
  12. Music City Agile 2016 - @jeffmikres 12 Waterfall | Years

    XP/Scrum | Weeks Kanban | Days Continuous | Hours Is it Faster Delivery?
  13. Music City Agile 2016 - @jeffmikres 13 Impressive Test Suites?

    100%
  14. Music City Agile 2016 - @jeffmikres 14 Is it Saving

    Money?
  15. Music City Agile 2016 - @jeffmikres 15 We’ve missed this

    Validated product ideas
  16. Music City Agile 2016 - @jeffmikres 16 Misses Have we

    identified a job-to-be-done with our product? Do our customers want to hire our product? Have we validated our product idea with real customers? Do we have product / market fit?
  17. Music City Agile 2016 - @jeffmikres 17 So we push

    our product out and… we get low adoption, sales, etc.
  18. Music City Agile 2016 - @jeffmikres 18 DESIGN SPRINTS from

    google
  19. Music City Agile 2016 - @jeffmikres 19 2007 2016 Jake

    Knapp at Google 2009 Gmail Google Ventures Sprint Book 100’s of Sprints 2011
  20. None
  21. Music City Agile 2016 - @jeffmikres 21 Sprints Used At

  22. Music City Agile 2016 - @jeffmikres 22 Elevator pitch of

    a Sprint A very focused, highly collaborative 5-day session with your team ideating your “big” product goal, building a prototype, and culminating in real testing with real, potential customers on Friday
  23. Music City Agile 2016 - @jeffmikres 23 Decide if you

    should take a product idea to the next steps of actually building it Why use a Sprint? % When you need to get a project moving again Validate an important decision
  24. Music City Agile 2016 - @jeffmikres 24 Let’s Dive In

  25. Music City Agile 2016 - @jeffmikres 25 5 Full Days

    Team Around 7 People Lots of Collaboration Room for team with lots of whiteboards General Sprint Rules
  26. Music City Agile 2016 - @jeffmikres 26 Who’s in your

    Sprint? DECIDER FACILITATOR ENGINEERS BIZ DEV & Experts DESIGNERS PRODUCT MANAGERS
  27. Music City Agile 2016 - @jeffmikres 27 Day 1 -

    Big Goal & Map &
  28. Music City Agile 2016 - @jeffmikres 28 We need to

    pick our long-term goal! Pick our Big Goal % “Why are we doing this thing?” “Where do we want to be in 6 months, 1 year?”
  29. Music City Agile 2016 - @jeffmikres 29 Provide low-cost movers

    that are available whenever you need something moved no matter how big or small. Reimagine how a thermostat can interact with a home. Offer a hotel-like experience to travelers for half the cost. LONG TERM GOALS
  30. Music City Agile 2016 - @jeffmikres 30 Sprint Questions %

    “What assumptions are lurking around our goal?” “If a year from now we fail - what could’ve caused it?” “To meet our long-term goal - what needs to be true?”
  31. Music City Agile 2016 - @jeffmikres 31 How will customers

    discover our product? Can we find people willing to help move a customer at a moments notice? Will our customers feel safe letting people they’ve never met move their things? SPRINT QUESTIONS
  32. Music City Agile 2016 - @jeffmikres 32 Building Your Map

    a story through the steps of our big idea Next Step
  33. Music City Agile 2016 - @jeffmikres 33 Map Customer Search

    web for movers Find Us on Web Workers See ad to get paid to move Check Pricing Check Availability Check Safety Hire us to move their stuff Decide if pay is adequate Apply to be a mover Customer Service Vet potential movers Approve workers for jobs Wait for vetting Pick up moving jobs
  34. Music City Agile 2016 - @jeffmikres 34 Validating Your Map

    with your Experts Next Step
  35. Music City Agile 2016 - @jeffmikres 35 Ask the Experts

    % Review your whiteboard (big goal, sprint questions & our map) with the experts Listen intently to their input Take a lot of notes
  36. Music City Agile 2016 - @jeffmikres 36 I’m not sure

    how we will be able to quickly do background checks on all the potential movers who’ll work for us. HMW … find an external vendor that can provide real time background checks… Taking Notes with Experts
  37. Music City Agile 2016 - @jeffmikres 37 Map Customer Search

    web for movers Find Us on Web Workers See ad to get paid to move Check Pricing Check Availability Check Safety Hire us to move their stuff Decide if pay is adequate Apply to be a mover Customer Service Vet potential movers Approve workers for jobs Wait for vetting Pick up moving jobs I’m not sure how we will be ble to quickly do background checks I’m not sure how we will be ble to quickly do background checks I’m not sure how we will be ble to quickly do background checks I’m not sure how we will be ble to quickly do background checks Add HMW Notes
  38. Music City Agile 2016 - @jeffmikres 38 Time to Pick

    A Target Next Step
  39. Music City Agile 2016 - @jeffmikres 39 It’s Decision Time

    % The Decider now has to make the call on the target of our map to move forward with. If Decider wants they can do a straw poll with sprint team. Ultimately it comes down to their decision.
  40. Music City Agile 2016 - @jeffmikres 40 Map Customer Search

    web for movers Find Us on Web Workers See ad to get paid to move Check Pricing Check Availability Check Safety Hire us to move their stuff Decide if pay is adequate Apply to be a mover Customer Service Vet potential movers Approve workers for jobs Wait for vetting Pick up moving jobs I’m not sure how we will be ble to quickly do background checks I’m not sure how we will be ble to quickly do background checks I’m not sure how we will be ble to quickly do background checks I’m not sure how we will be ble to quickly do background checks Pick Your Target
  41. Music City Agile 2016 - @jeffmikres 41 Day 1 -

    Recap &
  42. Music City Agile 2016 - @jeffmikres 42 Day 2 -

    Ideate and Sketch '
  43. Music City Agile 2016 - @jeffmikres 43 Finding Inspiration

  44. Music City Agile 2016 - @jeffmikres 44 Remix and Improve

    The team individually looks for inspiring products and services that they like Products can be in the same domain or in different ones. Inspiration is everywhere. Ask questions and take notes! Put them up on the whiteboard for later Lightning Rounds - each team members walks everyone through their favorite 1 or 2 products
  45. Music City Agile 2016 - @jeffmikres 45 Sketching Next Step

  46. Music City Agile 2016 - @jeffmikres 46

  47. Music City Agile 2016 - @jeffmikres 47 Sketching Rules %

    Sketch by yourself! This is not group brainstorming. You should be sketching off of the target the Decider selected from the team’s map. Review everything the team’s got on the whiteboards before you start sketching.
  48. Music City Agile 2016 - @jeffmikres 48

  49. Music City Agile 2016 - @jeffmikres 49 Examples

  50. Music City Agile 2016 - @jeffmikres 50 Day 2 -

    Recap '
  51. Music City Agile 2016 - @jeffmikres 51 Day 3 -

    Sketch Review / Storyboarding (
  52. Music City Agile 2016 - @jeffmikres 52 Sketch Reviews -

    Step 1 % Team members put dot stickers on the parts of the sketches that you like. All team members review them silently Facilitator gets them up on wall.
  53. Music City Agile 2016 - @jeffmikres 53 Sketch Reviews -

    Step 2 % Team - straw poll after sketch review Facilitator - speed critique Decider - they get supervotes!
  54. Music City Agile 2016 - @jeffmikres 54 Storyboarding Next Step

  55. Music City Agile 2016 - @jeffmikres 55 Storyboard Rules %

    Start your storyboard upstream to make it realistic Storyboard enough detail so it’s self explanatory for customer testing Use the Decider’s favorite sketches (dot voted)
  56. Music City Agile 2016 - @jeffmikres 56 Example Storyboard

  57. Music City Agile 2016 - @jeffmikres 57 Day 3 -

    Recap (
  58. Music City Agile 2016 - @jeffmikres 58 Day 4 -

    Build the Prototype )
  59. Music City Agile 2016 - @jeffmikres 59 Prototypes - solving

    for the surface % Get the surface right first! Surface of your product is where your customers interact with you Get it wrong - technology doesn’t matter
  60. Music City Agile 2016 - @jeffmikres 60 We want fast

    feedback
  61. Music City Agile 2016 - @jeffmikres 61 The Prototype Mindset

    % Prototypes are disposable You can prototype anything Build just enough to learn - but make it real
  62. Music City Agile 2016 - @jeffmikres 62 Prototype Tools

  63. Music City Agile 2016 - @jeffmikres 63 Roles to build

    Prototype MAKERS STITCHERS DECIDER INTERVIEWER WRITER ASSET COLLECTOR
  64. Music City Agile 2016 - @jeffmikres 64 Do a Trial

    Run Next Step
  65. Music City Agile 2016 - @jeffmikres 65 Day 4 -

    Recap )
  66. Music City Agile 2016 - @jeffmikres 66 Day 5 -

    Customer Testing *
  67. Music City Agile 2016 - @jeffmikres 67 Customer Testing %

    If it doesn’t work - you’ve lost one week We want real, validated learning. Opinions are meaningless. We test with 5 customers
  68. Music City Agile 2016 - @jeffmikres 68 Interviewer with customer

  69. Music City Agile 2016 - @jeffmikres 69 Team watching customer

    interviews
  70. Music City Agile 2016 - @jeffmikres 70 Start the Interviews

  71. Music City Agile 2016 - @jeffmikres 71 Talk about the

    weather, small talk, etc. Reassure them that we want their feedback, that it’s important, and to be honest. Also indicate you are impartial to the solution. Step 1 “friendly welcome”
  72. Music City Agile 2016 - @jeffmikres 72 Ask questions about

    their life, interests, activities The questions should be relevant to the product we’re working on in the sprint Step 2 “context questions”
  73. Music City Agile 2016 - @jeffmikres 73 Ask for permission

    to start the test Introduce the tasks to accomplish in prototype Ask a ton of questions (open-ended) Let them know that some things may not work quite right in the prototype Step 3 “introduce the prototype”
  74. Music City Agile 2016 - @jeffmikres 74 Give them clues

    for the test through the prototype. Offer up open-ended tasks for them to accomplish Don’t tell them what to do! Step 4 “tasks and nudges”
  75. Music City Agile 2016 - @jeffmikres 75 “How does this

    product compare with what you do now?” “What did you like about the product?” “What did you not like?” “How would you describe the product to a friend?” Step 5 “quick debrief”
  76. Music City Agile 2016 - @jeffmikres 76 Post-Interview Wrap up

    % Look for patterns Review all of the feedback your team captured. Watch back video if needed. Did we answer our sprint questions? Validate our big goal? The interview tasks were achieved?
  77. Music City Agile 2016 - @jeffmikres 77 Time for a

    Decision Our customers got it and we’re confident in moving forward! MOVE TO BUILD We had good feedback but tweaks need to be made REWORK & TEST The feedback was poor and significant change or pivot is needed. STOP or PIVOT
  78. Music City Agile 2016 - @jeffmikres 78 DESIGN SPRINTS WRAPPING

    UP
  79. Music City Agile 2016 - @jeffmikres 79 We want to

    validate our long-term goal in days We don’t want to commit to cost & time of building the real product yet We believe in high performing teams ability to ideate together We want a higher probability of success with our products. Why Sprints?
  80. Music City Agile 2016 - @jeffmikres 80 Better Chance for

    Success DESIGN SPRINTS
  81. Music City Agile 2016 - @jeffmikres 81 Challenge + Read

    the Book & references + Bring it back to your company. Experiment!! + Validate your product ideas.
  82. Music City Agile 2016 - @jeffmikres 82 Thank You

  83. Music City Agile 2016 - @jeffmikres 83 References 1.Agile Manifesto

    - http://www.agilemanifesto.org 2.Chaos Manifesto - 2012 - https://www.mountaingoatsoftware.com/blog/agile- succeeds-three-times-more-often-than-waterfall 3.You only need to test 5 users - Jakob Nielsen - https://www.nngroup.com/articles/ why-you-only-need-to-test-with-5-users/ 4.Customer Interviewing Tips - https://library.gv.com/get-better-data-from-user- studies-16-interviewing-tips-328d305c3e37#.yze6515qq 5.The Sprint Book Tools - http://www.thesprintbook.com/tools/ 6.Sprint Checklist - http://static1.squarespace.com/static/ 56778f460ab377c981686546/t/56c2b6c337013bc7bcab14c7/1456958631313/ Sprint+checklists.pdf 7.The five act interview - https://youtu.be/U9ZG19XTbd4