Inventor of the Design Sprint, ex-Google Ventures
Jake Knapp created the design sprint at Google after a week of prototyping in Stockholm produced what became Google Meet. He later co-founded the venture firm Character Capital and co-wrote Click, a book on a two-day sprint. Across the sprints he has run, the common element in the big successes is differentiation, worked out from the customer's view at the very start of a project.
Lenny's Podcast 01:09 01:31 06:55 07:01 07:46 08:58 1:12:28 Greg Isenberg 42:37
Shipping
Pick one Highlight a day, not a longer to-do list. Getting faster at the inbox only refills it, so name what the day is for and defend one block.
most people struggle with productivity because they focus on 'getting through' their inbox and meetings
Jake Knapp
puts a floor under the Highlight at roughly an hour, on the logic that anything smaller cannot anchor a day, and caps the day at one.
argues the opposite direction: shrink the behavior until it takes under 30 seconds and needs almost no motivation, then let it grow.
From Make Time
Lenny's Podcast
Greg Isenberg
Lenny's Podcast
The Design Sprint
A five-day structured process to go from undefined problem to customer-tested prototype, replacing months of debate with compressed, focused execution.
Crazy Eights Rapid Ideation
An eight-minute sketching exercise where each person folds a sheet of paper into eight panels and draws eight variations of their best idea, one per minute, to push past…
Sticky Decision Method
A five-step structured decision process that replaces open debate with silent evaluation, crowd wisdom, and a clear Decider's final call to select winning solutions.
Time-box every phase of creative work. Five days is enough to go from problem to tested solution if you enforce strict daily boundaries.
When teams face open-ended product challenges that could drag on for weeks or months without resolution.
Always have a single Decider with final authority. Democratic consensus produces watered-down compromises, not bold solutions.
When a cross-functional team must choose between competing solution sketches and no one wants to overrule others.
Test with real customers on Friday, not internal stakeholders. Five target customers reveal major patterns without statistical overhead.
When validating a prototype and the team is tempted to rely on internal opinions or wait for large sample sizes.
If you can prototype it, do not debate it. A testable artifact resolves more arguments in one afternoon than weeks of meetings.
When a team is going back and forth on whether an idea will work and discussion is circular.
Five customers is enough. After five one-on-one tests, you will see the major patterns. Waiting for more data is usually procrastination disguised as rigor.
When deciding how many users to recruit for prototype testing or usability sessions.
If you can pull to refresh, it is an Infinity Pool. Treat it as a controlled substance: schedule access windows, do not leave it open.
When evaluating which apps and services are draining your attention and need friction added.
Compress learning cycles ruthlessly. Five days to go from problem to tested solution is not reckless speed; it is disciplined elimination of waste.
Most product development time is spent in meetings, debates, and waiting for decisions, not in actual creation or learning. The sprint structure eliminates the waste and…
Default settings are the enemy. Both your calendar and your phone are configured by others to steal your time. You must actively redesign your defaults.
Tech companies optimize for engagement (Infinity Pools) and workplace culture optimizes for busyness (Busy Bandwagon). Neither optimizes for your meaningful output.…
Prototypes are disposable hypotheses, not investments to protect. Build only enough to learn, then throw it away without regret.
When teams invest significant effort in a prototype, sunk cost fallacy makes them reluctant to discard it even when testing reveals problems. Keeping prototypes…
