The archive · Work & Ways of Doing · Product decision · 2010–2016
GV's Design Sprint compresses a product decision into five days — prototype tested Friday
The Design Sprint packs a product's key questions into five days: map, sketch, decide, prototype, test with real customers — before any expensive build.
Google Ventures
What it had to solve
Startups funded by Google Ventures kept spending months debating ideas and building the wrong things. GV design partner Jake Knapp wanted a way to answer critical business questions and get customer feedback in days, not quarters.
How it works
In 2010, Google design partner Jake Knapp began running 'design sprints' with internal teams such as Chrome, Google Search and Google X. The idea: instead of months of debate, compress a product's most critical questions into a single structured week and end with a prototype tested by real customers.
In 2012 Knapp brought the sprint to Google Ventures, where John Zeratsky, Braden Kowitz, Michael Margolis and Daniel Burka refined it. Monday the team maps the problem and picks a target; Tuesday everyone sketches competing solutions; Wednesday they decide and turn the best ideas into a testable hypothesis; Thursday they build a high-fidelity prototype with a 'fake it' philosophy; Friday they test it with real customers and watch what happens.
The point was learning without launching: 'Instead of waiting to launch a minimal product to understand if an idea is any good, you'll get clear data from a realistic prototype,' GV's own guide explains. Sprints ran with portfolio companies like Nest, Flatiron Health and Medium to enter new markets, design products and develop features.
GV published a formal DIY guide in 2015 and announced the method as a book; 'Sprint' became a New York Times best seller in 2016. Teams around the world adopted the process, and GV began collecting their stories on SprintStories.com.
Why it lands
- A fixed five-day deadline forces decisions that open-ended brainstorming never reaches.
- Building a realistic prototype beats debating abstractions, because customers react to the thing, not the idea.
- Ending with real customer interviews turns opinions into observations everyone can accept.
- The structured day-by-day agenda made the process teachable, packageable and repeatable.
- Publishing it openly let the method spread far beyond GV's portfolio.
What it did
GV ran sprints with portfolio companies including Nest, Flatiron Health and Medium; the method spread beyond startups to teams worldwide, with a DIY guide, a SprintStories community and a New York Times best-selling book making the five-day process a standard product practice.
What you can take
Prototype-and-test beats debate: a hard five-day deadline forces teams to choose, build a realistic fake, and learn from real customers before spending on development.
Since then
The Design Sprint became a standard product practice: companies of all sizes ran the five-day format, agencies and schools taught it, and the book remained a reference for product teams. GV kept using sprints with its startups and collected adoption stories from teams around the world at SprintStories.com. The process also seeded related methods — sprint weeks inside organizations, design-sprint workshops and an open Design Sprint Kit — cementing 'test before you build' as a default way to make product decisions.
Sources
- The Design Sprint — GV
- Google Ventures releases new DIY guide to help startups design better products
spotted an error? The archive wants to know.
Your turn
You just read one. Describe the brief you are staring at, and see who has been given the same problem.
Free account · 3 free questions · no card