If You Buy It, We'll Build It - Combining Design Sprints & Pretotypes
summary
Combines Google Design Sprint steps with Alberto Savoia pretotyping methods to get buying signals before building, claiming prototypes should cost near zero and be testable in 24 hours and reminding that 80% failure needs mitigation. Uses Miro, lean canvas, lightning demos, sketches, and pretotype types like fake door and one‑night stand or Pinocchio wooden mocks to collect real behavior data not opinions. Requires a facilitator, a decider, experts and diverse team, and aims to deliver tight tests that produce go/no‑go decisions (example threshold shown: 5% conversion).
AI-written summary · about
chapters (24)
- 0:00Start
- 0:09Introduction
- 6:54How To Place the Right Bets on the Right Ideas
- 8:27Design Sprints
- 9:55Who Do You Have To Need To Have in the Room for a Design Sprint
- 17:09How Is Mvp Different
- 19:35Working Together but Working Alone
- 21:19Design Sprint Structure
- 22:10Alberto Savoya
- 23:10The Design Sprint Map
- 26:58Team Roles
- 28:46Design Sprint Map
- 32:47Does It Work for Software Implementation
- 42:18Three Factors Causing Traffic Jams Saturation Construction and Accidents
- 45:26Sprint Questions
- 57:07Crazy Eights
- 59:17Prototyping
- 1:06:11Facade
- 1:06:53Pinocchio
- 1:07:20Mechanical Turk
- 1:12:39Lean Canvas
- 1:13:08Link Canvas
- 1:18:04Final Questions
- 1:20:08Sprint Map
