Should you do a Design Sprint Workshop?

So you have come up with a great idea for a mobile app. Or maybe you are thinking of redesigning your existing website, or possibly developing a new internal application to streamline your business process? But where do you begin? And most importantly, how do you make sure you are solving the right problem in the best possible way. It's easy to get too excited and jump right into the implementation, but if the problem-solution space was not verified carefully it will probably lead you to failure.
Countless startup entrepreneurs have made the mistake over and over again. Pouring enormous amounts of money, time, and effort into launching an app or a solution, only to discover that problem they were persuing to solve, really doesn't exist or that nobody cared about it.
I even argue that holding only a one-time 5-day Design Sprint workshop at the beginning of the project is not enough, as the results must be challenged again and again. And by end of this article, you will understand why. 

Your idea is a hypothesis

Your idea is a hypothesis and this is the way you should think about it. It's a hypothesis of why your solution will solve a problem.

And before spending thousands of hard-earned dollars, we should first be sure that the problem really exists and that the problem we will be solving is a problem people actually care about.

So, because of this, or first Day of the Desing sprint is all about developing a common understanding of the context within which we are working and all the elements in that context (the problem, the business, the customer, the value prop/hypothesis, and how does the success look like). Our goal is to expose risky knowledge gaps and identify risky assumptions so that we can make plans for reducing those risks and move forward confident we are heading in the right direction and solving the right problem. Also, by gather this info, we will empower our decision-making abilities and eliminate the need for guesswork later on.