Design Sprints
Design Sprints are an incredibly efficient way to test ideas and validate assumptions in a single week. The feedback and insights generated from these sprints are the foundation for successful products.
Devin, Alex, Mike, and Ellie generating ideas for an internal Yeti design sprint
What happens in a design sprint?
Pre-Sprint
For a Design Sprint to be successful, there must be a concise problem statement, an identified user persona, a clear understanding of the competitive landscape, and well-defined metrics for success.
Day 1: Understand
On the first day we revisit the work from the strategy workshop and choose a target challenge based on your riskiest assumption.
Day 2: Generate
With all stakeholders participating, we’ll sketch possible solutions for our challenge, considering it from every angle.
Day 3: Decide
After reviewing the previous day’s work, the product owner will decide which solutions we will prototype and test.
Day 4: Prototype
The design team works to rapidly prototype an interactive version of the chosen solutions that will be tested with users.
Day 5: Test
Having pre-identified users is critical. For testing, we’ll bring five potential customers to test our prototypes while gathering vital feedback.
Design Sprints can conclude in several ways. Most likely some ideas will resonate with users and others won’t, regardless we know what to take into production and what to take back to the drawing board. After we have validated your riskiest assumptions, we’ll define an MVP and product roadmap and we can begin working in agile Build Sprints!
Learn more about design sprints
For more information on Design Sprints have a look at some of these resources:
