Design Sprint

Overview

The focus of a Design Sprint, as developed by Jack Knapp, John Zeratsky and Braden Kowitz, is on the need for a structured, time-boxed approach to problem-solving that fosters collaboration and creativity while delivering tangible results in just five days. The attention is on innovation and problem-solving within a tight timeframe.

Sprint refers here to a short, intensive burst of activity aimed at accomplishing a lot in a limited time, much like a runner dashing towards a finishing line. This term fits the five-day process of quickly moving from a problem to a tested prototype.

Day 1: Understand

Day 1 is all about understanding the problem and setting a clear goal for the week. The team gathers to discuss the challenge, map out the problem space, and decide on a specific target. This day includes:

• Gathering insights: Understanding the background and context of the problem.
• Mapping: Creating a simple map of the problem area.
• Setting a long-term goal: Determining what success looks like.
• Identifying obstacles: Listing potential roadblocks.
• Choosing a target: Focusing on the most critical aspect of the problem to tackle during the sprint.

The aim is to align everyone on the team and ensure they have a shared understanding of the problem and the goals for the sprint.

Day 2: Sketch

Day 2 of the sprint is about diverging and converging ideas. It’s time for the team to come up with a broad range of solutions and then narrow them down to the best ones. Key activities include:

• Lightning Demos: Team members present inspiring ideas and existing solutions from various sources to spark creativity.
• Sketching Solutions: Each team member independently sketches detailed solutions based on the insights from Day 1.
• Crazy 8s: A fast-paced exercise where each person sketches eight different ideas in eight minutes.
• Solution Sketches: Everyone creates a more refined and detailed sketch of their best idea, focusing on clarity and completeness.

The goal of Day 2 is to generate as many solutions as possible and prepare to make informed decisions about which ones to pursue.

Day 3: Decide

On Day 3, the team focuses on making decisions. Here’s the breakdown:

• Art Museum: Everyone’s solution sketches from Day 2 are displayed side-by-side on the wall like an art gallery.
• Heat Map: Team members silently vote on the parts of sketches they like best by placing dot stickers next to the most compelling elements.
• Speed Critique: A structured discussion where the team reviews each sketch, focusing on the highlighted parts.
• Straw Poll and Super Vote: After the critique, team members vote on their favorite solution using a quick poll. The Decider, usually the project leader, then makes the final call with a “Super Vote.”
• Storyboard: The chosen solution(s) are transformed into a detailed storyboard, which outlines the prototype that will be built on Day 4.

Day 3 is all about converging on the best ideas and preparing to bring them to life.

Day 4: Prototype

Day 4 is all about prototyping. Here’s the drill:

• Prototype Building: The team creates a high-fidelity prototype based on the storyboard developed on Day 3. This prototype should be realistic enough to get genuine reactions from users, but efficient enough to be completed in a day.
• Assign Roles: Team members are assigned specific roles to streamline the process, such as making sure the prototype is cohesive and consistent.
• Tool Selection: The team chooses the tools and materials needed to build the prototype, focusing on speed and functionality.

The goal for Day 4 is to build a prototype that looks and feels real enough to gather meaningful feedback during testing on Day 5.

Day 5: Test

Day 5 is all about testing. Here’s the game plan:

• User Interviews: The team conducts one-on-one interviews with real users, observing their interactions with the prototype and gathering their feedback.
• Note-taking: Each team member takes detailed notes on user reactions, focusing on what works well and what doesn’t.
• Debriefing: After the interviews, the team reviews the feedback, identifies patterns, and discusses key insights.
• Decisions: Based on the user feedback, the team decides on the next steps, which could involve refining the prototype, pivoting to a new idea, or even planning a follow-up sprint.

The goal for Day 5 is to validate the prototype with real users, learning what needs improvement and what can move forward. It’s the ultimate test to ensure the solution is on the right track.