Beyond Lean and Agile

Marty Cagan argues that while Lean and Agile are often criticized, their core principles remain valuable, even though most companies practice them poorly. He observes that the best product teams have already moved beyond typical implementations by adopting three underlying principles. These are tackling risks before building, defining solutions collaboratively rather than sequentially, and focusing on solving problems rather than shipping features. He connects these principles to the dual-track model of discovery and delivery, and to similar ideas in design thinking, customer development, and Y Combinator's approach. The message matters because it reframes agile success around outcomes and risk reduction rather than process compliance.

01Key takeaways

• Tackle value and business risks before writing production software, not after building.
• Have product, design, and engineering shape solutions together rather than passing requirements down a line.
• Measure work by the problem it solves and the results it produces, not by features shipped.
• Build a real MVP with a clear learning goal, rather than spending months building something you cannot yet evaluate.
• Run discovery in parallel with delivery so validated solutions keep flowing to engineering.

02Key sections

Disappointment with Lean and Agile

Cagan notes that many teams are disappointed with Lean and Agile, but he believes the underlying principles are still sound. He points out that teams often misuse these methods, such as building an MVP without knowing what it will sell, or validating everything and stalling.

Tackling risks up front

Strong teams address value, usability, feasibility, and business risks before committing to build anything. This shifts validation from the end of a project to the beginning.

Collaborative definition and design

Product, design, and engineering work side by side in a back-and-forth process instead of handing off requirements sequentially. This produces solutions that are both loved by customers and workable for the business.

Solving problems, not implementing features

Roadmaps focused on output miss the point, so teams should judge success by whether the solution actually solves the underlying problem. The emphasis is on delivering results.

The dual-track model and related approaches

Cagan links the three principles to continuous discovery running alongside continuous delivery. He notes that design thinking, design sprints, customer development, and Y Combinator's mantra rest on the same ideas.

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.