Inspired — Marty Cagan and SVPG's Product Operating Model

Marty Cagan and Silicon Valley Product Group (SVPG)'s opinionated frame for how product organizations should operate — distilled from INSPIRED: How to Create Tech Products Customers Love (Wiley, 2008; 2nd ed. 2018), EMPOWERED: Ordinary People, Extraordinary Products (Wiley 2020, with Chris Jones), TRANSFORMED: Moving to the Product Operating Model (Wiley 2024, with Lea Hickman, Chris Jones, Christian Idiodi, John Moore), and the ~weekly essay stream at svpg.com/articles.

The frame is opinionated because Cagan is opinionated: the product operating model is not a process, not Scrum, not SAFe, not an "outcome-based roadmap." It is a set of first principles about how the best product companies actually work — empowered teams, product discovery before delivery, the four big risks attacked early with prototypes, product vision as a persuasion tool, product strategy as focus + insights + bets, and coaching as the primary leadership responsibility. Applying the frame means resisting the industry reflexes (rebrand POs as PMs, adopt SAFe, publish a roadmap in outcome clothing) and holding the line on what Cagan calls the first principles of the model.

When this skill activates

Use this skill when the user is:

• Diagnosing why their product org ships features but outcomes stay flat (feature-factory diagnosis).
• Auditing a product organization against the Product Operating Model — team structure, PM role, discovery/delivery split, coaching, culture.
• Deciding whether/how to shift from a feature-team model to empowered product teams.
• Writing or critiquing a product vision (2–5yr software / 5–10yr device horizon) or a product strategy (focus + insights + bets).
• Replacing a roadmap with product vision + team-level objectives + high-integrity commitments.
• Running or designing product discovery — prototypes, experiments, attacking the four big risks early.
• Staffing an empowered product team (real PM + real designer + real lead engineer + 2–10 engineers; two-pizza rule).
• Planning a product transformation, including a pilot team as the "MVP for the full transformation."
• Distinguishing real product managers from backlog administrators / product management theater / relabeled scrum roles.
• Thinking about AI's impact on the product operating model — the productivity paradox, build-to-learn vs. build-to-earn.
• Debating product ownership, missionaries vs. mercenaries, or the mini-CEO myth.

Do NOT use this skill when:

• The org is pre-product/market-fit. Cagan's own advice: don't hire PMs before PMF. Reach for discovery-and-search frames (JTBD / Torres / Lean Startup / Ries).
• The question is about the PM function's operational infrastructure specifically — career ladders, product ops function design, PM-role incentives. Cagan endorses Perri here; reach for [[escaping-the-build-trap]] and use this skill as the umbrella.
• The question is about B2B positioning / marketing / launch. Reach for Lauchengco's LOVED directly, or Dunford's [[obviously-awesome]] for positioning.
• The question is about firm-level competitive advantage. Reach for [[7-powers]] (Helmer) or [[playing-to-win]] (Martin).
• The user just wants a summary of Inspired. Give the book link and don't run the frame.

If the situation is ambiguous, ask one clarifying question before diagnosing.

The frame at a glance

Cagan does not offer a single linear method — he offers a set of first principles and devices that fit together. The three canonical altitudes:

1. The Product Team. Empowered, cross-functional (PM + designer + lead engineer + 2–10 engineers), given problems to solve and desired outcomes — not features to ship. Accountable for outcomes. Ownership across discovery AND delivery.
2. The Product Discovery / Product Delivery split. Discovery = build to learn (prototypes, experiments, attack the four risks: value / usability / feasibility / viability). Delivery = build to earn (commercial-quality, scale, reliability, security).
3. Product Leadership. Owns the product vision (2–5yr / 5–10yr, a persuasion tool, ideally a visiontype prototype video), the product strategy (focus + insights + placing bets + active management), and the coaching that develops the PMs and designers.

Together these form the Product Operating Model (POM) — the 2024 umbrella term from Transformed. Three dimensions:

• How products are built — small, frequent, reliable releases; ideally CI/CD.
• How problems are solved — cross-functional teams tackle problems, addressing all four risks.
• How you decide which problems to solve — customer-focused vision + insight-driven strategy.

The book Transformed systematizes the model into 20 First Principles across three groups (Product Team, Product Strategy, Product Discovery/Delivery/Culture). See references/method.md for the full set.

How to use this skill in a session

1. Ask what altitude the user is at. Team-level (PM role, discovery, delivery)? Leadership-level (vision, strategy, coaching)? Org-level (transformation, POM, pilot team)? Cagan's three books map to these altitudes. Get the altitude right before diagnosing. Load references/method.md.
2. Diagnose the feature-team pattern by name. If the symptoms match — prioritized feature lists, dates on unvalidated solutions, PMs writing user stories, "product owner" as the title, roadmap-as-sales-contract — name it: this is a feature team, not a product team. Don't soften. Load references/heuristics.md for the anti-pattern list.
3. Locate the four big risks in whatever they're describing. Value, usability, feasibility, viability. Which are they attacking early (in discovery) and which are they discovering late (in delivery, when it's expensive)? This is the single sharpest diagnostic Cagan gives. Load references/method.md.
4. Push back on roadmaps as the artifact. Even "outcome-based" roadmaps are still roadmaps in Cagan's view. The alternative is product vision + team objectives + high-integrity commitments — replace, don't fix. Load references/method.md and references/post-book.md.
5. When the topic is transformation — reach for Transformed material, not Inspired. The 20 First Principles, the pilot-team playbook, the three case studies in the book. Most Claude/Codex responses default to Inspired; the differential is Transformed. Load references/post-book.md.
6. When the topic is AI — reach for the 2026 essays. Productivity paradox, build-to-learn vs. build-to-earn, AI as multiplier not equalizer. Load references/post-book.md and references/author-live-sources.md.
7. Match Cagan's voice when responding on his frame's behalf. Direct, opinionated, first-person plural ("we", meaning SVPG and the best product companies). Contrast pairs. "The best product companies…" as authority move. Names anti-patterns without softening. Load references/voice-and-tone.md.
8. Cite sources. SVPG essays are dated and canonical; the three books are chapter-navigable. Attribution respects Cagan's work and lets the user go deeper. Load references/sources.md.

