Sprint
by Jake Knapp, John Zeratsky & Braden Kowitz
A five-day recipe for killing bad ideas cheaply — useful, padded, and worth skimming.
- Status
- Read · August 2017
- Bought
- August 23, 2017
- For
- Product engineers who hate building the wrong thing · Solo builders and small teams deciding what to prototype next · Anyone who runs design or planning workshops
Where it earned its place
The one-paragraph verdict
The core loop — map the problem, sketch in silence, let one decider pick, storyboard, prototype, test on five users — is genuinely good engineering discipline applied to product decisions. Knapp’s strongest move is forcing convergence: no design-by-committee, no endless debate, a single decider breaks ties. The recurring criticism is fair, though. It’s a long magazine article stretched to book length, padded with Google Ventures war stories, and it assumes you can clear five people’s calendars for a full week with a trained facilitator — a luxury most teams don’t have. I read it for the skeleton and ignored the padding. [Sprint on Goodreads]
Who should read it
Read it if you keep shipping features nobody wanted and need a cheaper way to be wrong. Product engineers, small teams, and anyone facilitating workshops will get the most out of it. Skip it if you already run lean discovery cycles — you’ve internalized this and the book will feel slow.
Where it earned its place
The compress-and-test instinct showed up directly in my self-optimizing design loop: generate a prototype, put it in front of a critic fast, converge on one direction instead of debating variants. The Sprint method just swaps five humans for a tighter feedback loop.
Skip it if…
You want depth on why the rituals work, not just the playbook. It’s prescriptive, not analytical — borrow the structure, don’t expect theory.