Sprint by Jake Knapp with John Zeratsky and Braden Kowitz, published by Simon & Schuster in 2016, explains the five-day design sprint the authors ran with startups at Google Ventures. The method takes a team from a big, fuzzy question to a tested prototype in one working week, without writing production code.
What is Sprint about?
Knapp developed the process at Google and refined it with Zeratsky and Kowitz across many sessions with portfolio companies. The problem they set out to fix is familiar to every founder: teams argue for weeks, build what the loudest person wants and learn whether it works only after launch. The book replaces that with a strict schedule and a small team, ideally up to seven people, locked in a room for five days.
The structure follows the week. On Monday the team maps the problem and picks a target moment in the customer’s journey. On Tuesday each person sketches possible solutions on paper, working alone. On Wednesday the team critiques the sketches in silence and the Decider picks a direction. Thursday is for building a realistic prototype, a facade that looks real enough for customers to react to. On Friday five target customers try it in one-on-one interviews while the team watches and notes patterns.
What makes the book stand out is its detail. It specifies times, materials, roles and even snacks, and it explains why each rule exists. Stories from companies the authors worked with, such as Blue Bottle Coffee and the robotics startup Savioke, show the process in action.
What are the main lessons for founders?
- Start at the end. Write the long-term goal and the scariest questions first, then aim the week at answering them. A clear question stops the team from drifting into general brainstorming.
- Work alone, together. Group brainstorming favours confident talkers. Silent individual sketches give quiet team members the same weight.
- Name a Decider. In a young startup this is the founder or CEO. One person with the final call keeps ideas sharp instead of turning them into compromises.
- Fake it to learn it. A clickable mock-up, a brochure or a staged service is enough for a test. Spend one day on it, never a month.
- Five interviews are enough to see patterns. When three or more of five customers stumble at the same point, you have a finding worth acting on.
Who should read Sprint?
It suits startup teams of four to seven people with a high-stakes question: a new product, a new market, a redesign or a pricing page. Product managers, designers and agency teams use it to make workshops shorter and decisions faster. Founders who struggle to get a team to agree will value the clear roles and rules.
Solo founders and very early teams can skip most of it, or borrow only the sketching and testing days. The full method needs several people free for a whole week.
How do you put Sprint to work this week?
- Write your biggest open product question as a single sentence, plus the long-term goal it serves.
- Block one day with your team to map the customer journey and sketch solutions alone, then pick one with a Decider.
- Build a one-day prototype in slides or a no-code tool and book five customer interviews for the following day.
If the prototype is a sign-up or sales page, the free Landing Page module in the F/MS Startup School shows what to put on it.
Where does Sprint fall short?
The method assumes a team that can drop everything for five days, which few early startups can afford. Friday’s interviews measure how people react to a prototype, so the test says little about whether they will pay or come back next month. The examples come from well-funded companies backed by Google Ventures, and the book spends little time on what to do when the answer is unclear. To test demand with real money or behaviour, pair it with The Right It or Testing Business Ideas.