Accelerate innovation and make decisions based on user feedback: how the Design Sprint can reduce the time to design and validate solutions.
The Design Sprint is a collaborative design process developed and popularized by designer Jake Knapp, along with John Zeratsky and Braden Kowitz. The process was developed within Google Venture to rapidly test and validate ideas and solutions, through co-design, prototyping and user-testing techniques.
The goal of the Design Sprint is to obtain tangible results in a much shorter time frame than traditional approaches, accelerating the processes of interaction, prototyping and validation, and allowing the team to make decisions based on user feedback.
The Sprint is an ideal tool for developing and testing solutions that would usually take months (or years): the ideas and solutions implemented through the Sprint during testing can “fail”; but even from bankruptcy it is possible to receive many indications on how to proceed with the development of the project, in a few days, without major economic and time investments.
Design Sprint was born to develop digital projects and services, but today it is used in very different contexts.
The Design Sprint, developed from the Design Thinking philosophy, consists of 5 key phases:
Traditionally months of work are required to develop a project following these phases, but the goal of the Design Sprint is to condense them into one week of intense work. Below is an example of the execution of a Design Sprint.
Define the long-term goals of the project
Fundamental to define the priorities and objectives of the company
Mapping the “challenge”
Define the user-flow of the users involved in using the product or service.
“Nobody know everything”
Each participant shares their knowledge related to the various areas of the project and the other team members have the opportunity to ask questions and take notes.
Define the problems and choose a target
At the end of the day, the issues to be addressed are identified and the final target of the sprint is chosen.
Existing ideas and solutions from competitors and in alternative markets are shared and analysed, from which to draw inspiration.
Through guided techniques, each team member represents his ideas and solutions.
The objective of the 3rd day is to choose which solution(s) will be prototyped, through the analysis and discussion of the ideas developed the previous day.
The whole team is involved in the choice, but the final decision rests with a Decider (appointed before the Sprint).
Using the winning ideas, a storyboard is created which will be the basis for generating the prototype.
Starting from the storyboard, a prototype of the project/service is developed.
Learn by customer
Even the best idea has to collide with reality: the prototype is tested with a limited number of people (5-6) in the presence of a moderator.
From a separate room, the rest of the team observes the tests in real time and takes notes. At the end of the tests, the notes are shared to identify positive and negative patterns and draw conclusions.
Throughout the entire process, the team works collaboratively, adopting an open mind and experimenting with solutions without setting limits. These phases guide the team through a structured and focused process to obtain rapid and validated results, providing a solid basis for future decisions on product design and development.
The Design Sprint is all about co-design, and choosing who to include on the team is critical.
The team must be composed of 5-8 components, with heterogeneous roles. Stakeholder participation in the Design Sprint is critical to its success.
Stakeholders are individuals or groups interested in or affected by the project outcome and can include executives, end users, industry experts, and other key members of the organization. Involving stakeholders in the Design Sprint allows for a more complete and diversified view of the problem to be addressed, leading to more effective and adoptable solutions.
Their participation helps to better understand user needs, business challenges, technical restrictions and other critical factors. Furthermore, involving stakeholders in the ideation, prototyping and testing process allows them to actively contribute, providing valuable feedback and suggestions that will influence the final result. The goal is to create a collaborative environment where different perspectives can be integrated, enabling more informed decision making and smoother implementation of solutions.
Priorities, problems and possible solutions are defined through the Sprint; probably not all the questions will be answered, but surely great progress will be made, thanks to the successes – but also failures – of the tests.
The Sprint is not the end of a process, but the beginning.