Now one question that people will ask, "Could you validate a product with the design sprint without knowing the theories behind Design Thinking?" Well, the answer is Yes, it's like buying a cookbook from Jamie Oliver, and there's a cool complex meal, but all you have to do is read it step by step to execute it.
Now maybe you won't cut the onions entirely. Perhaps you won't cook the pasta exactly the exact weight needs to be, but yes, you would be able to make this pasta dish with a recipe and know who should do what. If you want to, if you only had design thinking independently, you have to be an expert. You have to understand how to play out these recipes precisely, so that's why the design sprint filled this missing piece of the puzzle.
Suppose we look at how product design and how some innovative product processes worked before, there was design thinking, so that's almost like the research phase. We're going to design thinking to figure out the problem like understand the users you know, brainstorm and prototype and try out these things, and get deep into the user challenge, so the Design Thinking part is this human-centered approach. Then it would almost go from here to into the actual implementation. There was a missing part of the puzzle.
How do you validate that product? How do we validate the should even make this in the first place. Design Thinking was used for that, but there was no exact recipe for getting there, and that's really what the design sprint is. This kind of recipe allows you to take the learnings and the skill the mindset from design thinking and apply it to a production process. What I like about the design sprint as well is that it's design thinking is not super useful without a recipe, so you know before. When we used to get a project, people would say, " Hey, can you help us with this new app" we would say "yes," and we'd have to go away look into our design thinking tool kit and think about what sort of recipe will be used for this project? We would change it every time so we wouldn't be able to battle the test one recipe. Whereas the design sprint has been this recipe, we've been testing over and over and over and over again for years, and we know it is an excellent recipe for validating products for coming up with new product ideas, and for testing things exceptionally quickly.
People are often afraid of design thinking because it's for creatives, and designers use design thinking. It's one of those things that turns a lot of like stakeholders and the product managers, and you know people who are just interested in designing products and making products it kind of turns those people off. Whereas the design Sprint is a freezing step-by-step robust serious process with very little creativity involved. Almost anyone in your company will feel comfortable being part of a design sprint process because it has this more strategic and business angle to it as well. Rather than design thinking, it is excellent for us designers to get everything out on the table. When it comes to executing and figuring out, should we make this product what this product should be, then the design sprint is the answer to that question.