Design sprint

UX & design method

Focusing effort on a design problem in 5 days

The design sprint is a short, framed format for tackling a design problem in one week. In five days, a team moves from the problem to a prototype tested with real users. Theorised by Jake Knapp with John Zeratsky and Braden Kowitz at Google Ventures, it was published in the book Sprint in 2016.

The design sprint is a format, not a method. It offers, over 5 days, an accelerated version of the steps drawn from design thinking. Spoiler alert: it's no magic recipe either!

What is a design sprint for?

  • Building team cohesion
  • Providing structure and pace, with concrete goals at the end of each day
  • Involving participants in the project
  • Producing a testable outcome

Why run a design sprint?

  • Tackling a pre-identified problem within a limited time
  • Focusing a team's effort on one specific problem to try and find suitable solutions
  • Clarifying the key aspects of a topic
  • Informing the thinking behind an MVP

Typical design sprint schedule

01

Day 1: define the problems to solve, set a goal, exchange and take notes, generate How Might We questions with experts around a customer journey to pin down the target and the experience step to address

02

Day 2: competitive review and lightning presentations, individual sketching and user recruitment in parallel for Friday

03

Day 3: pick the best ideas and build a storyboard

04

Day 4: split tasks, build the prototype and prepare the user tests

05

Day 5: user testing and trend analysis, closing the sprint with an immediate debrief alongside the participants

In practice

Depending on availability or appetite, the 5 days set by the format are sometimes spread over several weeks, or even condensed into four days. A typical design sprint runs as follows:

Day 1: define the problems to solve, set a goal, exchange and take notes, generate How Might We questions with experts around a customer journey to pin down the target and the experience step to address.

Day 2: competitive review and lightning presentations, individual sketching and user recruitment in parallel for Friday.

Day 3: pick the best ideas and build a storyboard.

Day 4: split tasks, build the prototype and prepare the user tests.

Day 5: user testing and trend analysis, closing the sprint with an immediate debrief alongside the participants.

Frequently asked questions

A few of our case studies

Co-design

Drawing on collective intelligence, these workshops align stakeholders and surface solutions with the team and/or the end users.

Read more about Co-design

Prototype

More or less advanced animation of the screens to present a dynamic journey to users and gather feedback.

Read more about Prototype

User testing

User testing has target users assess the usability of your product or service. Depending on the goals, several approaches exist.

Read more about User testing

Storyboard

A storyboard illustrates a usage scenario in context. It is a UX tool for exploring a service idea or specifying the sequence of interactions.

Read more about Storyboard

Design thinking

An innovation-management method built on 5 pillars that make for a useful thinking framework. A heads-up: it's no magic recipe.

Read more about Design thinking

Sketching

Sketching is a technique for creating interfaces as drawings, most often by hand. It is often used in co-design workshops.

Read more about Sketching

Curious to learn more about us?

Everyone talks about user experience, service design, ergonomics...
It's not always clear, and you'd like to find out, or sharpen what you already know.

Let's talk