“The design sprint was very interesting, effective and enjoyable. I believe we managed to reach valuable ideas by deepening the team’s understanding of the problems and putting our minds together for the solutions. I think we all benefited from this event, as individuals and as a team (or teams).”
“This was A productive and fun day. Everyone that attended, said they really enjoyed the process, the option of being a part of the thinking process and the general atmosphere. There is a consensus we need more sessions like these and with additional team members.”
The cost of a design sprint facilitation depends on the preparations needed, the number of days if we do a follow-up Sprint or not, and a few logistics aspects. You can get a tailor-made assessment when you contact us here.
You'll be able to compress months of product development simply by gathering ideas of potential solutions, creating a high-fidelity interactive prototype, validating it with real users, and saving a potentially enormous amount of resources. You'll also get your teammates in line with the product challenge, and use a team effort using a fun, creative, and engaging method.
There are several opportunities when you can run a Design Sprint - When you have a big challenge, but not too big, when you have limited resources, when you have a strong conflict, when there’s a lack of creativity, and when you want to engage your team. For more detailed answer, you can read my article The right opportunity for a Design Sprint on UX planet.
Usually, the recommendation is to have 5-8 team participants in a Design Sprint from a different disciplines (product, development, design, marketing, and etc) and at least one stakeholder. In case there are more than 8 participants, we can switch into groups of 5-8 team members each.
When running a Sprint, the challenge should be neither too narrow nor too broad. You shouldn’t run a Sprint to determine where to put a button or to solve the world’s climate change (you still have only one week). However, it’s very important that your challenge will be well defined. Not too specific, but rather a generalization; in case there’s a challenge of figuring out how people will interact with a product and study their behavior, or in case you are working on a new feature and you want to check the value that it gives to your users, or in case you want to increase the usage of an existing functionality — that’s where you should put up a Sprint together. Here are a few examples of Design Sprint challenges: "How can we raise users' awareness of an existing feature in the app and improve its conversion rate?"; "How can we make the information accessible on our dashboard screen and adapt it to our users' needs?"; "How can we engage users to subscribe to our platform to increase our subscriptions?" You can explore more case studies on Sprint Stories.
There are a few success metrics - The important of all is you've successfully validated a prototype that you've created as a team. however, many Design Sprints were just a trigger to work using a method, gathered your team, or working in synergy.
For a successful Desing Sprint there are a few preparations that need to be done. We'll need to define the specific challenge we would like to solve using a detailed brief, the participant will be asked to prepare 5-minute brief pitches that explain their perspective of the challenge, we'll need to plan the logistics, like finding the right space for the workshop, arrange the equipment needed, create the agenda, scheduling with users, and more. You can read my article on Google Developers Experts blog for more details.