A product design sprint is a technique to quickly solve product design problems
and test the viability of a solution. It was pioneered by Jake Knapp and
the Google Ventures Design Team.
We've been running design sprints for over 10 years. Over that time we've built
up a bigger and bigger list of things that we know about design sprints. We've
collected everything into our Design Sprint Guide.
Each sprint should be tailored to the individual project. Our guide serves as a
repository of sprint schedules, exercises, and resources that can be used to
create the ideal sprint for each project.
Why do a design sprint?
A design sprint orients the team and aims our efforts toward a mutual goal. It
allows us to invest our time and money wisely by eliminating inherent risk in
building products by shortening the product design feedback loop with real
world data as a focused group.
Sprints are most useful when kicking off a new business, product, feature, or
What should you expect to have at the end of a design sprint?
At the end of the sprint, the team should have a shared understanding of the
problem and have tested assumptions with a prototype. After testing, the team
should decide on and document next steps for the product.
That could mean:
- Rolling into product design and development
- Taking learning from the testing and starting a new Design Sprint
- Deciding not to move forward with the product