Product Leadership
"Your job is no longer to build products. It's to build the teams and systems that build products."
This skill covers Product Leadership — the overlay for operating at Director, VP, or CPO level. It addresses portfolio management, executive alignment, board communication, team structure, and the operating rhythms that scale product organizations.
Related skills: product-strategy, product-discovery, product-architecture, product-delivery, ai-native-product
When to Use This Skill
Use this skill when:
- Managing multiple products or product teams
- Aligning product strategy with company strategy
- Communicating to board or executives
- Designing product team structure
- Establishing operating rhythms across teams
- Coaching and developing product managers
- Navigating organizational politics
Role scope: Director, VP Product, CPO, Head of Product
The Leadership Shift
IC PM vs. Product Leader
| Dimension |
IC PM |
Product Leader |
| Output |
Ship features, move metrics |
Build teams that ship and move metrics |
| Discovery |
Do discovery |
Ensure discovery happens across teams |
| Decisions |
Make product decisions |
Create systems for good decisions |
| Influence |
Team + stakeholders |
Organization + executives + board |
| Success |
Your product wins |
Your PMs and products win |
| Time horizon |
Quarters |
Years |
The Three Jobs of Product Leadership
- Set Direction — Portfolio strategy, resource allocation, what to build/not build
- Build Capability — Hire, coach, develop PMs; establish systems and processes
- Remove Obstacles — Unblock teams, align executives, navigate politics
Progress Tracking
Display progress during leadership work:
[████░░░░░░░░░░░░░░░░] 25% — Phase 1/4: Portfolio Assessment & Team Structure
[████████░░░░░░░░░░░░] 50% — Phase 2/4: Executive Alignment & Communication
[████████████░░░░░░░░] 75% — Phase 3/4: Operating Rhythm Design
[████████████████████] 100% — Phase 4/4: Board/Stakeholder Readout
Framework Components
1. Portfolio Management
The Portfolio View
As a leader, you manage a portfolio of products/bets, not a single product.
┌─────────────────────────────────────────────────────────────────┐
│ PRODUCT PORTFOLIO │
├─────────────────┬─────────────────┬─────────────────┬──────────┤
│ Product A │ Product B │ Product C │ Product D│
│ [Cash Cow] │ [Star] │ [Question] │ [Dog] │
│ Maintain │ Invest │ Decide │ Sunset? │
└─────────────────┴─────────────────┴─────────────────┴──────────┘
Portfolio Categories (BCG-style)
| Category |
Characteristics |
Strategy |
| Stars |
High growth, high share |
Invest heavily |
| Cash Cows |
Low growth, high share |
Maintain, harvest |
| Question Marks |
High growth, low share |
Invest or divest |
| Dogs |
Low growth, low share |
Sunset or pivot |
Resource Allocation Questions
- Where are we over/under-invested relative to opportunity?
- Which products deserve more resources? Fewer?
- What would we stop doing to fund something new?
- Are we spreading too thin or concentrating appropriately?
Portfolio Review Cadence: Quarterly
2. Executive Alignment
The Alignment Challenge
Product leaders translate between:
- Customer needs ↔ Business objectives
- Team capabilities ↔ Executive expectations
- Long-term bets ↔ Short-term pressures
Stakeholder Map
| Stakeholder |
Cares About |
Your Job |
| CEO |
Company strategy, major bets, competitive position |
Align product to company strategy, flag strategic choices |
| CFO |
Revenue, costs, unit economics |
Connect product to financial outcomes |
| CTO |
Technical strategy, platform health, eng efficiency |
Partner on build vs. buy, technical investments |
| Sales |
Pipeline, quota, competitive wins |
Enable sales, balance custom vs. scalable |
| Marketing |
Positioning, launches, demand gen |
Coordinate GTM, provide product narrative |
| Board |
Growth, market position, key metrics |
Simplify complexity, show progress |
Managing Up Principles
- No surprises — Flag risks early, even if uncomfortable
- Options, not just problems — Bring recommendations
- Translate to their language — Business impact, not feature details
- Build trust through delivery — Track record enables autonomy
- Pick your battles — Not everything is worth escalating
Executive Review Format
| Section |
Content |
Time |
| Progress |
Key wins, metrics moved |
5 min |
| Risks |
What could go wrong, mitigation |
5 min |
| Decisions needed |
Choices requiring exec input |
10 min |
| Forward look |
Next quarter priorities |
5 min |
3. Board Communication
What Boards Care About
| Topic |
Board Question |
Your Preparation |
| Growth |
Are we growing? Why/why not? |
Key metrics, trend, drivers |
| Product-market fit |
Do customers love it? |
NPS, retention, expansion |
| Competitive position |
Are we winning? |
Win rates, market share |
| Roadmap confidence |
Will you deliver? |
Track record, risks |
| Team |
Do we have the right people? |
Org health, key hires |
Board Metrics (Keep Simple)
| Metric |
Why It Matters |
Target |
| ARR/Revenue |
Business health |
[Target] |
| Growth rate |
Trajectory |
[Target]% |
| Retention |
Product stickiness |
[Target]% |
| NPS |
Customer love |
[Target] |
| Activation |
New user success |
[Target]% |
Board Slide Principles
- One message per slide
- Metrics with context (vs. target, vs. last period)
- Honest about challenges
- Clear asks if any
- No jargon, no feature lists
Common Board Questions to Prepare For
- "What's the biggest risk to hitting plan?"
- "Why should customers choose us over [competitor]?"
- "What would you do with more resources?"
- "What's taking longer than expected and why?"
- "What's the one thing keeping you up at night?"
4. Team Structure
Product Team Models
| Model |
Structure |
Best For |
| Feature teams |
Team owns feature area |
Clear boundaries, simple coordination |
| Mission teams |
Team owns outcome/metric |
Outcome focus, cross-functional |
| Platform + Product |
Platform serves product teams |
Scale, shared infrastructure |
| Pods/Squads |
Small autonomous units |
Speed, ownership |
Team Sizing Guidelines
| Team Size |
Characteristics |
| 4-6 |
Tight, fast, 0→1 mode |
| 6-10 |
Standard product team |
| 10+ |
Consider splitting |
The Product Trio at Scale
Product Leader
│
┌─────────┼─────────┐
│ │ │
PM A PM B PM C
│ │ │
[Trio] [Trio] [Trio]
Each PM leads a trio (PM + Designer + Tech Lead). Product Leader coaches PMs, not trios directly.
Hiring Principles
| Level |
Look For |
| Junior PM |
Curiosity, analytical ability, communication, coachability |
| Senior PM |
Track record, strategic thinking, influence, autonomy |
| PM Lead |
Team building, coaching, systems thinking, exec presence |
PM Career Ladder Dimensions
- Scope (feature → product → portfolio)
- Complexity (clear → ambiguous)
- Influence (team → org → company)
- Autonomy (guided → independent → guiding others)
5. Operating Rhythm
The Operating Calendar
| Cadence |
Activity |
Purpose |
| Daily |
Standups (teams) |
Execution alignment |
| Weekly |
PM sync |
Cross-team coordination |
| Weekly |
1:1s with PMs |
Coaching, unblocking |
| Bi-weekly |
Product review |
Progress, decisions |
| Monthly |
Metrics review |
Performance assessment |
| Quarterly |
Planning |
Prioritization, resourcing |
| Quarterly |
Portfolio review |
Strategic alignment |
| Annually |
Strategy refresh |
Direction setting |
Weekly PM Sync (60 min)
| Segment |
Time |
Purpose |
| Wins & learnings |
15 min |
Celebrate, share knowledge |
| Cross-team dependencies |
20 min |
Unblock, coordinate |
| Escalations |
15 min |
Decisions needed from leader |
| Announcements |
10 min |
Org updates, process changes |
Quarterly Planning Process
| Week |
Activity |
| Week -4 |
Strategy inputs gathered (market, customers, data) |
| Week -3 |
Leadership alignment on priorities |
| Week -2 |
Teams develop proposals |
| Week -1 |
Review, negotiate, finalize |
| Week 0 |
Communicate and kick off |
1:1 Structure with PMs
| Topic |
Questions |
| Progress |
What's going well? What's stuck? |
| Support |
What do you need from me? |
| Development |
What are you learning? Where do you want to grow? |
| Strategy |
Any concerns about direction? |
| Personal |
How are you doing? |
6. Culture & Principles
Building Product Culture
| Principle |
What It Looks Like |
| Customer obsession |
Every PM talks to customers weekly |
| Outcome over output |
Teams celebrate metrics, not launches |
| Evidence-based |
Decisions cite data or research |
| Bias to action |
Ship → learn → iterate beats planning |
| Psychological safety |
PMs can flag risks without fear |
| Intellectual honesty |
We say what's not working |
Anti-Patterns to Fix
| Anti-Pattern |
Symptom |
Fix |
| Feature factory |
Teams build what's requested |
Outcome-based goals |
| PM as project manager |
PMs track tasks, not strategy |
Elevate PM role, coach |
| Stakeholder-driven |
Loudest voice wins |
Evidence-based prioritization |
| Hero culture |
Individual heroics save the day |
Systems and processes |
| Analysis paralysis |
Endless research, no shipping |
Timeboxes, thin slices |
Defending Product Time
As leader, protect your teams from:
- Stakeholder pet projects
- Excessive meetings
- Scope creep
- Reactive firefighting
- Process theater
7. Coaching PMs
Coaching vs. Directing
| Directing |
Coaching |
| "Do X" |
"What options are you considering?" |
| "The answer is Y" |
"What does the data suggest?" |
| "I would do Z" |
"What's your recommendation?" |
Coaching Questions
| Situation |
Questions |
| PM is stuck |
"What have you tried? What's blocking you?" |
| PM wants validation |
"What's your conviction level? What would change your mind?" |
| PM made a mistake |
"What did you learn? What would you do differently?" |
| PM is succeeding |
"What made this work? How can you replicate it?" |
Development Conversations
| PM Level |
Focus Areas |
| Junior |
Discovery skills, stakeholder management, shipping |
| Senior |
Strategic thinking, influence without authority, ambiguity |
| Lead |
Team building, coaching others, exec communication |
Feedback Framework
- Situation: What happened (specific)
- Behavior: What the PM did
- Impact: Effect on outcome
- Request/Suggestion: What to do differently
Templates
This skill includes templates in the templates/ directory:
portfolio-review.md — Quarterly portfolio assessment
board-metrics.md — Board-ready metrics summary
operating-rhythm.md — Annual operating calendar
pm-development.md — PM coaching and development plan
Using This Skill with Claude
Ask Claude to:
- Design portfolio strategy: "Help me assess my product portfolio and resource allocation"
- Prepare board deck: "What should I include in my board update for [situation]?"
- Structure team: "How should I structure my product team for [X PMs, Y products]?"
- Create operating rhythm: "Design an operating rhythm for a [size] product org"
- Plan quarterly: "Help me design a quarterly planning process"
- Coach PM: "How should I coach a PM who is struggling with [issue]?"
- Handle stakeholder: "How do I manage [stakeholder type] who wants [request]?"
- Prepare exec review: "Help me structure an executive product review"
- Build culture: "What practices build a strong product culture?"
- Navigate politics: "How do I handle [organizational challenge]?"
Connection to Other Skills
| When you need to... |
Use skill |
| Define product strategy |
product-strategy |
| Ensure discovery practices |
product-discovery |
| Review roadmaps and bets |
product-architecture |
| Assess delivery health |
product-delivery |
| Guide AI product teams |
ai-native-product |
Quick Reference: Leadership Checklist
Weekly:
Monthly:
Quarterly:
Sources & Influences
- Marty Cagan — EMPOWERED, INSPIRED
- Melissa Perri — Escaping the Build Trap
- Julie Zhuo — The Making of a Manager
- Gibson Biddle — PM leadership frameworks
- Lenny Rachitsky — PM research and interviews
1---2name: product-leadership3description: This skill should be used when the user needs to operate as a Director or CPO leading product organizations. Use when managing product portfolios, aligning with executives, communicating to boards, designing team structures, or establishing operating rhythms across product teams.4license: MIT5---67# Product Leadership89> "Your job is no longer to build products. It's to build the teams and systems that build products."1011This skill covers **Product Leadership** — the overlay for operating at Director, VP, or CPO level. It addresses portfolio management, executive alignment, board communication, team structure, and the operating rhythms that scale product organizations.121314**Related skills**: `product-strategy`, `product-discovery`, `product-architecture`, `product-delivery`, `ai-native-product`1516---1718## When to Use This Skill1920Use this skill when:21- Managing multiple products or product teams22- Aligning product strategy with company strategy23- Communicating to board or executives24- Designing product team structure25- Establishing operating rhythms across teams26- Coaching and developing product managers27- Navigating organizational politics2829**Role scope**: Director, VP Product, CPO, Head of Product3031---3233## The Leadership Shift3435### IC PM vs. Product Leader3637| Dimension | IC PM | Product Leader |38|-----------|-------|----------------|39| **Output** | Ship features, move metrics | Build teams that ship and move metrics |40| **Discovery** | Do discovery | Ensure discovery happens across teams |41| **Decisions** | Make product decisions | Create systems for good decisions |42| **Influence** | Team + stakeholders | Organization + executives + board |43| **Success** | Your product wins | Your PMs and products win |44| **Time horizon** | Quarters | Years |4546### The Three Jobs of Product Leadership47481. **Set Direction** — Portfolio strategy, resource allocation, what to build/not build492. **Build Capability** — Hire, coach, develop PMs; establish systems and processes503. **Remove Obstacles** — Unblock teams, align executives, navigate politics5152---5354## Progress Tracking5556Display progress during leadership work:5758```59[████░░░░░░░░░░░░░░░░] 25% — Phase 1/4: Portfolio Assessment & Team Structure60[████████░░░░░░░░░░░░] 50% — Phase 2/4: Executive Alignment & Communication61[████████████░░░░░░░░] 75% — Phase 3/4: Operating Rhythm Design62[████████████████████] 100% — Phase 4/4: Board/Stakeholder Readout63```6465## Framework Components6667### 1. Portfolio Management6869**The Portfolio View**7071As a leader, you manage a portfolio of products/bets, not a single product.7273```74┌─────────────────────────────────────────────────────────────────┐75│ PRODUCT PORTFOLIO │76├─────────────────┬─────────────────┬─────────────────┬──────────┤77│ Product A │ Product B │ Product C │ Product D│78│ [Cash Cow] │ [Star] │ [Question] │ [Dog] │79│ Maintain │ Invest │ Decide │ Sunset? │80└─────────────────┴─────────────────┴─────────────────┴──────────┘81```8283**Portfolio Categories (BCG-style)**8485| Category | Characteristics | Strategy |86|----------|-----------------|----------|87| **Stars** | High growth, high share | Invest heavily |88| **Cash Cows** | Low growth, high share | Maintain, harvest |89| **Question Marks** | High growth, low share | Invest or divest |90| **Dogs** | Low growth, low share | Sunset or pivot |9192**Resource Allocation Questions**9394- Where are we over/under-invested relative to opportunity?95- Which products deserve more resources? Fewer?96- What would we stop doing to fund something new?97- Are we spreading too thin or concentrating appropriately?9899**Portfolio Review Cadence**: Quarterly100101---102103### 2. Executive Alignment104105**The Alignment Challenge**106107Product leaders translate between:108- Customer needs ↔ Business objectives109- Team capabilities ↔ Executive expectations110- Long-term bets ↔ Short-term pressures111112**Stakeholder Map**113114| Stakeholder | Cares About | Your Job |115|-------------|-------------|----------|116| **CEO** | Company strategy, major bets, competitive position | Align product to company strategy, flag strategic choices |117| **CFO** | Revenue, costs, unit economics | Connect product to financial outcomes |118| **CTO** | Technical strategy, platform health, eng efficiency | Partner on build vs. buy, technical investments |119| **Sales** | Pipeline, quota, competitive wins | Enable sales, balance custom vs. scalable |120| **Marketing** | Positioning, launches, demand gen | Coordinate GTM, provide product narrative |121| **Board** | Growth, market position, key metrics | Simplify complexity, show progress |122123**Managing Up Principles**1241251. **No surprises** — Flag risks early, even if uncomfortable1262. **Options, not just problems** — Bring recommendations1273. **Translate to their language** — Business impact, not feature details1284. **Build trust through delivery** — Track record enables autonomy1295. **Pick your battles** — Not everything is worth escalating130131**Executive Review Format**132133| Section | Content | Time |134|---------|---------|------|135| Progress | Key wins, metrics moved | 5 min |136| Risks | What could go wrong, mitigation | 5 min |137| Decisions needed | Choices requiring exec input | 10 min |138| Forward look | Next quarter priorities | 5 min |139140---141142### 3. Board Communication143144**What Boards Care About**145146| Topic | Board Question | Your Preparation |147|-------|----------------|------------------|148| **Growth** | Are we growing? Why/why not? | Key metrics, trend, drivers |149| **Product-market fit** | Do customers love it? | NPS, retention, expansion |150| **Competitive position** | Are we winning? | Win rates, market share |151| **Roadmap confidence** | Will you deliver? | Track record, risks |152| **Team** | Do we have the right people? | Org health, key hires |153154**Board Metrics (Keep Simple)**155156| Metric | Why It Matters | Target |157|--------|----------------|--------|158| **ARR/Revenue** | Business health | [Target] |159| **Growth rate** | Trajectory | [Target]% |160| **Retention** | Product stickiness | [Target]% |161| **NPS** | Customer love | [Target] |162| **Activation** | New user success | [Target]% |163164**Board Slide Principles**165166- One message per slide167- Metrics with context (vs. target, vs. last period)168- Honest about challenges169- Clear asks if any170- No jargon, no feature lists171172**Common Board Questions to Prepare For**173174- "What's the biggest risk to hitting plan?"175- "Why should customers choose us over [competitor]?"176- "What would you do with more resources?"177- "What's taking longer than expected and why?"178- "What's the one thing keeping you up at night?"179180---181182### 4. Team Structure183184**Product Team Models**185186| Model | Structure | Best For |187|-------|-----------|----------|188| **Feature teams** | Team owns feature area | Clear boundaries, simple coordination |189| **Mission teams** | Team owns outcome/metric | Outcome focus, cross-functional |190| **Platform + Product** | Platform serves product teams | Scale, shared infrastructure |191| **Pods/Squads** | Small autonomous units | Speed, ownership |192193**Team Sizing Guidelines**194195| Team Size | Characteristics |196|-----------|-----------------|197| **4-6** | Tight, fast, 0→1 mode |198| **6-10** | Standard product team |199| **10+** | Consider splitting |200201**The Product Trio at Scale**202203```204 Product Leader205 │206 ┌─────────┼─────────┐207 │ │ │208 PM A PM B PM C209 │ │ │210 [Trio] [Trio] [Trio]211```212213Each PM leads a trio (PM + Designer + Tech Lead). Product Leader coaches PMs, not trios directly.214215**Hiring Principles**216217| Level | Look For |218|-------|----------|219| **Junior PM** | Curiosity, analytical ability, communication, coachability |220| **Senior PM** | Track record, strategic thinking, influence, autonomy |221| **PM Lead** | Team building, coaching, systems thinking, exec presence |222223**PM Career Ladder Dimensions**224225- Scope (feature → product → portfolio)226- Complexity (clear → ambiguous)227- Influence (team → org → company)228- Autonomy (guided → independent → guiding others)229230---231232### 5. Operating Rhythm233234**The Operating Calendar**235236| Cadence | Activity | Purpose |237|---------|----------|---------|238| **Daily** | Standups (teams) | Execution alignment |239| **Weekly** | PM sync | Cross-team coordination |240| **Weekly** | 1:1s with PMs | Coaching, unblocking |241| **Bi-weekly** | Product review | Progress, decisions |242| **Monthly** | Metrics review | Performance assessment |243| **Quarterly** | Planning | Prioritization, resourcing |244| **Quarterly** | Portfolio review | Strategic alignment |245| **Annually** | Strategy refresh | Direction setting |246247**Weekly PM Sync (60 min)**248249| Segment | Time | Purpose |250|---------|------|---------|251| Wins & learnings | 15 min | Celebrate, share knowledge |252| Cross-team dependencies | 20 min | Unblock, coordinate |253| Escalations | 15 min | Decisions needed from leader |254| Announcements | 10 min | Org updates, process changes |255256**Quarterly Planning Process**257258| Week | Activity |259|------|----------|260| Week -4 | Strategy inputs gathered (market, customers, data) |261| Week -3 | Leadership alignment on priorities |262| Week -2 | Teams develop proposals |263| Week -1 | Review, negotiate, finalize |264| Week 0 | Communicate and kick off |265266**1:1 Structure with PMs**267268| Topic | Questions |269|-------|-----------|270| **Progress** | What's going well? What's stuck? |271| **Support** | What do you need from me? |272| **Development** | What are you learning? Where do you want to grow? |273| **Strategy** | Any concerns about direction? |274| **Personal** | How are you doing? |275276---277278### 6. Culture & Principles279280**Building Product Culture**281282| Principle | What It Looks Like |283|-----------|-------------------|284| **Customer obsession** | Every PM talks to customers weekly |285| **Outcome over output** | Teams celebrate metrics, not launches |286| **Evidence-based** | Decisions cite data or research |287| **Bias to action** | Ship → learn → iterate beats planning |288| **Psychological safety** | PMs can flag risks without fear |289| **Intellectual honesty** | We say what's not working |290291**Anti-Patterns to Fix**292293| Anti-Pattern | Symptom | Fix |294|--------------|---------|-----|295| **Feature factory** | Teams build what's requested | Outcome-based goals |296| **PM as project manager** | PMs track tasks, not strategy | Elevate PM role, coach |297| **Stakeholder-driven** | Loudest voice wins | Evidence-based prioritization |298| **Hero culture** | Individual heroics save the day | Systems and processes |299| **Analysis paralysis** | Endless research, no shipping | Timeboxes, thin slices |300301**Defending Product Time**302303As leader, protect your teams from:304- Stakeholder pet projects305- Excessive meetings306- Scope creep307- Reactive firefighting308- Process theater309310---311312### 7. Coaching PMs313314**Coaching vs. Directing**315316| Directing | Coaching |317|-----------|----------|318| "Do X" | "What options are you considering?" |319| "The answer is Y" | "What does the data suggest?" |320| "I would do Z" | "What's your recommendation?" |321322**Coaching Questions**323324| Situation | Questions |325|-----------|-----------|326| **PM is stuck** | "What have you tried? What's blocking you?" |327| **PM wants validation** | "What's your conviction level? What would change your mind?" |328| **PM made a mistake** | "What did you learn? What would you do differently?" |329| **PM is succeeding** | "What made this work? How can you replicate it?" |330331**Development Conversations**332333| PM Level | Focus Areas |334|----------|-------------|335| **Junior** | Discovery skills, stakeholder management, shipping |336| **Senior** | Strategic thinking, influence without authority, ambiguity |337| **Lead** | Team building, coaching others, exec communication |338339**Feedback Framework**3403411. **Situation**: What happened (specific)3422. **Behavior**: What the PM did3433. **Impact**: Effect on outcome3444. **Request/Suggestion**: What to do differently345346---347348## Templates349350This skill includes templates in the `templates/` directory:351- `portfolio-review.md` — Quarterly portfolio assessment352- `board-metrics.md` — Board-ready metrics summary353- `operating-rhythm.md` — Annual operating calendar354- `pm-development.md` — PM coaching and development plan355356---357358## Using This Skill with Claude359360Ask Claude to:3613621. **Design portfolio strategy**: "Help me assess my product portfolio and resource allocation"3632. **Prepare board deck**: "What should I include in my board update for [situation]?"3643. **Structure team**: "How should I structure my product team for [X PMs, Y products]?"3654. **Create operating rhythm**: "Design an operating rhythm for a [size] product org"3665. **Plan quarterly**: "Help me design a quarterly planning process"3676. **Coach PM**: "How should I coach a PM who is struggling with [issue]?"3687. **Handle stakeholder**: "How do I manage [stakeholder type] who wants [request]?"3698. **Prepare exec review**: "Help me structure an executive product review"3709. **Build culture**: "What practices build a strong product culture?"37110. **Navigate politics**: "How do I handle [organizational challenge]?"372373---374375## Connection to Other Skills376377| When you need to... | Use skill |378|---------------------|-----------|379| Define product strategy | `product-strategy` |380| Ensure discovery practices | `product-discovery` |381| Review roadmaps and bets | `product-architecture` |382| Assess delivery health | `product-delivery` |383| Guide AI product teams | `ai-native-product` |384385---386387## Quick Reference: Leadership Checklist388389Weekly:390- [ ] 1:1s with all direct reports391- [ ] PM sync completed392- [ ] Cross-team blockers addressed393- [ ] Exec touchpoints maintained394395Monthly:396- [ ] Metrics reviewed with team397- [ ] Development conversations held398- [ ] Stakeholder relationships maintained399- [ ] Portfolio health assessed400401Quarterly:402- [ ] Planning completed403- [ ] Portfolio review done404- [ ] Board materials prepared405- [ ] Team retro facilitated406407---408409## Sources & Influences410411- **Marty Cagan** — EMPOWERED, INSPIRED412- **Melissa Perri** — Escaping the Build Trap413- **Julie Zhuo** — The Making of a Manager414- **Gibson Biddle** — PM leadership frameworks415- **Lenny Rachitsky** — PM research and interviews416417---418