product-leadership
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseProduct 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-strategyproduct-discoveryproduct-architectureproduct-deliveryai-native-product"你的工作不再是打造产品,而是打造能够打造产品的团队和体系。"
本技能涵盖产品领导力——适用于总监、副总裁或CPO层级的工作方法。内容涉及产品组合管理、高管对齐、董事会沟通、团队架构设计,以及支撑产品组织规模化发展的运营节奏。
所属系列:Modern Product Operating Model —— 一套可组合的产品技能集合。
相关技能:, , , ,
product-strategyproduct-discoveryproduct-architectureproduct-deliveryai-native-productWhen 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
在以下场景中使用本技能:
- 管理多个产品或产品团队
- 使产品战略与公司战略对齐
- 向董事会或高管汇报
- 设计产品团队架构
- 在跨团队间建立运营节奏
- 指导和培养产品经理
- 应对组织内部的政治问题
适用角色:产品总监、产品副总裁、CPO、产品负责人
The Leadership Shift
领导力转型
IC PM vs. Product Leader
个体贡献型PM vs. 产品领导者
| 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 |
| 维度 | 个体贡献型PM | 产品领导者 |
|---|---|---|
| 产出 | 交付功能、推动指标增长 | 打造能交付功能并推动指标增长的团队 |
| 用户探索 | 亲自开展探索工作 | 确保各团队都在开展探索工作 |
| 决策 | 做出产品决策 | 建立保障优质决策的体系 |
| 影响力 | 团队 + 利益相关者 | 整个组织 + 高管 + 董事会 |
| 成功标准 | 负责的产品取得成功 | 下属PM和所有产品都取得成功 |
| 时间视野 | 季度 | 年度 |
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
- 设定方向 —— 产品组合战略、资源分配、确定要做/不做的事情
- 构建能力 —— 招聘、指导、培养PM;建立体系和流程
- 清除障碍 —— 为团队扫清障碍、对齐高管、应对组织政治
Framework Components
框架组件
1. Portfolio Management
1. 产品组合管理
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
产品组合视角
作为领导者,你管理的是一系列产品/赌注,而非单一产品。
┌─────────────────────────────────────────────────────────────────┐
│ PRODUCT PORTFOLIO │
├─────────────────┬─────────────────┬─────────────────┬──────────┤
│ Product A │ Product B │ Product C │ Product D│
│ [Cash Cow] │ [Star] │ [Question] │ [Dog] │
│ Maintain │ Invest │ Decide │ Sunset? │
└─────────────────┴─────────────────┴─────────────────┴──────────┘产品组合分类(BCG矩阵风格)
| 分类 | 特征 | 战略 |
|---|---|---|
| 明星产品 | 高增长、高市场份额 | 大力投入 |
| 现金牛产品 | 低增长、高市场份额 | 维持运营、收割收益 |
| 问题产品 | 高增长、低市场份额 | 投入或剥离 |
| 瘦狗产品 | 低增长、低市场份额 | 淘汰或转型 |
资源分配问题
- 相对于机会而言,我们在哪些领域投入过多/不足?
- 哪些产品值得获得更多资源?哪些应该减少资源?
- 我们会停止做哪些事情来为新项目提供资金?
- 我们的资源是过于分散还是集中得当?
产品组合回顾节奏:季度
2. Executive Alignment
2. 高管对齐
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 |
对齐挑战
产品领导者需要在以下各方之间搭建桥梁:
- 用户需求 ↔ 业务目标
- 团队能力 ↔ 高管期望
- 长期赌注 ↔ 短期压力
利益相关者地图
| 利益相关者 | 关注重点 | 你的工作 |
|---|---|---|
| CEO | 公司战略、重大赌注、竞争地位 | 使产品与公司战略对齐,标记战略选择 |
| CFO | 收入、成本、单位经济效益 | 将产品与财务结果关联起来 |
| CTO | 技术战略、平台健康度、研发效率 | 在自研vs采购、技术投入方面开展合作 |
| 销售团队 | 销售管线、配额、竞争获胜 | 赋能销售,平衡定制化与可扩展性 |
| 营销团队 | 定位、发布、需求生成 | 协调上市(GTM)工作,提供产品叙事 |
| 董事会 | 增长、市场地位、关键指标 | 简化复杂信息,展示进展 |
向上管理原则
- 无意外 —— 尽早标记风险,即使情况令人不适
- 提供选项,而非只提问题 —— 带来解决方案建议
- 用他们的语言沟通 —— 强调业务影响,而非功能细节
- 通过交付建立信任 —— 过往交付记录能带来自主权
- 选择你的战场 —— 并非所有事情都值得升级上报
高管评审格式
| 板块 | 内容 | 时长 |
|---|---|---|
| 进展 | 关键成果、指标变化 | 5分钟 |
| 风险 | 可能出现的问题、缓解措施 | 5分钟 |
| 需要决策的事项 | 需要高管输入的选择 | 10分钟 |
| 展望 | 下一季度优先级 | 5分钟 |
3. Board Communication
3. 董事会沟通
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?"
董事会关注的内容
| 主题 | 董事会可能的问题 | 你的准备工作 |
|---|---|---|
| 增长 | 我们在增长吗?为什么增长/不增长? | 关键指标、趋势、驱动因素 |
| 产品-市场契合度 | 用户是否喜爱我们的产品? | NPS、留存率、拓展情况 |
| 竞争地位 | 我们在竞争中获胜了吗? | 胜率、市场份额 |
| 路线图可信度 | 你们能交付承诺的内容吗? | 交付记录、风险 |
| 团队 | 我们拥有合适的人才吗? | 组织健康度、关键招聘 |
董事会汇报指标(保持简洁)
| 指标 | 重要性 | 目标 |
|---|---|---|
| ARR/收入 | 业务健康度 | [目标值] |
| 增长率 | 发展轨迹 | [目标值]% |
| 留存率 | 产品粘性 | [目标值]% |
| NPS | 用户喜爱度 | [目标值] |
| 激活率 | 新用户成功度 | [目标值]% |
董事会汇报幻灯片原则
- 每张幻灯片传递一个核心信息
- 指标附带上下文(与目标对比、与上期对比)
- 坦诚面对挑战
- 如有需求,明确提出
- 避免行话,不要罗列功能
需准备的常见董事会问题
- “影响达成计划的最大风险是什么?”
- “为什么用户应该选择我们而非[竞争对手]?”
- “如果有更多资源,你会做什么?”
- “什么事情比预期耗时更长,为什么?”
- “最让你夜不能寐的一件事是什么?”
4. Team Structure
4. 团队架构
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)
产品团队模型
| 模型 | 架构 | 适用场景 |
|---|---|---|
| 功能型团队 | 团队负责特定功能领域 | 边界清晰、协调简单 |
| 使命型团队 | 团队负责结果/指标 | 聚焦结果、跨职能 |
| 平台+产品型 | 平台团队为产品团队提供支持 | 规模化、共享基础设施 |
| Pods/Squads(小团队) | 小型自治单元 | 快速、自主 ownership |
团队规模指南
| 团队规模 | 特征 |
|---|---|
| 4-6人 | 紧密、快速,从0到1阶段 |
| 6-10人 | 标准产品团队 |
| 10人以上 | 考虑拆分 |
规模化下的产品三人组
Product Leader
│
┌─────────┼─────────┐
│ │ │
PM A PM B PM C
│ │ │
[Trio] [Trio] [Trio]每个PM领导一个三人组(PM + 设计师 + 技术负责人)。产品领导者指导PM,而非直接指导三人组。
招聘原则
| 级别 | 考察重点 |
|---|---|
| 初级PM | 好奇心、分析能力、沟通能力、可培养性 |
| 高级PM | 过往业绩、战略思维、影响力、自主性 |
| PM主管 | 团队建设、指导能力、系统思维、高管沟通能力 |
PM职业晋升维度
- 范围(功能 → 产品 → 产品组合)
- 复杂度(清晰 → 模糊)
- 影响力(团队 → 组织 → 公司)
- 自主性(受指导 → 独立 → 指导他人)
5. Operating Rhythm
5. 运营节奏
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? |
运营日历
| 频率 | 活动 | 目的 |
|---|---|---|
| 每日 | 团队站会 | 执行对齐 |
| 每周 | PM同步会 | 跨团队协调 |
| 每周 | 与PM的1对1沟通 | 指导、扫清障碍 |
| 每两周 | 产品评审会 | 进展汇报、决策 |
| 每月 | 指标评审会 | 绩效评估 |
| 每季度 | 规划会 | 优先级排序、资源分配 |
| 每季度 | 产品组合回顾会 | 战略对齐 |
| 每年 | 战略更新会 | 方向设定 |
每周PM同步会(60分钟)
| 环节 | 时长 | 目的 |
|---|---|---|
| 成果与经验分享 | 15分钟 | 庆祝成果、共享知识 |
| 跨团队依赖项 | 20分钟 | 扫清障碍、协调工作 |
| 升级上报事项 | 15分钟 | 需要领导者决策的事项 |
| 公告 | 10分钟 | 组织更新、流程变更 |
季度规划流程
| 周数 | 活动 |
|---|---|
| 第-4周 | 收集战略输入(市场、用户、数据) |
| 第-3周 | 领导层对齐优先级 |
| 第-2周 | 团队制定提案 |
| 第-1周 | 评审、协商、最终确定 |
| 第0周 | 沟通并启动 |
与PM的1对1沟通结构
| 主题 | 问题 |
|---|---|
| 进展 | 哪些事情进展顺利?哪些卡住了? |
| 支持需求 | 你需要我提供什么支持? |
| 个人发展 | 你正在学习什么?你希望在哪些方面成长? |
| 战略 | 对方向有任何疑虑吗? |
| 个人状态 | 你近况如何? |
6. Culture & Principles
6. 文化与原则
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
打造产品文化
| 原则 | 具体表现 |
|---|---|
| 用户至上 | 每位PM每周都与用户沟通 |
| 结果优先于产出 | 团队庆祝指标达成,而非仅仅是产品发布 |
| 基于证据 | 决策引用数据或研究结果 |
| 行动导向 | 发布→学习→迭代 优于 无休止规划 |
| 心理安全 | PM可以毫无顾虑地标记风险 |
| 理智诚实 | 我们坦诚说出哪些事情行不通 |
需要纠正的反模式
| 反模式 | 症状 | 解决方法 |
|---|---|---|
| 功能工厂 | 团队只做被要求的功能 | 设定基于结果的目标 |
| PM沦为项目经理 | PM只跟踪任务,不关注战略 | 提升PM角色定位,提供指导 |
| 利益相关者驱动 | 声音最大的人说了算 | 基于证据的优先级排序 |
| 英雄文化 | 依赖个人英雄主义解决问题 | 建立体系和流程 |
| 分析瘫痪 | 无休止研究,不发布产品 | 设定时间盒,发布最小可行版本 |
保护产品团队的时间
作为领导者,保护你的团队免受以下事项干扰:
- 利益相关者的私人项目
- 过多的会议
- 范围蔓延
- 被动救火
- 流程形式主义
7. Coaching PMs
7. 指导PM
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
指导 vs. 指挥
| 指挥 | 指导 |
|---|---|
| “做X” | “你在考虑哪些选项?” |
| “答案是Y” | “数据表明了什么?” |
| “我会做Z” | “你的建议是什么?” |
指导问题
| 场景 | 问题 |
|---|---|
| PM遇到瓶颈 | “你已经尝试了哪些方法?是什么在阻碍你?” |
| PM需要确认 | “你的信心程度如何?什么会改变你的想法?” |
| PM犯了错误 | “你学到了什么?下次你会怎么做?” |
| PM取得成功 | “是什么让这件事成功?你如何复制这种成功?” |
发展沟通
| PM级别 | 聚焦领域 |
|---|---|
| 初级 | 用户探索技能、利益相关者管理、产品交付 |
| 高级 | 战略思维、无权威影响力、应对模糊性 |
| 主管 | 团队建设、指导他人、高管沟通 |
反馈框架
- 场景:具体发生了什么
- 行为:PM做了什么
- 影响:对结果的影响
- 请求/建议:如何改进
Templates
模板
This skill includes templates in the directory:
templates/- — Quarterly portfolio assessment
portfolio-review.md - — Board-ready metrics summary
board-metrics.md - — Annual operating calendar
operating-rhythm.md - — PM coaching and development plan
pm-development.md
本技能在目录中包含以下模板:
templates/- —— 季度产品组合评估模板
portfolio-review.md - —— 适用于董事会的指标汇总模板
board-metrics.md - —— 年度运营日历模板
operating-rhythm.md - —— PM指导与发展计划模板
pm-development.md
Using This Skill with Claude
与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]?"
你可以让Claude:
- 设计产品组合战略:“帮我评估我的产品组合和资源分配”
- 准备董事会汇报材料:“针对[场景],我的董事会更新应该包含哪些内容?”
- 搭建团队架构:“针对[X名PM,Y个产品],我应该如何搭建产品团队?”
- 建立运营节奏:“为[规模]的产品组织设计运营节奏”
- 规划季度工作:“帮我设计季度规划流程”
- 指导PM:“如何指导在[问题]上遇到困难的PM?”
- 处理利益相关者:“如何管理想要[需求]的[利益相关者类型]?”
- 准备高管评审:“帮我搭建高管产品评审的结构”
- 打造文化:“哪些实践能打造强大的产品文化?”
- 应对组织政治:“如何处理[组织挑战]?”
Connection to Other Skills
与其他技能的关联
| When you need to... | Use skill |
|---|---|
| Define product strategy | |
| Ensure discovery practices | |
| Review roadmaps and bets | |
| Assess delivery health | |
| Guide AI product teams | |
| 当你需要... | 使用技能 |
|---|---|
| 定义产品战略 | |
| 确保用户探索实践 | |
| 评审路线图和赌注 | |
| 评估交付健康度 | |
| 指导AI产品团队 | |
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
每周:
- 与所有直接下属进行1对1沟通
- 完成PM同步会
- 解决跨团队障碍
- 维护与高管的沟通触点
每月:
- 与团队一起评审指标
- 开展发展沟通
- 维护与利益相关者的关系
- 评估产品组合健康度
每季度:
- 完成规划工作
- 完成产品组合回顾
- 准备好董事会材料
- 推动团队回顾
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
- Marty Cagan —— 《EMPOWERED》、《INSPIRED》
- Melissa Perri —— 《Escaping the Build Trap》
- Julie Zhuo —— 《The Making of a Manager》
- Gibson Biddle —— PM领导力框架
- Lenny Rachitsky —— PM研究与访谈
属于Yannick Maurice的Modern Product Operating Model系列内容