Keep these 28 tips handy
Thank you for downloading our guide to the worst Design Sprint goof-ups!Your file is on its way to your email address.
If you're facilitating a Design Sprint, this guide is for you. That includes external sprint facilitators (like us) who run sprints for other teams, or people who want to organise a sprint for their own organisation.
This guide is organised by the original five-day Design Sprint 1.0 schedule, but everything also applies to the four-day Design Sprint 2.0 process. The key difference is that voting on a solution and storyboarding happens on Tuesday with the 2.0 schedule and Wednesday with the 1.0 schedule.
You probably already know this, since you're about to start a Design Sprint? (Riiiight? 🤨)
A Design Sprint is a five-day process where a diverse team works together to understand, prototype and test their solution for a big business problem. If the solution is a winner, it goes straight into product development.
The Design Sprint framework helps teams quickly identify the right problems to solve and test their solution through rapid prototyping and user feedback. Within a week, teams can move from an abstract idea to a high-fidelity prototype tested with real users. It's efficient, quick and easy on the budget.
Looking for more information?
Check out Google Venture's guide to the Design Sprint framework