Inspired: How to Create Tech Products Customers Love
Source: https://www.svpg.com/books/inspired-how-to-create-products-customers-love-by-marty-cagan/ ↗
Cagan's guide to how the strongest tech product organisations actually operate — empowered product teams, product discovery, continuous delivery, the difference between feature factories and outcome-driven teams.
The book gathers decades of Silicon Valley product practice into a structured argument that is more polemical than it reads: most companies calling themselves "product-led" are running a cargo-cult version of what Cagan describes.
For a product director it is a checklist of where the gap lies between rhetoric and practice.
The second edition is the essential one — Cagan sharpened it after a decade of consulting exposure to companies that had read the first and still got it wrong.
Read alongside Empowered for the leadership layer.
Central argument
Cagan argues that the dominant model of product development — where engineering teams execute a prioritised roadmap defined by business stakeholders — is structurally incapable of producing great products, because it confuses output with outcome and removes discovery from the people closest to the technology. The book's central thesis is that the best tech companies operate through empowered product teams given a problem to solve, not a feature to build, and that the product manager role is fundamentally about owning the intersection of customer value, business viability, and technical feasibility before anything is committed to development. Product discovery — rapid, low-cost experimentation to reduce risk before delivery — is the mechanism that separates these teams from what Cagan calls feature factories.
Critique
The model Cagan describes is drawn almost entirely from a specific cohort of well-resourced, consumer-facing Silicon Valley companies at a particular moment of growth, which limits its transferability to regulated industries, enterprise software, or organisations where customer needs are mediated through procurement and contracts rather than direct usage data. A deeper tension the book does not fully resolve is the power dynamics required to actually run empowered teams: Cagan's framework presupposes an executive layer willing to relinquish roadmap control, but offers thin guidance on how product leaders navigate organisations where that authority is structurally held elsewhere — a gap the curator's note acknowledges is partly addressed only in the later companion volume.
Why it matters for product
For a product director, the book's sharpest operational use is as a diagnostic: the distinction between a team that is handed solutions and one that owns the problem exposes whether discovery is genuinely integrated into the delivery cycle or performed as a ritual after decisions have already been made. The framework around product trio accountability — product manager, designer, and tech lead jointly responsible for outcomes — is directly applicable to org design decisions about where to seat authority, how to structure team charters, and what to hold teams accountable for in performance conversations.