In the current moment in which we live, economic resources are limited, companies or clients are reluctant to start design projects that take a long time without knowing in depth the chances of success of said design.
There is a method called Design Sprint that helps speed up the design process and provides valuable and relevant information that ensures design success.
What is Design Sprint
Design Sprint a methodology created by Jake Knapp in 2010 and updated in 2018 while working at Google. This methodology consists of 6 phases. Depending on the project and the occasion, one phase will last longer than another.
This type of methodology helps teams work together to solve a specific problem and provide solutions that will be tested with users.
Considerably speeds up decision making and reduces project risk. The purpose is to build a testable prototype with future clients or users. It is also used to test new ideas, a little more risky, solving the challenges of new proposals and design opportunities.
Design Sprint allows you to speed up and simplify the process of designing a product through co-creation workshops.
Thanks to this methodology, concrete and measurable results are obtained, which allow the concept to be validated, since it will be tested with real users. Risks are reduced, unnecessary functionality or features are not developed, and return on investment (ROI) is maximized.
Phases of the Design Sprint
Google defines 6 phases to be carried out in a period of 5 days, 40 hours in its entirety.
0. Understand
It consists of knowing the context and defining the real problem. It is necessary to bring the entire team together and establish the necessary relationships with the Stakeholders.
All participants must know and share the objective and have the same starting information.
It is necessary to generate a shared database for all participants. A small investigation must be carried out, each component providing relevant data about the business, users and customers, competitors and strengths, technical weaknesses, etc.
An ideal team should include representatives from all departments critical to the development of the Sprint.
1. Research and Define
In this phase, the documentation resulting from the investigations must be provided, such as:
In the definition, the whole team must evaluate everything that was learned in the understanding phase to establish the focus. The specific context must be defined and what results are to be achieved with the possible solutions for the problem.
The phase ends by choosing a specific approach, goals, and success metrics for the completion of the Sprint.
2. Sketch
Each of the team members must sketch their own solution to the problem. It consists of working individually on the best solution that solves the problemwithout the solution, opinion or proposal of the rest of the components influencing ours.
They are quick sketches, made on paper, which are made to help convey ideas. The act of performing is because it’s fast and if they need to change things, it doesn’t take long.
3. Decide
In this phase a decision is made about which idea (or ideas) are going to be carried out in the prototype phase. It is necessary to determine how the chosen solutions can generate conflicts with the objectives, clients, users, resources or the business itself.
You must come out of this phase with some that are accepted by all in order to know exactly what is going to be prototyped.
4. Prototype
At this time, ideas and solutions begin to be prototyped. that were decided in the previous phase. , they get down to work to get a High Definition prototype to which the necessary animations will later be introduced so that the basic functionalities that solve the problem can be understood.
You only have one day to complete this task, so at this point things get serious. At the same time that the prototype is made, the research or Research team must specify the schedules for the tests and prepare the schedule to carry out the .
5. Validate
It is the last phase and the most important. Tests with Users are carried out in it. It will be necessary to gather up to a maximum of 20 users and a minimum of 6 to carry out the tests with the prototype.
All test observers must take notes and generate user test logs. The fact of creating records through observation will help to know which parts of the tested prototype need to be improved and which will be the iterations.
After validation, we must generate the necessary to continue with the development phase.
Facebook Comments
Disqus