Design sprints for teams

Table of contents

1. What Is a Design Sprint?
   1. Uses of a Design Sprint
      1. At the beginning of a project
      2. In the middle of a project
      3. For a mature project
   2. How the Design Sprint Came to Be
      1. From Agile
      2. From design charrettes
      3. From digital product design
      4. From Google Ventures
   3. Created for Startups, Great for Enterprises
      1. For startups
      2. For enterprises
   4. Success = Time and Money Saved + Minds Blown
      1. Success by preventing failure
      2. When you get validation
      3. Some validation, some things to fix
      4. When you don’t get validation
   5. Takeaways:
2. When (and When Not) to Do a Design Sprint
   1. Why Do a Design Sprint?
      1. Speed, efficiency, and focus will increase
      2. To align a diverse team
      3. To have a clear process
      4. To start a new project in a clear direction
   2. When Not to Use a Design Sprint
      1. The product is already very well-defined
      2. Significant research is needed beyond the scope of 1–2 days of interviews
      3. The project is only a few days in scope
      4. The business opportunity isn’t clear
      5. The scope is far too broad
      6. A more sophisticated product development effort is required
      7. You won’t break up with your idea: The IKEA effect
   3. Takeaways:
3. After the Design Sprint: Capture, Iterate, and Continue
   1. What Happens Next?
   2. Capture and Document
      1. For the design firm
      2. For the product team within an organization
   3. Determine Next Steps
   4. Continue the Practice
      1. Make Design Sprints Commonplace
      2. It’s in Your Hands
   5. Takeaways