The Need For Speed

Marty Cagan argues that product teams need to move fast, and that many teams still hold a Waterfall-era belief that speed trades off against quality and innovation. He contends that speed is valuable for reasons beyond beating competitors to market, which he says is one of his least important motives. He lists ten reasons speed matters, including more learning iterations, staying focused on the MVP, earning leadership support, and keeping customers happy. He also notes that a team's ability to learn and move quickly is one of the few differentiators competitors cannot easily copy. Speed, he stresses, comes from skill, technique, and culture rather than long hours.

01Key takeaways

• Treat speed as a driver of learning, since faster iterations let you test more approaches within the same budget.
• Use urgency to keep the team building only the minimum viable product rather than over-engineering.
• Deliver small, incremental changes with test automation to get better quality than large batch releases.
• Get working software to early customers quickly so real usage data can guide product decisions.
• Recognize that the ability to learn and move fast is harder for competitors to copy than any single feature.
• Build speed through skills, techniques, and culture instead of asking people to work longer hours.

02Key sections

Speed versus the Waterfall mindset

Many teams still believe quality, time, and scope must be traded off against each other. Cagan argues this belief is rooted in outdated Waterfall thinking.

Speed drives learning and focus

Faster cycles allow more experiments in the same time, while urgency keeps teams building only the smallest viable product and aligned to their purpose.

Speed improves quality and customer outcomes

Small, incremental, automated delivery produces better quality than big-bang handoffs, and fast fixes and early live usage data make customers happier and inform direction.

Speed builds morale, leadership support, and differentiation

Visible progress wins leadership backing and motivates the team, and the ability to learn fast is a hard-to-copy advantage.

Speed is not long hours

Real speed comes from team skill, technique, and culture, and forcing overtime undermines the motivation that speed depends on, with the product owner carrying most of the responsibility.

03From the post

“A partnership dedicated to teaching best practices to product teams and product leaders”

04Frameworks mentioned

Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.