| name | cagan-empowered |
| description | Knowledge base from "EMPOWERED: Ordinary People, Extraordinary Products" by Marty Cagan with Chris Jones. Use when applying Cagan's frameworks for product leadership, coaching product teams, staffing, product vision, product strategy, team objectives, team topology, transformation, or empowered teams — studying the book, or referencing its concepts. |
EMPOWERED: Ordinary People, Extraordinary Products
Author: Marty Cagan with Chris Jones | Pages: ~400 | Chapters: 81 | Generated: 2026-08-10
How to Use This Skill
- Without arguments — load core frameworks for reference
- With a topic — ask about
coaching, objectives, empowerment, onboarding, or another indexed topic; I find and read the relevant chapter
- With chapter — ask for
ch10; I load that specific chapter
- Browse — ask "what chapters do you have?" to see the full index
When you ask about a topic not covered in Core Frameworks below, I will read
the relevant chapter file before answering.
Companion skills: cagan-inspired (INSPIRED) covers product discovery, the four risks, OKRs, and the product team model; EMPOWERED is the leadership/coaching layer on top. cagan-transformed (TRANSFORMED) covers the organization-level transformation to the product operating model — EMPOWERED Part X (ch77–81) and ch79 "TRANSFORMED" are the bridge between the two. Recommended reading order: INSPIRED → EMPOWERED → TRANSFORMED.
Core Frameworks & Mental Models
The Thesis: Empowered Teams vs. Feature Teams
- Empowered product team: cross-functional team (PM + designer + engineers) given a problem to solve, empowered to choose the solution, accountable to results. Feature team: assigned features and projects (output), not accountable. Most companies run feature teams and call it agility (ch01, ch04).
- The five key rules of the product operating model (ch06): missionaries not mercenaries; empowered to solve problems, not implement features; solve problems customers love that work for the business; teams account for commitments; strong product leaders at every level.
- The three roles of product leadership (ch05): staffing (right people, right team, right time), coaching (to competence, then potential), vision/strategy (the why and where). If a leader does one thing well, it's staffing.
- Why great companies win (ch01): it's not talent acquisition — it's how they enable ordinary people to work together: technology as core enabler, strong product leaders, and empowered teams. Get these three right and the rest follows.
- The Sprint Planning Test (ch80): if engineers see a product idea first at sprint planning, it's a feature team. Coding-only engineering captures about half the engineers' value.
Coaching (Part II — the heart of the book)
- Coaching mindset (ch07): the leader's job is developing people to competence, then to potential. If you don't have the will, no technique matters. Bill Campbell: "Leadership is about recognizing that there's a greatness in everyone, and your job is to create an environment where that greatness can emerge."
- The Assessment (ch08): rate each skill (people/process/product taxonomy) on expectations vs. capability, 1–10; gaps weighted by importance; coach only the top three gaps. Table stakes (product knowledge) come first.
- The One-on-One (ch10): the sacred weekly 30-minute session whose only purpose is developing the person — never status updates. Reschedule, never cancel; daily-to-3x weekly during onboarding.
- The Coaching Plan (ch09): the assessment's gaps sequenced into a weekly agenda delivered in the 1:1, with homework and customer visits between sessions; assessed each week. New PMs need ≥15 customer visits before meaningful decisions.
- The Written Narrative (ch11): a few-page persuasive argument (problem, value, strategy) + FAQ anticipating objections, reviewed with objectors before the decision meeting. The canary: executives judge a PM's readiness through her homework.
- The coaching topics (ch12–24): strategic context, sense of ownership, managing time (4 solid hours/day of discovery), thinking, team collaboration, stakeholder collaboration, imposter syndrome, customer-centricity (3 customer interactions/week), integrity (high-integrity commitments), decisions, effective meetings (async first), ethics (the 5th risk: should we build it?), happiness.
Staffing (Part III)
- Competence and character (ch26): hire only people with both; never trade character for skill; never hire for "cultural fit." The No Assholes Rule is non-negotiable.
- Raise the average (ch28): every PM/designer/tech-lead hire must raise the team's average capability — those are not junior roles.
- Always recruiting (ch27): hiring is the manager's day job — minimum 50% of time on an open role; active pursuit like a sports coach, not HR sourcing.
- Onboarding (ch31–32): five checkpoints through day 60 (friend/expectations, team, paycheck, company, 60-day public win); a New Employee Bootcamp (Strategic Context, storytellers, product workshop); APM programs only with proven coaches.
- Terminating (ch34): competence failure → 3–6 months coaching then relocate; toxic → 3–6 months correction then protect the team. Never trade trust for skills.
- Promoting (ch35): promote on demonstrated qualification against a gap list, not on openings; dual tracks keep senior ICs.
Product Vision & Strategy (Parts IV & VI)
- Product vision (ch37–38): inspiring, customer-centric description of the future 3–10 years out — the North Star, the recruiting tool, the driver of architecture and topology. Create it with design and tech leads; the CEO must feel real ownership (she sells it thousands of times). A visiontype (smoke-and-mirrors prototype + video) makes it real.
- Stubborn on vision, flexible on details: share the vision, never the roadmap. Demand is validatable; the solution is a leap of faith — validate the demand, never the solution.
- Product principles (ch39): stated priorities for trade-offs teams can't escalate, written with reasoning at vision creation, with ethics guidance in advance.
- Focus (ch48): 2–3 pivotal objectives, not 20–30 "critical" initiatives. More than a handful is prioritizing, not focusing.
- Insights-driven strategy (ch49): mine four sources — quantitative data, qualitative research, enabling technology, industry/competitive analysis. Generative insights (new opportunities) are the linchpin; a vision pivots only for a larger opportunity, never because problems got hard.
- Actions (ch50): convert strategy to team objectives — problems to solve, never features to build. Management (ch51): servant leadership — weekly 1:1s for obstacles, coaching, escalation; no strategy survives first contact with reality.
Team Objectives (Part VII — the operating system)
- Empowerment (ch53): an objective (problem) + key results (how success is measured), replacing the feature roadmap. 2–4 KRs: one primary + quality guardrails; values and timeframes come from the team, bottom-up; leaders provide direction, top-down.
- Ambition (ch55): label roof shots vs. moon shots vs. confidence %; manage as a portfolio of bets. Moon-shot failure is expected; roof-shot and high-integrity-commitment failure triggers accountability.
- Commitments (ch56): high-integrity commitments are made only after discovery (feasibility prototype included), tracked separately, flagged early — the exception, not the rule.
- Collaboration & accountability (ch57–59): shared objectives cross team boundaries (API contracts); common objectives let teams attack independently; attribute shared results by A/B test or slicing; substantial failure gets a postmortem like an outage.
Team Topology (Part V)
- Optimize for empowerment (ch41): ownership (scope of responsibility incl. trade-offs) + autonomy (few dependencies) + alignment (consistent boundaries). A good topology resolves more ownership questions than it raises.
- Team types (ch42–44): platform teams (best engineers; up to half of teams in big tech) vs. experience teams (end-to-end responsibility); split experience teams by user/segment/journey/channel; keep-the-lights-on (10–50% capacity) separate from objective work.
- Topology evolution (ch45–46): co-locate the cross-functional team over managers/executives/customers; keep teams intact, restructure rarely; beware Conway's Law — don't ship your org chart.
Business Collaboration (Part IX)
- Stakeholders as partners, not clients (ch72): "stakeholder management" is the feature-team mindset; empowered teams collaborate on constraints to discover solutions. If a solution violates a constraint, it's a nonstarter.
- Product leaders at peer level (ch71): product must report to the CEO level, not under CIO/CTO — buried product signals the subservient feature-team model.
- Evangelism (ch75): marketing to your own org — prototypes, shared credit, demos-as-sales, face time; it never stops.
Transformation (Part X)
- The three steps, in order (ch77): 1) strong product leaders, 2) staff to competence, 3) redefine the business relationship. Never empower a team staffed below the task; up-level teams one at a time. Scope transformation to the product operating model (how value is produced), not Agile practices.
- The CFO Test (ch77): a pilot area comparing empowered vs. current model on costs and results — empowered teams cost less and ship more.
- The Destination (ch81): tech-enabled business, coaching culture, empowered accountable teams — audited on nine elements (tech role, coaching, staffing, vision, topology, strategy, objectives, business relationship, empowered teams).
Chapter Index
| # | Chapter |
|---|---------|----------------|
| ch01 | Behind Every Great Company |
| ch02 | The Role of Technology |
| ch03 | Strong Product Leadership |
| ch04 | Empowered Product Teams |
| ch05 | Leadership in Action |
| ch06 | A Guide to EMPOWERED |
| ch07 | The Coaching Mindset |
| ch08 | The Assessment |
| ch09 | The Coaching Plan |
| ch10 | The One-on-One |
| ch11 | The Written Narrative |
| ch12 | Strategic Context |
| ch13 | Sense of Ownership |
| ch14 | Managing Time |
| ch15 | Thinking |
| ch16 | Team Collaboration |
| ch17 | Stakeholder Collaboration |
| ch18 | Imposter Syndrome |
| ch19 | Customer-Centricity |
| ch20 | Integrity |
| ch21 | Decisions |
| ch22 | Effective Meetings |
| ch23 | Ethics |
| ch24 | Happiness |
| ch25 | Leader Profile: Lisa Kavanaugh |
| ch26 | Competence and Character |
| ch27 | Recruiting |
| ch28 | Interviewing |
| ch29 | Hiring |
| ch30 | Remote Employees |
| ch31 | Onboarding |
| ch32 | New Employee Bootcamp |
| ch33 | Performance Reviews |
| ch34 | Terminating |
| ch35 | Promoting |
| ch36 | Leader Profile: April Underwood |
| | Creating a Compelling Vision |
| | Sharing the Product Vision |
| | Product Principles and Ethics |
| | Leader Profile: Audrey Crane |
| | Optimizing for Empowerment |
| | Team Types |
| | Empowering Platform Teams |
| | Empowering Experience Teams |
| | Topology and Proximity |
| | Topology Evolution |
| | Leader Profile: Debby Meredith |
| | Focus |
| | Insights |
| | Actions |
| | Management |
| | Leader Profile: Shan-Lyn Ma |
| | Empowerment |
| | Assignment |
| | Ambition |
| | Commitments |
| | Collaboration |
| | Management |
| | Accountability |
| | Objectives in Perspective |
| | Leader Profile: Christina Wodtke |
| | Case Study: Company Backgrounder |
| | Case Study: Company Objectives |
| | Case Study: Vision & Principles |
| | Case Study: Team Topology |
| | Case Study: Product Strategy |
| | Case Study: Team Objectives |
| | Case Study: Business Results |
| | Case Study: Key Takeaways |
| | Leader Profile: Judy Gibbons |
| | The Role of Product Leaders |
| | Stakeholder vs Shareholder Management |
| | Shared Insights and Learning |
| | Keeping the Lights On |
| | Evangelism |
| | Leader Profile: Avid Larizadeh Duggan |
| | Meaningful Transformation |
| | Transformation in Action |
| | TRANSFORMED |
| | The Most Important Thing |
| | The Destination |
Topic Index
- Accountability → ch59, ch60
- Ambition / roof shots / moon shots → ch55, ch67
- Assessment / gap analysis → ch8, ch9
- Case study (company transformation) → ch62–69
- Coaching → ch7–11
- Commitments / high-integrity commitments → ch20, ch56
- Customer-centricity → ch19, ch52
- Decisions → ch21
- Empowered product teams / feature teams → ch1, ch4, ch6, ch77, ch80
- Ethics → ch23, ch39
- Evangelism → ch75
- Focus → ch48
- Hiring / recruiting / interviewing → ch26–29
- Insights → ch49, ch73
- Keep-the-lights-on (KTLO) → ch43, ch54, ch74
- Meetings → ch22
- Objectives / key results (OKRs) → ch50, ch53–60, ch61
- Onboarding / bootcamp → ch31, ch32
- One-on-one → ch9, ch10
- Ownership → ch13, ch41
- Performance reviews → ch33
- Product principles → ch39
- Product strategy → ch48–51, ch66
- Product vision / visiontype → ch37, ch38, ch64
- Promotion / termination → ch34, ch35
- Remote teams → ch30
- Stakeholders / business collaboration → ch17, ch71–75
- Team topology / platform vs experience teams → ch41–46, ch65
- Technology leadership (CTO/CIO) → ch2
- Time management → ch14
- Transformation → ch77–81
- Written narrative → ch11
Supporting Files
Scope & Limits
This skill covers EMPOWERED only. For product discovery techniques, the four risks,
prototyping, and OKR fundamentals, see the companion cagan-inspired skill (INSPIRED).
For organization-level transformation to the product operating model, see the companion
cagan-transformed skill (TRANSFORMED). For hands-on implementation in your codebase,
combine with project-specific tools.
