Sprint
How to Solve Big Problems and Test New Ideas in Just Five Days
Jake Knapp, John Zeratsky, and Braden Kowitz · 2016 · Business
14 min · 13 chaptersNarrated in your voice
What it's about
Sprint argues that most companies waste months debating ideas that could be tested in a week. Drawing on the authors' experience running over a hundred design sprints at Google Ventures, the book lays out a five-day process—map, sketch, decide, prototype, test—that forces a small team to convert a vague, risky bet into a real customer reaction. It mattered because it gave startups and corporations alike a repeatable alternative to endless meetings and speculative roadmaps.
Read a little every day
15 min a day
1 days · done Sat, Oct 31
Read together
Start a circle and share the code — everyone sees everyone's honest place in the book. Accountability, not leaderboards.
Who it's for
- A startup founder about to spend six months building a feature no one has asked for - A product manager tired of meetings that produce opinions but no decisions - A team lead who wants a structured alternative to open-ended brainstorming
What’s inside
- 1Why Teams Waste Time Building the Wrong Thing1 min
Most product failures trace back to teams debating opinions for months instead of testing the one assumption that actually matters.
- 2The Origin and Logic of the Design Sprint1 min
Squeezing months of work into one calendar week works because it removes the escape valves that let teams delay hard decisions indefinitely.
- 3Choosing the Right Problem and Assembling the Team1 min
A sprint is wasted on routine decisions; it only pays off when the stakes are high, the direction is genuinely unclear, and time is short before a costly commitment.
- 4Monday: Mapping the Problem and Picking a Target1 min
Teams overestimate how well they understand their own problem, and drawing a simple map of the customer's journey before generating any solutions prevents the week from solving the wrong thing.
- 5Tuesday: Solitary Sketching Beats Group Brainstorming1 min
Group brainstorming produces worse ideas than individual, silent sketching because whiteboard sessions reward the loudest or most senior voice rather than the best solution.
- 6Wednesday: Deciding Without True Consensus1 min
Waiting for full team agreement on a direction is a slower and often worse method than a structured critique followed by a designated Decider making the final call.
- 7Thursday: Building a Prototype Just Real Enough to Test1 min
A sprint prototype should be built to look convincing for a few minutes under interview conditions, not to function—treating it as more real than that wastes the week's only truly scarce resource.
- 8Friday: Five Interviews Reveal the Truth1 min
Interviewing five target customers one at a time uncovers nearly all the major problems with a concept, making it unnecessary and often misleading to wait for larger-scale quantitative testing at this stage.
- 9Why the Constraints Are the Method1 min
The sprint's real innovation is not any single exercise but the deliberate stacking of hard constraints—one week, one room, one Decider, seven people—that forces clarity no individual technique could achieve alone.
- 10Where Sprint Runs Thin1 min
The book's evidence is a curated set of Google Ventures success stories, not a controlled study, so it understates how much the method depends on conditions—a willing Decider, a real budget, a narrow well-chosen question—that many organizations lacking VC-style leverage cannot reliably arrange.
About Jake Knapp, John Zeratsky, and Braden Kowitz
Jake Knapp created the design sprint while at Google and refined it as a design partner at Google Ventures. John Zeratsky and Braden Kowitz were also GV design partners who ran sprints with hundreds of startups, from Slack to Blue Bottle Coffee, before co-writing the book from that shared casework.
