Key Moments
Marty Cagan: Strong Opinions, loosely held
Lenny's PodcastKey Moments
Marty Cagan regrets underestimating business viability and product leadership, arguing that AI now makes clear thinking and outcome focus more critical than ever.
Key Insights
Cagan admits to a significant blind spot regarding business viability, which he largely ignored in the first edition of 'Inspired' (2008), only addressing it ten years later.
He emphasizes that the core of product management is solving customer problems and delivering business results, not simply focusing on the latest processes or frameworks.
The 'why are people NOT using our product?' question is presented as a more critical driver of innovation than understanding the 'why we are building this'.
Cagan criticizes the over-reliance on roadmaps and PRDs, suggesting they can stifle innovation by fostering a false sense of predictability and knowledge.
He argues that product organizations need better leadership, not just less management, highlighting the critical role of product strategy.
Cagan expresses concern that AI and LLMs might be used as a substitute for critical thinking, a trend he's observed with processes in many companies.
The critical oversight of business viability
Marty Cagan opens by confessing his most embarrassing regret: severely underestimating the importance of business viability in product development. He defines viability as ensuring that solutions are not only accepted by customers but are also marketable, sellable, maintainable, legal, compliant, and ethical. While discussing value, usability, and viability as risks in the first edition of 'Inspired,' he admits viability was almost entirely neglected. He spent a decade correcting this blind spot, eventually addressing it in the second edition. Cagan notes that his background in developer tools and platforms, a niche where business acumen could be overlooked, contributed to this oversight. However, he stresses that for most products, especially those involving AI, business viability must be a fundamental consideration, viewed through a systems-thinking lens. This underscores a shift from focusing solely on technical feasibility and user desirability to a more holistic business perspective. The implication is that a product's success hinges not just on solving a user problem but on its ability to thrive commercially.
The overlooked importance of problem discovery
Cagan revisits his long-held emphasis on product discovery, which encompasses both problem discovery and solution discovery. He regrets not fully appreciating how much people are drawn to the problem discovery aspect, often seeing themselves as 'gatekeepers' who must ensure everyone agrees a problem exists. While understanding the problem, its target audience, and success metrics is necessary, Cagan argues it's often not the most challenging part and can distract from the crucial task of solution discovery. He warns that focusing too much on problem definition can lead to wasted effort, as a better solution from a competitor might reveal the initial problem wasn't as significant as assumed. Therefore, while problem discovery is important, dedicating ample time to solution discovery is where true innovation lies.
Prioritizing 'why people don't use our product?'
While the common wisdom, popularized by figures like John Doerr, emphasizes understanding 'why' teams are working on something (being missionaries, not mercenaries), Cagan points to a more critical question: 'Why are people not using our product?' He laments that this question, which he believes is key to unlocking innovation, is rarely asked by most teams. Cagan shares his own practice of constantly trying new products and frequently abandoning them due to poor quality, yet notes the lack of follow-up from companies. He highlights that understanding user attrition is vital, as it reveals deeper insights than simply knowing the intended purpose of a product. This perspective challenges teams to look beyond initial adoption and focus on sustained engagement and user retention.
The detrimental impact of predictability and arrogance
Cagan delves into the concept of humility in product development, defining it as recognizing what you don't know and admitting ignorance. He contends that the common interpretation of the product manager as 'CEO of the product' contradicts this essential humility. This desire for predictability, shared by both product teams and executives, is deeply at odds with genuine innovation and achieving results. He specifically targets roadmaps and Product Requirements Documents (PRDs) as artifacts that often entrench this desire for predictability, creating a false sense of knowing more than we do. Cagan clarifies that PRDs and roadmaps are not inherently bad, but their purpose is crucial. If used arrogantly to dictate solutions, they become blockers. However, if informed by learning, testing, and evidence, they can be valuable communication tools. The underlying issue is that the pursuit of predictability can lead to the waste of engineering resources and sacrifice of actual outcomes.
The pervasive influence of politics
Contrary to his initial belief that product quality would be the sole determinant of success, Cagan acknowledges the pervasive and deeply ingrained nature of politics within organizations. He notes that politics has become a significant focus in his recent content, almost as much as AI. This realization came after years of helping companies improve their products, only to see them become targets for individuals with different agendas seeking to alter the product's direction. This suggests that technical excellence alone is insufficient; navigating organizational dynamics is equally critical for a product's long-term survival and success.
The critical role of product leadership
Cagan expresses regret for not focusing more on product leadership in his earlier work. He observes that many companies, after reading 'Inspired,' mistakenly believe that simply forming empowered product teams and hiring strong product managers is sufficient. This overlooks the crucial need for superior management and effective product leadership. He defines product leadership as providing essential context, including a clear product strategy—a prioritized list of problems to solve. Without this strategic direction from leadership, even empowered teams can struggle to make meaningful progress or align with business goals.
The necessity of thinking, not just processes
Cagan identifies 'thinking' as the core of good product work and laments how often people go to great lengths to avoid it, often by fixating on processes and frameworks. He admits his own mistake in structuring 'Inspired' around people, process, and product, considering it a significant error. He expresses concern, particularly with the rise of AI and Large Language Models (LLMs), that these tools might be used as a substitute for critical thinking, a trend he notes has already occurred with processes in many companies. He echoes Elon Musk's sentiment that processes are often used as a crutch for a lack of genuine thought. Cagan stresses that the fundamental requirement for product sense is clear, explicit thinking.
Building for learning over predictable output
Despite his list of regrets, Cagan remains optimistic about the future of product development, particularly in the context of AI. He addresses the common criticisms of his work: that companies are addicted to output and predictability, and that implementing his principles is difficult. However, he argues that AI actually makes focusing on outcomes—rather than just outputs—more necessary and achievable than ever. He introduces the concept of 'building for learning' versus 'building for profit,' a distinction derived from Jeff Patton's work. The difference lies between product discovery (learning) and product delivery. Cagan emphasizes that product managers should aim to ensure that whatever is built achieves the desired outcome, requiring a fundamentally different approach focused on learning and iteration. He concludes that the principles of product management, the craft of product strategy, and product discovery are more vital now than ever, amplified by AI.
Mentioned in This Episode
●Books
●People Referenced
Common Questions
Marty Cagan identifies two primary product models: the project model and the product model. He emphasizes that his work primarily focuses on the product model, which aims to solve customer problems and achieve business results.
Topics
Mentioned in this video
Credited with the idea that teams need to be missionaries, not mercenaries, emphasizing the importance of understanding the 'why' behind the work.
Author of the book 'The Lean Startup', whose new book 'Unquantifiable' is recommended by the speaker in the context of corporate governance.
Mentioned as being correct in his observation that in many companies, processes are used as a substitute for thinking.
Mentioned as the originator of a concept related to 'building for learning', which the speaker adapts.
Acknowledged for providing feedback on early versions of the speaker's content.
Acknowledged for providing feedback on early versions of the speaker's content.
More from Lenny's Podcast
View all 52 summaries
24 minThe last roadmap | Claire Vo
97 min90 minutes of unfiltered product advice from Snap and Discord’s product chief | Peter Sellis
83 minHow we built Grok Bot in a month | Roman Ugarte (SpaceXAI)
80 minWhy companies are becoming a series of loops | Anish Acharya (a16z)
Ask anything from this episode.
Save it, chat with it, and connect it to Claude or ChatGPT. Get cited answers from the actual content — and build your own knowledge base of every podcast and video you care about.
Get Started Free