There are a multitude of reasons why you should use a Design Sprint. However, an important rule of thumb is: if the investment for a Design Sprint is equal to, or lower than the risk that you are trying to hedge, you do not really need a Design Sprint. All the more reason to do it! If the expected risk is higher, these are the main reasons why you want to do a Sprint:

  • To create focus
  • To make ideas tangible
  • To get a clear Go / No Go
  • To create support within the team / organization
  • To get the various stakeholders in line
  • To strengthen your case with a proof of concept
  • To get direct feedback from customers and / or consumers on assumptions
  • To get quick answers to important questions in a practical manner
  • To incorporate knowledge and experience from multiple disciplines into your solution and eliminate noise.


If you know why you want to do a Design Sprint, it is also useful to know when it is best to do this. The list with answers to this question is remarkably shorter and straight forward. A Design Sprint is useful when:

  • You want to test a daring idea
  • You developed a new product or service
  • A new proposition must be devised
  • There is disagreement about which approach works best
  • There is a lot at stake and the risk you take is therefore high
  • The existing service or the existing product must be improved
  • There are several good ideas in the organization and it is somehow not possible to bring them together