Perfect Time of Design Sprint
I learned many things in the product management class at Binar Academy. Once upon a time, I was confused in understanding the design sprint method, where it was difficult for me to distinguish between design sprints and design thinking. Apart from that, there are various other similar terms such as lean startup and agile. The questions that popped up in my head at that time is, “How to distinguish between the two?”, “When is the right time to use this method?”
To get the answer, we start with the definition and purpose of the design sprint. A design sprint is a framework that takes 5 days to help companies create product concepts and prototypes. It takes communication and interaction in carrying out the various stages in the design sprint. The goal is that we are able to issue various types of ideas, problems, as well as solutions that must later be tested for potential users. From the statement above, we can understand that a design sprint is a way to solve a problem in a product quickly. That means, the design sprint method can be used if we have created a solution to the problem in the form of a product later.
The design sprint has 5 stages where in 1 day there will be 1 stage to be done. The five stages consist of Understand, Diverge, Decide, Prototype, and Validate. The Understand stage aims to determine targets that can be completed in this sprint. From the product idea that you already have, of course, there will be new problems that cannot be solved with the product idea. Therefore, a deeper understanding of the problem is needed. The techniques that can be used are interviews, focus group discussions, surveys, and problem analysis from all online tools or metrics.
The next stage, namely divergence, is carried out to find solutions to the problems that have been discussed at the understand stage. In making a solution, it is important to stay focused on the core of the problem by measuring the urgency of the problem. Another thing that needs to be prepared is the user persona that will be used as user validation.
After collecting solutions, proceed to the decide stage, each solution idea will be explained by each originator. The group will discuss and vote on the best solution ideas to be implemented later. Next, a sketch will be created based on the chosen solution idea.
The last stage is the prototype stage and the validation stage. The prototype was created initially as a tester by users to get feedback from them. This test must be objective. Therefore, developers from these companies should not participate in testing because there is a tendency to be subjective. Good validation produces targeted and maximum product results so that the product can slide to the next stage, namely commercialization.