Where to Start with Marty Cagan: A Reading Guide
Where to start with Marty Cagan — how to approach Inspired, the canonical guide to technology product management covering team structure, product discovery, and how to build products customers love. A complete reading guide.
By Marcus Webb
Marty Cagan is an American technology executive and author who worked as a product manager and product leader at Hewlett-Packard, eBay, and Netscape before founding the Silicon Valley Product Group (SVPG) in 2001. SVPG has since trained and coached product teams at hundreds of companies, and Cagan has become the most influential voice in technology product management. Inspired: How to Create Tech Products Customers Love was first published in 2008 and substantially revised in 2017; the second edition is the standard reference in the field, the book that product managers at every level read first and return to throughout their careers.
Where to Start: Inspired (2017)
The essential Marty Cagan — and the canonical text of modern technology product management. Inspired opens with a question that sounds simple but exposes everything: what distinguishes the companies that build technology products customers love from the vast majority that produce mediocre products despite adequate resources? Cagan’s answer is structural — a matter of how product teams are organised and how they work — not a matter of talent, funding, or technology.
The feature team vs. empowered product team distinction is the book’s most clarifying insight. A feature team is given requirements by stakeholders — business leaders, executives, sales teams — and builds them. Its accountability is to ship what it was asked to ship on the timeline it was given. An empowered product team is given a problem to solve (increase retention, reduce support costs, reach a new customer segment) and is held accountable for whether it solves it. The product team owns outcomes; the feature team owns output. The difference in what they produce is not marginal.
Product discovery is the discipline that most companies skip and that Cagan considers the foundation of building anything worth building. Discovery is the work that happens before development: understanding customer problems in sufficient depth to generate solutions worth building, then testing those solutions through prototypes before committing engineering resources. The four risks that every product faces — value risk (will customers buy or use this?), usability risk (can customers figure out how to use this?), feasibility risk (can our team build this?), and business viability risk (does this work for our business?) — define what discovery work needs to address.
The prototype is the primary tool for de-risking discovery. Cagan’s principle: build the cheapest version possible that tests your most important assumption. A high-fidelity prototype that simulates a key user flow costs days and tests in hours; a full engineering build of the same feature costs months. The goal is to fail quickly and cheaply, not to succeed expensively.
The product manager role is defined precisely, and the precision matters. PMs are not project managers — they are accountable for the business results their product generates, not for the timely delivery of a feature list. This accountability model is different from how most organisations actually deploy PMs, and understanding the distinction is foundational to building effective product practice.
Reading Marty Cagan
Inspired is Cagan’s essential and most widely read book. Readers who want to continue should move to Empowered (2020), which covers the product leadership side of building the teams Inspired describes.
For the full Marty Cagan bibliography, reviews, and biography, visit the Marty Cagan author page on Editors Reads.
Affiliate disclosure: Links to Amazon on this page are affiliate links. We earn a small commission at no extra cost to you.
Frequently Asked Questions
Where should I start with Marty Cagan?
Inspired: How to Create Tech Products Customers Love (second edition 2017) is Cagan's essential book — the canonical text of modern technology product management, covering the distinction between feature teams and empowered product teams, the product discovery framework, the four risks every product faces, and the cultural conditions that allow great products to emerge. It is the book every product manager reads early in their career and returns to throughout it.
What is Inspired about?
Inspired argues that the difference between the best technology products in the world and everything else comes down to how product teams are structured and how they work. The central distinction: feature teams take requirements from stakeholders and build them; empowered product teams are given problems to solve and held accountable for outcomes. The book covers product discovery (finding what to build, validating assumptions before committing to development), product delivery (building and shipping), and the role of the product manager as accountable for business results rather than project timelines.
Is Inspired relevant for non-technical product managers or for startups?
Yes to both. Cagan's framework applies to any technology product — mobile apps, SaaS products, consumer platforms — regardless of the PM's technical background. The concepts of product discovery, prototype-based risk reduction, and outcome accountability are if anything more critical for startups, which cannot afford to build the wrong thing. The book primarily describes how top-tier tech companies operate, which Cagan acknowledges may mean smaller teams need to adapt the framework rather than apply it directly.
What should I read after Inspired?
After Inspired, Cagan's companion book Empowered (2020) covers the product leadership side — how to build and lead the kind of teams Inspired describes. Rob Fitzpatrick's The Mom Test is the most practical guide to the customer discovery interviews that underpin the discovery work Inspired advocates. Teresa Torres's Continuous Discovery Habits provides the most operational implementation of Cagan's product discovery framework.