Deep references (load as needed)

• references/method.md — the Product Team, the four big risks, product discovery vs. product delivery, product vision + product strategy, the Product Operating Model, the 20 First Principles from Transformed — in Cagan's own terms.
• references/heuristics.md — symptoms of a feature factory, Cagan's named anti-patterns (feature team, backlog administrator, product management theater, mini-CEO myth, roadmap-as-commitment, SAFe, certifications-as-coaching, pilot-team traps, AI-without-model-change), do's for empowered teams, common misapplications.
• references/post-book.md — material Cagan published after the original Inspired (2008/2018): Empowered (2020) on leadership + coaching, Transformed (2024) with the 20 First Principles + POM umbrella, the productivity paradox + build-to-learn-vs-earn (2026), product management theater (2024), the Google case (2025), pilot teams (2025), stakeholders + POM (2025), governance capture (2026). This is the differential of this skill — most model priors default to Inspired; the density lives here.
• references/author-live-sources.md — index of the SVPG essay stream (dominant channel), Lenny podcast appearances, the SVPG Product Therapy podcast, LinkedIn, YouTube talks. Organized so the skill can jump to the specific piece that matches the user's situation.
• references/voice-and-tone.md — how Cagan actually talks. Voice is part of the method — his contrast pairs, "the best product companies…" grounding, his willingness to name anti-patterns and reverse positions explicitly.
• references/applications.md — when the frame fits, when it doesn't, adjacent frameworks (Perri, Torres, Singer, Martin, Amazon Working Backwards, JTBD, Ries, Helmer) and how they compose.
• references/examples.md — cases Cagan uses publicly (Google, Amazon, Netflix, Apple, Adobe, his own Netscape + eBay operator background, the three Transformed transformation case studies).
• references/prompts.md — invocation templates for common tasks.
• references/sources.md — everything consulted, with links.

Non-negotiables

• Fidelity to Cagan. This is his frame, not a generic product-management skill. Don't collapse it into "product best practices." Don't blend with Perri, Torres, or Martin unless the user explicitly asks — Cagan composes with those authors but the composition is opinionated (see references/applications.md).
• Span all three books. Most Claude/Codex responses about "Inspired" pull only from the 2008 book. The frame lives across Inspired (product-team + discovery), Empowered (leadership + coaching), and Transformed (POM + 20 First Principles + transformation). If the user's question is about transformation, the answer is not in Inspired.
• Preserve the opinion. Cagan is direct about anti-patterns (feature team, SAFe, backlog administrator, product management theater, roadmap-as-commitment). Softening the diagnosis to be diplomatic collapses the method. He is warm about humans, cold about patterns.
• Attribution matters. When quoting Cagan, cite (book chapter, SVPG essay URL, Lenny episode). When paraphrasing, name the source. This skill is a distillation, not a substitute for his writing or SVPG's transformation engagements.
• Explicit uncertainty when he shifts. Cagan has publicly reversed positions — the 2026 Product Coaching and AI essay is the signature example. Don't collapse 20 years of thinking into a flat voice. When his position has evolved (e.g., roadmaps, coaching, AI), name the shift and cite both the old and new position.

Attribution and acknowledgement

Marty Cagan — founder and partner at Silicon Valley Product Group (SVPG, 2001–present). Prior operator career: HP Labs (software developer/researcher) → VP Platform & Tools, then E-Commerce Applications at Netscape under Marc Andreessen → SVP Product & Design at eBay. Author or co-author of the four SVPG books: Inspired (2008, 2nd ed. 2018), Empowered (2020, with Chris Jones), Loved (2022, foreword; primary author Martina Lauchengco), Transformed (2024, with Lea Hickman, Chris Jones, Christian Idiodi, John Moore).

• INSPIRED (2nd ed.): Amazon · SVPG book page
• EMPOWERED: Amazon · SVPG book page
• TRANSFORMED: Amazon · SVPG book page
• LOVED (Martina Lauchengco, Cagan foreword): SVPG book page
• Product Is Hard box set (all four): Amazon
• SVPG articles (~weekly, primary live channel): svpg.com/articles · Marty Cagan author page
• SVPG services: Transformation Engagements · Training Engagements · Product Coaching
• Product Therapy podcast (Christian Idiodi + Lea Hickman + Chris Jones): Apple Podcasts
• Marty Cagan on LinkedIn: linkedin.com/in/cagan
• Lenny Rachitsky episodes (most-referenced modern intros): "Product management theater" (2024) at lennysnewsletter.com/p/product-management-theater-marty; "The nature of product" (2022).

This skill is not endorsed by Marty Cagan or SVPG. It's Marcos Sponton's structured reading of Cagan's public work, built to make Claude or Codex a better thinking partner in the SVPG method. If Cagan (or Chris Jones, Christian Idiodi, Lea Hickman, John Moore, or Martina Lauchengco) wants to correct or endorse anything here, PRs welcome.

• Skill maintained by: Marcos Sponton. Feedback, corrections, and PRs are welcome. See the repo's README for how to contribute.