Design Sprint

A design sprint is a five-day process for solving big product problems through ideation, rapid prototyping, and real-user testing in a single compressed week. It was developed at Google Ventures by Jake Knapp and is designed to bypass the usual months of debate and produce a validated direction before the company commits to building. It was popularized through Knapp's book Sprint (2016, co-authored with John Zeratsky and Braden Kowitz) and became one of the most-adopted structured product processes in the late 2010s.

The classical five-day schedule: Monday, understand (map the problem, interview experts, choose a focus area), Tuesday, sketch (each participant generates solutions individually, leading to a detailed solution sketch), Wednesday, decide (the team selects which sketches to prototype using structured voting; the decision sits with a designated "Decider," usually the founder or product lead), Thursday, prototype (build a realistic clickable prototype of the chosen solution; the cardinal rule is "facade, not foundation"), Friday, test (five user interviews, each watching a real user attempt to use the prototype, with the team observing live in another room). Famous examples of design sprints producing useful outcomes: Slack's onboarding flow (a 2014 sprint at GV-backed Blue Bottle Coffee and others), Savioke's hotel robot customer experience. The 2020s evolution: the original five-day format gets compressed (3 or 4-day variants) or remote-adapted, and many teams have moved away from running formal sprints at all in favor of continuous discovery practices (Teresa Torres) that spread the same activities across weekly rhythm rather than concentrating them. The honest critique: design sprints work well for genuinely big, undefined problems with a decision-maker present and time-boxed urgency; they are overkill for routine feature design and a waste when the team is missing the customer research or decision authority that the sprint depends on.

What founders get wrong: Running design sprints without a clear Decider in the room. The structure depends on someone with authority making the call on Wednesday; without that, the team builds whatever the loudest voice wants and Friday's user tests resolve nothing. If the founder can't commit to being in the room all week, the sprint will produce expensive output and zero alignment.

Related: Design Thinking · Prototype · Product Discovery · Usability Testing · User Research

FAQ

What is a design sprint?
A five-day structured process developed at Google Ventures by Jake Knapp for solving big product problems through ideation, prototyping, and real-user testing in a single compressed week. Designed to bypass months of debate and produce a validated direction before the company commits to building. Popularized in the 2016 book Sprint.

What is the five-day design sprint schedule?
Monday: understand and map the problem. Tuesday: sketch solutions individually. Wednesday: decide which sketches to prototype (with a designated Decider). Thursday: prototype the chosen solution. Friday: test the prototype with five real users while the team observes live.

When should a team NOT run a design sprint?
For routine feature design (overkill), when the customer research or decision authority needed isn't available (the structure depends on both), or when the team is already practicing continuous discovery (Teresa Torres style), which spreads similar activities across weekly rhythm rather than concentrating them.