Product Design
Sprint
by Jake Knapp, John Zeratsky, and Braden Kowitz
Sprint summary
Sprint by Jake Knapp, John Zeratsky, and Braden Kowitz is a product design book built around a clear concern: A five-day design process for choosing a challenge, sketching alternatives, deciding, prototyping, and testing with users before expensive implementation. Its major ideas include Map and target, Sketch independently, Decide, Storyboard. The useful reading is to connect these concepts into a way of diagnosing decisions, behavior, or systems rather than treating them as isolated tips. Examples can illustrate a mechanism without proving universal causality, so the Booknomics approach asks where the principle matters, what evidence supports it, what trade-offs it creates, and what would make a reader revise it. The result is a practical but skeptical reading that treats the book as a set of hypotheses to test against real constraints.
Detailed summary
Sprint — Premium Deep Summary
Overview
Sprint by Jake Knapp, John Zeratsky, and Braden Kowitz is a product design book built around a clear concern: A five-day design process for choosing a challenge, sketching alternatives, deciding, prototyping, and testing with users before expensive implementation. Its major ideas include Map and target, Sketch independently, Decide, Storyboard. The useful reading is to connect these concepts into a way of diagnosing decisions, behavior, or systems rather than treating them as isolated tips. Examples can illustrate a mechanism without proving universal causality, so the Booknomics approach asks where the principle matters, what evidence supports it, what trade-offs it creates, and what would make a reader revise it. The result is a practical but skeptical reading that treats the book as a set of hypotheses to test against real constraints. The durable takeaway is a cycle of noticing, testing, observing, and revising instead of turning an appealing principle into a rigid rule.
Critical synthesis
What Sprint is trying to explain
Jake Knapp, John Zeratsky, and Braden Kowitz's central project can be stated plainly: A five-day design process for choosing a challenge, sketching alternatives, deciding, prototyping, and testing with users before expensive implementation. A strong analysis must connect the book's ideas rather than merely collect advice. The reader needs to see the problem, the proposed mechanisms, how the ideas interact, where they guide action, and where they become weaker.
1. Map and target
In Sprint, Map and target is part of the larger attempt to explain a five-day design process for choosing a challenge, sketching alternatives, deciding, prototyping, and testing with users before expensive implementation. Its importance is not the label itself but the change in attention it produces. A reader can ask what evidence would show this mechanism operating, what alternative explanation fits the same facts, and what behavior would change if the idea were taken seriously.
The analytical value of Map and target is that it turns an abstract concern into something observable. Inspect choices, constraints, incentives, timing, feedback, and consequences rather than relying on intention alone. This prevents the concept from becoming a slogan while preserving the practical insight Jake Knapp, John Zeratsky, and Braden Kowitz is trying to communicate.
There is also a boundary condition. The same principle may work differently for an individual, a team, a market, or an institution. For practice, define one live situation, change one variable suggested by Map and target, and decide in advance what outcome would count as improvement or disconfirmation.
2. Sketch independently
In Sprint, Sketch independently is part of the larger attempt to explain a five-day design process for choosing a challenge, sketching alternatives, deciding, prototyping, and testing with users before expensive implementation. Its importance is not the label itself but the change in attention it produces. A reader can ask what evidence would show this mechanism operating, what alternative explanation fits the same facts, and what behavior would change if the idea were taken seriously.
The analytical value of Sketch independently is that it turns an abstract concern into something observable. Inspect choices, constraints, incentives, timing, feedback, and consequences rather than relying on intention alone. This prevents the concept from becoming a slogan while preserving the practical insight Jake Knapp, John Zeratsky, and Braden Kowitz is trying to communicate.
There is also a boundary condition. The same principle may work differently for an individual, a team, a market, or an institution. For practice, define one live situation, change one variable suggested by Sketch independently, and decide in advance what outcome would count as improvement or disconfirmation.
3. Decide
In Sprint, Decide is part of the larger attempt to explain a five-day design process for choosing a challenge, sketching alternatives, deciding, prototyping, and testing with users before expensive implementation. Its importance is not the label itself but the change in attention it produces. A reader can ask what evidence would show this mechanism operating, what alternative explanation fits the same facts, and what behavior would change if the idea were taken seriously.
The analytical value of Decide is that it turns an abstract concern into something observable. Inspect choices, constraints, incentives, timing, feedback, and consequences rather than relying on intention alone. This prevents the concept from becoming a slogan while preserving the practical insight Jake Knapp, John Zeratsky, and Braden Kowitz is trying to communicate.
There is also a boundary condition. The same principle may work differently for an individual, a team, a market, or an institution. For practice, define one live situation, change one variable suggested by Decide, and decide in advance what outcome would count as improvement or disconfirmation.
4. Storyboard
In Sprint, Storyboard is part of the larger attempt to explain a five-day design process for choosing a challenge, sketching alternatives, deciding, prototyping, and testing with users before expensive implementation. Its importance is not the label itself but the change in attention it produces. A reader can ask what evidence would show this mechanism operating, what alternative explanation fits the same facts, and what behavior would change if the idea were taken seriously.
The analytical value of Storyboard is that it turns an abstract concern into something observable. Inspect choices, constraints, incentives, timing, feedback, and consequences rather than relying on intention alone. This prevents the concept from becoming a slogan while preserving the practical insight Jake Knapp, John Zeratsky, and Braden Kowitz is trying to communicate.
There is also a boundary condition. The same principle may work differently for an individual, a team, a market, or an institution. For practice, define one live situation, change one variable suggested by Storyboard, and decide in advance what outcome would count as improvement or disconfirmation.
5. Prototype facade
In Sprint, Prototype facade is part of the larger attempt to explain a five-day design process for choosing a challenge, sketching alternatives, deciding, prototyping, and testing with users before expensive implementation. Its importance is not the label itself but the change in attention it produces. A reader can ask what evidence would show this mechanism operating, what alternative explanation fits the same facts, and what behavior would change if the idea were taken seriously.
The analytical value of Prototype facade is that it turns an abstract concern into something observable. Inspect choices, constraints, incentives, timing, feedback, and consequences rather than relying on intention alone. This prevents the concept from becoming a slogan while preserving the practical insight Jake Knapp, John Zeratsky, and Braden Kowitz is trying to communicate.
There is also a boundary condition. The same principle may work differently for an individual, a team, a market, or an institution. For practice, define one live situation, change one variable suggested by Prototype facade, and decide in advance what outcome would count as improvement or disconfirmation.
6. Five-user interviews
In Sprint, Five-user interviews is part of the larger attempt to explain a five-day design process for choosing a challenge, sketching alternatives, deciding, prototyping, and testing with users before expensive implementation. Its importance is not the label itself but the change in attention it produces. A reader can ask what evidence would show this mechanism operating, what alternative explanation fits the same facts, and what behavior would change if the idea were taken seriously.
The analytical value of Five-user interviews is that it turns an abstract concern into something observable. Inspect choices, constraints, incentives, timing, feedback, and consequences rather than relying on intention alone. This prevents the concept from becoming a slogan while preserving the practical insight Jake Knapp, John Zeratsky, and Braden Kowitz is trying to communicate.
There is also a boundary condition. The same principle may work differently for an individual, a team, a market, or an institution. For practice, define one live situation, change one variable suggested by Five-user interviews, and decide in advance what outcome would count as improvement or disconfirmation.
How the ideas fit together
The concepts in Sprint are more useful as an interacting system than as a checklist. Some sharpen diagnosis, others explain mechanisms, and others shape execution or feedback. Action without diagnosis can optimize the wrong problem, while diagnosis without action produces no learning. A second connection is the relationship between agency and environment: defaults, incentives, social expectations, information, timing, and feedback can change the probability of an outcome. A third connection is uncertainty. Even a sensible recommendation does not remove randomness, so reversible experiments, ranges, scenarios, and review points are more useful than false certainty.
Limits and cautions
No framework in Sprint is a guaranteed formula. Successful outcomes can reflect timing, resources, selection effects, and luck in addition to the highlighted principle. Readers should separate descriptive claims, prescriptive recommendations, and anecdotes used to make those claims memorable. Process quality should be reviewed separately from outcome.
Key takeaways
The durable value of Sprint is a disciplined sequence: notice a pattern, name a mechanism, choose a response, observe consequences, and revise. The most useful final question is which claim matters in the reader's current situation, what evidence would strengthen or weaken it, and what small action would create new information.
Analytical extension: Map and target
A deeper test of Map and target begins by specifying the unit of analysis: an individual decision, recurring behavior, team process, customer interaction, or financial rule. Then define the counterfactual—what would probably happen if nothing changed? Without that comparison, ordinary fluctuation can be mistaken for improvement.
Next separate mechanism from outcome. Sprint gives a reason to expect Map and target to matter, but the result may also depend on incentives, timing, prior skill, external shocks, or selection effects. A small reversible test is often more informative than a dramatic commitment. State the assumption before acting, observe the result, and revise if evidence points elsewhere.
Analytical extension: Sketch independently
A deeper test of Sketch independently begins by specifying the unit of analysis: an individual decision, recurring behavior, team process, customer interaction, or financial rule. Then define the counterfactual—what would probably happen if nothing changed? Without that comparison, ordinary fluctuation can be mistaken for improvement.
Next separate mechanism from outcome. Sprint gives a reason to expect Sketch independently to matter, but the result may also depend on incentives, timing, prior skill, external shocks, or selection effects. A small reversible test is often more informative than a dramatic commitment. State the assumption before acting, observe the result, and revise if evidence points elsewhere.
Analytical extension: Decide
A deeper test of Decide begins by specifying the unit of analysis: an individual decision, recurring behavior, team process, customer interaction, or financial rule. Then define the counterfactual—what would probably happen if nothing changed? Without that comparison, ordinary fluctuation can be mistaken for improvement.
Next separate mechanism from outcome. Sprint gives a reason to expect Decide to matter, but the result may also depend on incentives, timing, prior skill, external shocks, or selection effects. A small reversible test is often more informative than a dramatic commitment. State the assumption before acting, observe the result, and revise if evidence points elsewhere.
Analytical extension: Storyboard
A deeper test of Storyboard begins by specifying the unit of analysis: an individual decision, recurring behavior, team process, customer interaction, or financial rule. Then define the counterfactual—what would probably happen if nothing changed? Without that comparison, ordinary fluctuation can be mistaken for improvement.
Next separate mechanism from outcome. Sprint gives a reason to expect Storyboard to matter, but the result may also depend on incentives, timing, prior skill, external shocks, or selection effects. A small reversible test is often more informative than a dramatic commitment. State the assumption before acting, observe the result, and revise if evidence points elsewhere.
Analytical extension: Prototype facade
A deeper test of Prototype facade begins by specifying the unit of analysis: an individual decision, recurring behavior, team process, customer interaction, or financial rule. Then define the counterfactual—what would probably happen if nothing changed? Without that comparison, ordinary fluctuation can be mistaken for improvement.
Next separate mechanism from outcome. Sprint gives a reason to expect Prototype facade to matter, but the result may also depend on incentives, timing, prior skill, external shocks, or selection effects. A small reversible test is often more informative than a dramatic commitment. State the assumption before acting, observe the result, and revise if evidence points elsewhere.
Analytical extension: Five-user interviews
A deeper test of Five-user interviews begins by specifying the unit of analysis: an individual decision, recurring behavior, team process, customer interaction, or financial rule. Then define the counterfactual—what would probably happen if nothing changed? Without that comparison, ordinary fluctuation can be mistaken for improvement.
Next separate mechanism from outcome. Sprint gives a reason to expect Five-user interviews to matter, but the result may also depend on incentives, timing, prior skill, external shocks, or selection effects. A small reversible test is often more informative than a dramatic commitment. State the assumption before acting, observe the result, and revise if evidence points elsewhere.
Analytical extension: Map and target
A deeper test of Map and target begins by specifying the unit of analysis: an individual decision, recurring behavior, team process, customer interaction, or financial rule. Then define the counterfactual—what would probably happen if nothing changed? Without that comparison, ordinary fluctuation can be mistaken for improvement.
Next separate mechanism from outcome. Sprint gives a reason to expect Map and target to matter, but the result may also depend on incentives, timing, prior skill, external shocks, or selection effects. A small reversible test is often more informative than a dramatic commitment. State the assumption before acting, observe the result, and revise if evidence points elsewhere.
Analytical extension: Sketch independently
A deeper test of Sketch independently begins by specifying the unit of analysis: an individual decision, recurring behavior, team process, customer interaction, or financial rule. Then define the counterfactual—what would probably happen if nothing changed? Without that comparison, ordinary fluctuation can be mistaken for improvement.
Next separate mechanism from outcome. Sprint gives a reason to expect Sketch independently to matter, but the result may also depend on incentives, timing, prior skill, external shocks, or selection effects. A small reversible test is often more informative than a dramatic commitment. State the assumption before acting, observe the result, and revise if evidence points elsewhere.
Analytical extension: Decide
A deeper test of Decide begins by specifying the unit of analysis: an individual decision, recurring behavior, team process, customer interaction, or financial rule. Then define the counterfactual—what would probably happen if nothing changed? Without that comparison, ordinary fluctuation can be mistaken for improvement.
Next separate mechanism from outcome. Sprint gives a reason to expect Decide to matter, but the result may also depend on incentives, timing, prior skill, external shocks, or selection effects. A small reversible test is often more informative than a dramatic commitment. State the assumption before acting, observe the result, and revise if evidence points elsewhere.
Analytical extension: Storyboard
A deeper test of Storyboard begins by specifying the unit of analysis: an individual decision, recurring behavior, team process, customer interaction, or financial rule. Then define the counterfactual—what would probably happen if nothing changed? Without that comparison, ordinary fluctuation can be mistaken for improvement.
Next separate mechanism from outcome. Sprint gives a reason to expect Storyboard to matter, but the result may also depend on incentives, timing, prior skill, external shocks, or selection effects. A small reversible test is often more informative than a dramatic commitment. State the assumption before acting, observe the result, and revise if evidence points elsewhere.
Analytical extension: Prototype facade
A deeper test of Prototype facade begins by specifying the unit of analysis: an individual decision, recurring behavior, team process, customer interaction, or financial rule. Then define the counterfactual—what would probably happen if nothing changed? Without that comparison, ordinary fluctuation can be mistaken for improvement.
Next separate mechanism from outcome. Sprint gives a reason to expect Prototype facade to matter, but the result may also depend on incentives, timing, prior skill, external shocks, or selection effects. A small reversible test is often more informative than a dramatic commitment. State the assumption before acting, observe the result, and revise if evidence points elsewhere.
Key ideas
Map and target. This is one of Sprint's central lenses. Use it to identify a concrete pattern, the mechanism that may sustain it, and a decision that would change if the idea is true.
Sketch independently. This is one of Sprint's central lenses. Use it to identify a concrete pattern, the mechanism that may sustain it, and a decision that would change if the idea is true.
Decide. This is one of Sprint's central lenses. Use it to identify a concrete pattern, the mechanism that may sustain it, and a decision that would change if the idea is true.
Storyboard. This is one of Sprint's central lenses. Use it to identify a concrete pattern, the mechanism that may sustain it, and a decision that would change if the idea is true.
Prototype facade. This is one of Sprint's central lenses. Use it to identify a concrete pattern, the mechanism that may sustain it, and a decision that would change if the idea is true.
Five-user interviews. This is one of Sprint's central lenses. Use it to identify a concrete pattern, the mechanism that may sustain it, and a decision that would change if the idea is true.
Practical application
Apply Sprint today
- Map and target: Choose one current situation, write a one-sentence diagnosis using the idea, and define one small reversible action to test.
- Sketch independently: Choose one current situation, write a one-sentence diagnosis using the idea, and define one small reversible action to test.
- Decide: Choose one current situation, write a
Key ideas
Map and target. This is one of Sprint's central lenses. Use it to identify a concrete pattern, the mechanism that may sustain it, and a decision that would change if the idea is true.
Sketch independently. This is one of Sprint's central lenses. Use it to identify a concrete pattern, the mechanism that may sustain it, and a decision that would change if the idea is true.
Decide. This is one of Sprint's central lenses. Use it to identify a concrete pattern, the mechanism that may sustain it, and a decision that would change if the idea is true.
Storyboard. This is one of Sprint's central lenses. Use it to identify a concrete pattern, the mechanism that may sustain it, and a decision that would change if the idea is true.
Prototype facade. This is one of Sprint's central lenses. Use it to identify a concrete pattern, the mechanism that may sustain it, and a decision that would change if the idea is true.
Five-user interviews. This is one of Sprint's central lenses. Use it to identify a concrete pattern, the mechanism that may sustain it, and a decision that would change if the idea is true.
Deep analysis
What Sprint is trying to explain
Jake Knapp, John Zeratsky, and Braden Kowitz's central project can be stated plainly: A five-day design process for choosing a challenge, sketching alternatives, deciding, prototyping, and testing with users before expensive implementation. A strong analysis must connect the book's ideas rather than merely collect advice. The reader needs to see the problem, the proposed mechanisms, how the ideas interact, where they guide action, and where they become weaker. Each concept can be translated into an observation or decision rule and tested against real constraints, uncertainty, trade-offs, and contradictory evidence.
1. Map and target
In Sprint, Map and target is part of the larger attempt to explain a five-day design process for choosing a challenge, sketching alternatives, deciding, prototyping, and testing with users before expensive implementation. Its importance is not the label itself but the change in attention it produces. A reader can ask what evidence would show this mechanism operating, what alternative explanation fits the same facts, and what behavior would change if the idea were taken seriously. Inspect choices, constraints, incentives, timing, feedback, and consequences rather than relying on intention alone. This prevents the concept from becoming a slogan while preserving the practical insight Jake Knapp, John Zeratsky, and Braden Kowitz is trying to communicate.
There is also a boundary condition. The same principle may work differently for an individual, a team, a market, or an institution. For practice, define one live situation, change one variable suggested by Map and target, and decide in advance what outcome would count as improvement or disconfirmation.
2. Sketch independently
In Sprint, Sketch independently is part of the larger attempt to explain a five-day design process for choosing a challenge, sketching alternatives, deciding, prototyping, and testing with users before expensive implementation.
There is also a boundary condition. For practice, define one live situation, change one variable suggested by Sketch independently, and decide in advance what outcome would count as improvement or disconfirmation.
3. Decide
In Sprint, Decide is part of the larger attempt to explain a five-day design process for choosing a challenge, sketching alternatives, deciding, prototyping, and testing with users before expensive implementation.
There is also a boundary condition. For practice, define one live situation, change one variable suggested by Decide, and decide in advance what outcome would count as improvement or disconfirmation.
4. Storyboard
In Sprint, Storyboard is part of the larger attempt to explain a five-day design process for choosing a challenge, sketching alternatives, deciding, prototyping, and testing with users before expensive implementation.
There is also a boundary condition. For practice, define one live situation, change one variable suggested by Storyboard, and decide in advance what outcome would count as improvement or disconfirmation.
5. Prototype facade
In Sprint, Prototype facade is part of the larger attempt to explain a five-day design process for choosing a challenge, sketching alternatives, deciding, prototyping, and testing with users before expensive implementation.
There is also a boundary condition. For practice, define one live situation, change one variable suggested by Prototype facade, and decide in advance what outcome would count as improvement or disconfirmation.
6. Five-user interviews
In Sprint, Five-user interviews is part of the larger attempt to explain a five-day design process for choosing a challenge, sketching alternatives, deciding, prototyping, and testing with users before expensive implementation.
There is also a boundary condition. For practice, define one live situation, change one variable suggested by Five-user interviews, and decide in advance what outcome would count as improvement or disconfirmation.
How the ideas fit together
The concepts in Sprint are more useful as an interacting system than as a checklist. Some sharpen diagnosis, others explain mechanisms, and others shape execution or feedback. Action without diagnosis can optimize the wrong problem, while diagnosis without action produces no learning. A second connection is the relationship between agency and environment: defaults, incentives, social expectations, information, timing, and feedback can change the probability of an outcome. A third connection is uncertainty. Even a sensible recommendation does not remove randomness, so reversible experiments, ranges, scenarios, and review points are more useful than false certainty.
Limits and cautions
No framework in Sprint is a guaranteed formula. Successful outcomes can reflect timing, resources, selection effects, and luck in addition to the highlighted principle. Readers should separate descriptive claims, prescriptive recommendations, and anecdotes used to make those claims memorable. Process quality should be reviewed separately from outcome.
Key takeaways
The durable value of Sprint is a disciplined sequence: notice a pattern, name a mechanism, choose a response, observe consequences, and revise. The most useful final question is which claim matters in the reader's current situation, what evidence would strengthen or weaken it, and what small action would create new information.
Analytical extension: Map and target
A deeper test of Map and target begins by specifying the unit of analysis: an individual decision, recurring behavior, team process, customer interaction, or financial rule. Then define the counterfactual—what would probably happen if nothing changed. Without that comparison, ordinary fluctuation can be mistaken for improvement.
Next separate mechanism from outcome. Sprint gives a reason to expect Map and target to matter, but the result may also depend on incentives, timing, prior skill, external shocks, or selection effects. A small reversible test is often more informative than a dramatic commitment. State the assumption before acting, observe the result, and revise if evidence points elsewhere.
Analytical extension: Sketch independently
A deeper test of Sketch independently begins by specifying the unit of analysis: an individual decision, recurring behavior, team process, customer interaction, or financial rule.
Next separate mechanism from outcome. Sprint gives a reason to expect Sketch independently to matter, but the result may also depend on incentives, timing, prior skill, external shocks, or selection effects.
Finally consider second-order effects.
Analytical extension: Decide
A deeper test of Decide begins by specifying the unit of analysis: an individual decision, recurring behavior, team process, customer interaction, or financial rule.
Next separate mechanism from outcome. Sprint gives a reason to expect Decide to matter, but the result may also depend on incentives, timing, prior skill, external shocks, or selection effects.
Finally consider second-order effects.
Analytical extension: Storyboard
A deeper test of Storyboard begins by specifying the unit of analysis: an individual decision, recurring behavior, team process, customer interaction, or financial rule.
Next separate mechanism from outcome. Sprint gives a reason to expect Storyboard to matter, but the result may also depend on incentives, timing, prior skill, external shocks, or selection effects.
Finally consider second-order effects.
Analytical extension: Prototype facade
A deeper test of Prototype facade begins by specifying the unit of analysis: an individual decision, recurring behavior, team process, customer interaction, or financial rule.
Next separate mechanism from outcome. Sprint gives a reason to expect Prototype facade to matter, but the result may also depend on incentives, timing, prior skill, external shocks, or selection effects.
Finally consider second-order effects.
Analytical extension: Five-user interviews
A deeper test of Five-user interviews begins by specifying the unit of analysis: an individual decision, recurring behavior, team process, customer interaction, or financial rule.
Next separate mechanism from outcome. Sprint gives a reason to expect Five-user interviews to matter, but the result may also depend on incentives, timing, prior skill, external shocks, or selection effects.
Finally consider second-order effects.
Next separate mechanism from outcome.
Finally consider second-order effects.
Next separate mechanism from outcome.
Finally consider second-order effects.
Next separate mechanism from outcome.
Finally consider second-order effects.
Next separate mechanism from outcome.
Finally consider second-order effects.
Next separate mechanism from outcome.
Finally consider second-order effects.
Practical application
Apply Sprint today
- Map and target: Choose one current situation, write a one-sentence diagnosis using the idea, and define one small reversible action to test.
- Sketch independently: Choose one current situation, write a one-sentence diagnosis using the idea, and define one small reversible action to test.
- Decide: Choose one current situation, write a one-sentence diagnosis using the idea, and define one small reversible action to test.
- Storyboard: Choose one current situation, write a one-sentence diagnosis using the idea, and define one small reversible action to test.
- Prototype facade: Choose one current situation, write a one-sentence diagnosis using the idea, and define one small reversible action to test.
- Five-user interviews: Choose one current situation, write a one-sentence diagnosis using the idea, and define one small reversible action to test.
Review the result after a defined interval and revise the rule if the evidence is weak.
Continue exploring
Sprint FAQs
Who wrote Sprint?
Sprint was written by Jake Knapp, John Zeratsky, and Braden Kowitz.
What is Sprint about?
Sprint by Jake Knapp, John Zeratsky, and Braden Kowitz is a product design book built around a clear concern: A five-day design process for choosing a challenge, sketching alternatives, deciding, prototyping, and testing with users before expensive implementation. Its major ideas include Map and target, Sketch independently, Decide, Storyboard. The useful reading is to connect these concepts into a way of diagnosing decisions…
What are the key ideas in Sprint?
Map and target. Use it to identify a concrete pattern, the mechanism that may sustain it, and a decision that would change if the idea is true. Sketch independently.
Is this the full text of Sprint?
No. This Booknomics page is an independent study summary and analysis of Sprint; it is not the full text of the original book.
Related book summaries
- Empowered — Marty Cagan and Chris Jones
- Escaping the Build Trap — Melissa Perri
- Hooked — Nir Eyal with Ryan Hoover
- Inspired — Marty Cagan