Introduction · Page 8
Not the only method: the design sprint
For you only
I love design sprints. I am not in opposition to them. The design sprint was announced with the book in 2016, the method goes back to around 2010 at Google, and it gave a whole industry a shared way to work. Jake Knapp, John Zeratsky, and Braden Kowitz built something serious, and this book borrows from it openly: the decider in the room, the real user settling the call, the timeboxes.
It also takes four to five days, and it is hard to get a full team and their leadership to commit to a week. The bigger thing is what changed underneath both methods: when the sprint was designed, building a realistic prototype was slow and specialised, so the sprint's Thursday openly builds a facade, screens that look real from the front like an Old West movie set. Now the build is fast and open to anyone. A one-day format can do what used to need a week, because the build is no longer the expensive step.
| Design sprint | Product Build Day | |
|---|---|---|
| Length | 4 to 5 days (shorter variants exist) | 1 day, sometimes 2 |
| Core activity | Map, sketch, decide, prototype, test | Build working prototypes with AI, test, decide |
| Who builds | Usually one designer builds one prototype | Everyone builds, up to four teams |
| The prototype | Often a facade, not a real product | A real working thing, vibe-coded |
| Output | One tested prototype | Up to four tested prototypes plus a decision |
| The decision | Reported after, aligned later | Made in the room, same day |
| Commitment | A full team for most of a week | One day, and one hour from leadership |
| Best for | A big, ambiguous bet worth a week | A fast call on what is worth building now |
One more thing the two methods share. This is wartime, not peacetime. A normal week is democracy, lots of opinions, slow consensus. A build day is closer to a benevolent dictatorship for one day: one person owns the challenge, sets it, and the users settle the rest. That is a feature, not a flaw. It is why the day ends in a decision instead of a follow-up meeting.