- The sprint gives product teams a shortcut to figuring out whether a concept could work without building and launching it.
- Working from problem definition all the way through to usability testing, the sprint is typically a five-day process for answering critical business questions through design, prototyping, and testing ideas with customers.
- Developed at Google Ventures, it’s a “greatest hits” of business strategy, innovation, behavior science, design thinking, and more — packaged into a battle-tested process that any team can use.
Typically, we launch a minimum viable product (MVP) and wait for feedback – a process which can take months. A design sprint provides you with clear feedback in under a week to bypass the endless debate cycle.
Who are we designing for and what are the assumptions we have about their needs, goals, motivations and behaviours?
- Discuss what you know already about your customers and present any research.
- Define your customer, their needs and goals, using personas and “how might we…” problem statements.
Tuesday: Testing venue
How do we transition from identifying problems to creating solutions?
- Be inspired by exploring current ideas that relate even tangentially to your concept. How can we remix and improve on these?
- Learn to harness divergent thinking by finding ways to come up with as many ideas as possible, even if they’re not perfect.
How to make difficult decisions around your concept and turn your best ideas into a testable hypothesis?
- Critique your stack of solutions
- Weave the winning solutions into a plan for the first iteration of the prototype
How do we create the prototype so it’s ready for testing?
- Hammer out a low to medium fidelity prototype using paper and pens, or something more interactive such as Axure.
How do we obtain valuable feedback from actual users?
- Put the prototype in front of actual customers and receive their feedback
- Understand whether your concept has viability
- Dig deeper to uncover root problems
- Discover alternative solutions