product-leadership

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. Part of the Modern Product Operating Model collection.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "product-leadership" with this command: npx skills add yannickyamo/skills/yannickyamo-skills-product-leadership

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.

Part of: Modern Product Operating Model — a collection of composable product skills.

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

DimensionIC PMProduct Leader
OutputShip features, move metricsBuild teams that ship and move metrics
DiscoveryDo discoveryEnsure discovery happens across teams
DecisionsMake product decisionsCreate systems for good decisions
InfluenceTeam + stakeholdersOrganization + executives + board
SuccessYour product winsYour PMs and products win
Time horizonQuartersYears

The Three Jobs of Product Leadership

  1. Set Direction — Portfolio strategy, resource allocation, what to build/not build
  2. Build Capability — Hire, coach, develop PMs; establish systems and processes
  3. Remove Obstacles — Unblock teams, align executives, navigate politics

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)

CategoryCharacteristicsStrategy
StarsHigh growth, high shareInvest heavily
Cash CowsLow growth, high shareMaintain, harvest
Question MarksHigh growth, low shareInvest or divest
DogsLow growth, low shareSunset 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

StakeholderCares AboutYour Job
CEOCompany strategy, major bets, competitive positionAlign product to company strategy, flag strategic choices
CFORevenue, costs, unit economicsConnect product to financial outcomes
CTOTechnical strategy, platform health, eng efficiencyPartner on build vs. buy, technical investments
SalesPipeline, quota, competitive winsEnable sales, balance custom vs. scalable
MarketingPositioning, launches, demand genCoordinate GTM, provide product narrative
BoardGrowth, market position, key metricsSimplify complexity, show progress

Managing Up Principles

  1. No surprises — Flag risks early, even if uncomfortable
  2. Options, not just problems — Bring recommendations
  3. Translate to their language — Business impact, not feature details
  4. Build trust through delivery — Track record enables autonomy
  5. Pick your battles — Not everything is worth escalating

Executive Review Format

SectionContentTime
ProgressKey wins, metrics moved5 min
RisksWhat could go wrong, mitigation5 min
Decisions neededChoices requiring exec input10 min
Forward lookNext quarter priorities5 min

3. Board Communication

What Boards Care About

TopicBoard QuestionYour Preparation
GrowthAre we growing? Why/why not?Key metrics, trend, drivers
Product-market fitDo customers love it?NPS, retention, expansion
Competitive positionAre we winning?Win rates, market share
Roadmap confidenceWill you deliver?Track record, risks
TeamDo we have the right people?Org health, key hires

Board Metrics (Keep Simple)

MetricWhy It MattersTarget
ARR/RevenueBusiness health[Target]
Growth rateTrajectory[Target]%
RetentionProduct stickiness[Target]%
NPSCustomer love[Target]
ActivationNew 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

ModelStructureBest For
Feature teamsTeam owns feature areaClear boundaries, simple coordination
Mission teamsTeam owns outcome/metricOutcome focus, cross-functional
Platform + ProductPlatform serves product teamsScale, shared infrastructure
Pods/SquadsSmall autonomous unitsSpeed, ownership

Team Sizing Guidelines

Team SizeCharacteristics
4-6Tight, fast, 0→1 mode
6-10Standard 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

LevelLook For
Junior PMCuriosity, analytical ability, communication, coachability
Senior PMTrack record, strategic thinking, influence, autonomy
PM LeadTeam 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

CadenceActivityPurpose
DailyStandups (teams)Execution alignment
WeeklyPM syncCross-team coordination
Weekly1:1s with PMsCoaching, unblocking
Bi-weeklyProduct reviewProgress, decisions
MonthlyMetrics reviewPerformance assessment
QuarterlyPlanningPrioritization, resourcing
QuarterlyPortfolio reviewStrategic alignment
AnnuallyStrategy refreshDirection setting

Weekly PM Sync (60 min)

SegmentTimePurpose
Wins & learnings15 minCelebrate, share knowledge
Cross-team dependencies20 minUnblock, coordinate
Escalations15 minDecisions needed from leader
Announcements10 minOrg updates, process changes

Quarterly Planning Process

WeekActivity
Week -4Strategy inputs gathered (market, customers, data)
Week -3Leadership alignment on priorities
Week -2Teams develop proposals
Week -1Review, negotiate, finalize
Week 0Communicate and kick off

1:1 Structure with PMs

TopicQuestions
ProgressWhat's going well? What's stuck?
SupportWhat do you need from me?
DevelopmentWhat are you learning? Where do you want to grow?
StrategyAny concerns about direction?
PersonalHow are you doing?

6. Culture & Principles

Building Product Culture

PrincipleWhat It Looks Like
Customer obsessionEvery PM talks to customers weekly
Outcome over outputTeams celebrate metrics, not launches
Evidence-basedDecisions cite data or research
Bias to actionShip → learn → iterate beats planning
Psychological safetyPMs can flag risks without fear
Intellectual honestyWe say what's not working

Anti-Patterns to Fix

Anti-PatternSymptomFix
Feature factoryTeams build what's requestedOutcome-based goals
PM as project managerPMs track tasks, not strategyElevate PM role, coach
Stakeholder-drivenLoudest voice winsEvidence-based prioritization
Hero cultureIndividual heroics save the daySystems and processes
Analysis paralysisEndless research, no shippingTimeboxes, 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

DirectingCoaching
"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

SituationQuestions
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 LevelFocus Areas
JuniorDiscovery skills, stakeholder management, shipping
SeniorStrategic thinking, influence without authority, ambiguity
LeadTeam building, coaching others, exec communication

Feedback Framework

  1. Situation: What happened (specific)
  2. Behavior: What the PM did
  3. Impact: Effect on outcome
  4. 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:

  1. Design portfolio strategy: "Help me assess my product portfolio and resource allocation"
  2. Prepare board deck: "What should I include in my board update for [situation]?"
  3. Structure team: "How should I structure my product team for [X PMs, Y products]?"
  4. Create operating rhythm: "Design an operating rhythm for a [size] product org"
  5. Plan quarterly: "Help me design a quarterly planning process"
  6. Coach PM: "How should I coach a PM who is struggling with [issue]?"
  7. Handle stakeholder: "How do I manage [stakeholder type] who wants [request]?"
  8. Prepare exec review: "Help me structure an executive product review"
  9. Build culture: "What practices build a strong product culture?"
  10. Navigate politics: "How do I handle [organizational challenge]?"

Connection to Other Skills

When you need to...Use skill
Define product strategyproduct-strategy
Ensure discovery practicesproduct-discovery
Review roadmaps and betsproduct-architecture
Assess delivery healthproduct-delivery
Guide AI product teamsai-native-product

Quick Reference: Leadership Checklist

Weekly:

  • 1:1s with all direct reports
  • PM sync completed
  • Cross-team blockers addressed
  • Exec touchpoints maintained

Monthly:

  • Metrics reviewed with team
  • Development conversations held
  • Stakeholder relationships maintained
  • Portfolio health assessed

Quarterly:

  • Planning completed
  • Portfolio review done
  • Board materials prepared
  • Team retro facilitated

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

Part of the Modern Product Operating Model by Yannick Maurice

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

General

product-architecture

No summary provided by upstream source.

Repository SourceNeeds Review
General

product-operating-model

No summary provided by upstream source.

Repository SourceNeeds Review
General

ai-native-product

No summary provided by upstream source.

Repository SourceNeeds Review
General

product-strategy

No summary provided by upstream source.

Repository SourceNeeds Review