I have already written an article about Design Sprint, besides I would like to bring in a series in which I will illuminate the individual days in detail again. In this article, I’d like to say a little bit more about why I think Design Sprints fits very well in many companies.
What is one of the major problem we face with innovative projects in the company? Or problems we want to solve in a creative way and whiteness?
We can not estimate when we will finish, whether we will finish or with what effort we will come to a possible solution. Further, we can not even be sure if we will have a solution at all. Which, of course, if we want to complete or sell our project in the company, will cause huge difficulties. Product managers, HR managers, management usually work according to plans that are partially worked out in detail. And now we come with our idea to use an open-results method to develop new ideas and concepts. The apparently also without any frame comes along.
Here we often encounter resistance because we can not estimate necessary time and effort. Here we come slowly to the theme of the Design Sprint.
Compared to classic design thinking, we naturally have clearer structures that make it easier to present and present. I do not want to say that Design Sprint should replace Design Thinking. Also, the application is a little different. In the sprint it is usually an advantage if we already know in which direction the journey should go, the Design Thinking is completely open and develops with the process. This also makes the idea interesting to combine both. First the thinking to develop an idea and then to substantiate the sprint around it. But that makes it even harder, of course. So one by one.
Concept of Design Sprint is to develop a solution concept in only 5 working days. You follow a strictly respected plan and work step by step towards a possible result. Team building and orientation on Monday will then be about developing concepts for prototyping and testing on Friday. Determined by a strict set of rules and a streamlined schedule, our Sprint has been completed this week and can hopefully produce beautiful, interesting and practical results.
This concept is of course ideal to use in a company. Requirements, framework and concept are clearly formulated and implementable. The availability of employees is of course still a topic but we know at least sometimes the effort.
This is one of the strongest advantages of using this method; people in a project are deployed for a clearly defined time. The effort can be defined and a possible result can be expected on a defined date, namely on Friday. Of course, these conditions make it much easier to sell the method to management and get approvals and resources.
At the end
In conclusion I would like to say that the Design Sprint can score with its clearly defined structures. The communication of the project to stakeholders and management seems much easier. The strict rules that restrict the participants in their daily work but are certainly a hurdle, but that can be solved. I do not want to replace design thinking. I’m still a big fan of the method. But one should be concerned with the field, because in my opinion every method has its field of application in which it works best.
Of course you should just give it a try.