leadership-stakeholder-management

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Leadership & Stakeholder Management Skill

领导力与利益相关者管理技能

Master the human side of product management. Align stakeholders, communicate effectively, resolve conflicts, and inspire teams toward shared vision.

掌握产品管理中的人际沟通技巧。对齐利益相关者，高效沟通，解决冲突，激励团队朝着共同愿景前进。

Stakeholder Mapping & Analysis

利益相关者映射与分析

Identify All Stakeholders

识别所有利益相关者

┌─────────────────┬──────────────────┐
│   DECISION      │    INFLUENCE     │  ← POWER
│   MAKERS        │    MAKERS        │
│                 │                  │
│   CEO, Board    │  VP Eng, Design  │
├─────────────────┼──────────────────┤
│   USERS         │   SUPPORT        │  ← LOW POWER
│                 │   TEAM           │
└─────────────────┴──────────────────┘
     LOW              HIGH
     INTEREST    ← INTEREST →

┌─────────────────┬──────────────────┐
│   DECISION      │    INFLUENCE     │  ← POWER
│   MAKERS        │    MAKERS        │
│                 │                  │
│   CEO, Board    │  VP Eng, Design  │
├─────────────────┼──────────────────┤
│   USERS         │   SUPPORT        │  ← LOW POWER
│                 │   TEAM           │
└─────────────────┴──────────────────┘
     LOW              HIGH
     INTEREST    ← INTEREST →

Stakeholder List

利益相关者列表

Internal Stakeholders:

Executive Team

CEO: Company success
CFO: Budget/profitability
CTO: Technical feasibility
COO: Operational impact

Engineering

VP Engineering: Tech strategy, resourcing
Engineering Lead: Implementation difficulty
QA Lead: Testing time needed

Design

Design Lead: User experience, design system impact

Marketing

VP Marketing: GTM, messaging
Demand Gen: Conversion impact

Sales

VP Sales: Sales enablement, revenue impact
Sales team: Product capability

Customer Success

VP CS: Customer satisfaction impact

Support

Support Lead: Support volume impact

External Stakeholders:

Investors: Business metrics
Major customers: Feature requests
Partners: Integration impact
Community: Open source projects

内部利益相关者：

执行团队

CEO: 公司成功
CFO: 预算/盈利能力
CTO: 技术可行性
COO: 运营影响

工程部门

工程副总裁: 技术战略、资源分配
工程主管: 实施难度
QA主管: 所需测试时间

设计部门

设计主管: 用户体验、设计系统影响

营销部门

营销副总裁: GTM策略、信息传递
需求生成团队: 转化影响

销售部门

销售副总裁: 销售赋能、收入影响
销售团队: 产品能力

客户成功部门

客户成功副总裁: 客户满意度影响

支持部门

支持主管: 支持量影响

外部利益相关者：

投资者: 业务指标
重要客户: 功能需求
合作伙伴: 集成影响
社区: 开源项目

Stakeholder Assessment

利益相关者评估

For each stakeholder:

Interest Level - How much do they care?
Influence Level - How much power do they have?
Attitude - Supportive, neutral, or resistant?
Communication Needs - What do they need to hear?

Engagement Strategy:

Manage Closely (high interest, high power) - Weekly updates, deep involvement
Keep Satisfied (low interest, high power) - Monthly updates, key decisions
Keep Informed (high interest, low power) - Transparency, feedback loops
Monitor (low interest, low power) - Occasional updates

针对每个利益相关者：

兴趣程度 - 他们的关注程度如何？
影响程度 - 他们拥有多大权力？
态度 - 支持、中立还是反对？
沟通需求 - 他们需要了解什么信息？

参与策略：

密切管理(高兴趣、高权力) - 每周更新、深度参与
保持满意(低兴趣、高权力) - 每月更新、关键决策同步
保持知情(高兴趣、低权力) - 透明化、反馈闭环
监控(低兴趣、低权力) - 偶尔更新

Communication Frameworks

沟通框架

BLUF (Bottom Line Up Front)

BLUF（结论先行）

Structure:

Bottom Line (1 sentence) - The decision/news
Situation (2-3 sentences) - Context and background
Implications (2-3 sentences) - Why it matters
Next Steps - What happens now

Example:

BOTTOM LINE: We're pausing the mobile app to focus on web performance.

SITUATION: Our web app speed is 2x slower than competitors, causing
40% of free users to churn. Mobile app is only 5% of usage.

IMPLICATIONS: Focusing on web unlocks 10x retention improvements,
strengthens our core offering, and builds foundation for mobile later.

NEXT STEPS: Engineering team shifts Tuesday. We'll replan mobile for Q2.

结构：

核心结论(1句话) - 决策/消息内容
背景情况(2-3句话) - 上下文和背景信息
影响分析(2-3句话) - 为什么重要
下一步行动 - 后续计划

示例：

BOTTOM LINE: We're pausing the mobile app to focus on web performance.

SITUATION: Our web app speed is 2x slower than competitors, causing
40% of free users to churn. Mobile app is only 5% of usage.

IMPLICATIONS: Focusing on web unlocks 10x retention improvements,
strengthens our core offering, and builds foundation for mobile later.

NEXT STEPS: Engineering team shifts Tuesday. We'll replan mobile for Q2.

SitRep (Situation Report)

SitRep（情况报告）

Weekly Status Template:

PROJECT: [Name]
STATUS: On Track / At Risk / Off Track
PROGRESS:
- Completed: [Achievement]
- In Progress: [Current work]
- Blocked: [Blockers]

METRICS:
- Metric 1: [Current vs Target]
- Metric 2: [Current vs Target]

CHALLENGES:
- Challenge 1 (Severity: High)
  Mitigation: [Plan]
- Challenge 2 (Severity: Medium)

NEXT WEEK:
- Next step 1
- Next step 2

每周状态模板：

PROJECT: [Name]
STATUS: On Track / At Risk / Off Track
PROGRESS:
- Completed: [Achievement]
- In Progress: [Current work]
- Blocked: [Blockers]

METRICS:
- Metric 1: [Current vs Target]
- Metric 2: [Current vs Target]

CHALLENGES:
- Challenge 1 (Severity: High)
  Mitigation: [Plan]
- Challenge 2 (Severity: Medium)

NEXT WEEK:
- Next step 1
- Next step 2

One-Pager Format

单页简报格式

2-Page Executive Brief:

Page 1:

Title and date
Summary (2-3 sentences)
Problem statement
Proposed solution
Expected impact (revenue/growth/NPS)

Page 2:

Detailed reasoning
Success metrics
Timeline
Resource needs
Risks and mitigations
Decision requested

2页高管简报：

第1页：

标题和日期
摘要(2-3句话)
问题陈述
提议的解决方案
预期影响(收入/增长/NPS)

第2页：

详细推理
成功指标
时间线
资源需求
风险与缓解措施
所需决策

Executive Communication

高管沟通

Board Update (Monthly/Quarterly)

董事会更新（月度/季度）

Presentation Structure (30 minutes):

Dashboard (5 min)
- Key metrics vs targets
- Green/yellow/red status
- Trend arrows
Progress (5 min)
- Launched features
- Customer wins
- Team updates
Challenges (5 min)
- Market challenges
- Competitive threats
- Internal blockers
Opportunities (5 min)
- Market opportunities
- Strategic bets
- Investment needs
Request (5 min)
- What you need (capital, resources, approval)
- Timeline and impact
- Board decision needed

演示结构（30分钟）：

数据仪表盘(5分钟)
- 关键指标 vs 目标
- 绿/黄/红状态
- 趋势箭头
进展汇报(5分钟)
- 已上线功能
- 客户成功案例
- 团队更新
挑战分析(5分钟)
- 市场挑战
- 竞争威胁
- 内部障碍
机会挖掘(5分钟)
- 市场机会
- 战略赌注
- 投资需求
请求事项(5分钟)
- 所需支持（资金、资源、审批）
- 时间线与影响
- 需董事会做出的决策

Pitch Deck (Investor Ready)

投资者推介PPT

15-20 Slides:

Problem (customer pain)
Market opportunity (TAM/SAM/SOM)
Solution (what you're building)
Product demo (show it working)
Business model (how you make money)
Go-to-market (customer acquisition)
Team (why you'll win)
Traction (customer proof)
Financials (revenue projections)
Use of funds (how you'll use investment)
Q&A (be ready)

15-20页：

问题（客户痛点）
市场机会（TAM/SAM/SOM）
解决方案（产品定位）
产品演示（功能展示）
商业模式（盈利方式）
GTM策略（客户获取）
团队介绍（核心优势）
业务 traction（客户验证）
财务数据（收入预测）
资金用途（投资分配）
问答环节

Executive Storytelling

高管叙事技巧

Golden Circle Framework:

       WHY?
      ░░░░░
    ┌────────┐
    │ What?  │
    │(Facts) │
    └────────┘

WHY: Why does this matter?
WHAT: What are we doing?
HOW: How will we do it?

Example:

WHY: Every team wastes hours syncing data across tools
WHAT: We're building one unified hub for collaboration
HOW: Real-time sync, zero-config integrations, beautiful UX

黄金圈框架：

       WHY?
      ░░░░░
    ┌────────┐
    │ What?  │
    │(Facts) │
    └────────┘

WHY: 这件事为什么重要？
WHAT: 我们要做什么？
HOW: 我们将如何实现？

示例：

WHY: 每个团队都在跨工具同步数据上浪费大量时间
WHAT: 我们正在打造一个统一的协作中心
HOW: 实时同步、零配置集成、优质UX

Cross-Functional Alignment

跨职能对齐

Stakeholder Alignment Meeting

利益相关者对齐会议

Pre-Meeting (Friday before):

Send agenda + context
1-pager with key points
Data/evidence
Proposed decision

Meeting (Monday, 45 minutes):

Opening (5 min) - Goal and decision needed
Context (10 min) - Why this matters
Proposal (10 min) - What we recommend
Discussion (15 min) - Questions and concerns
Decision (5 min) - Clear decision and next steps

Post-Meeting (Tuesday):

Send summary
Decision documented
Next steps assigned
Follow-up timeline

会前准备（周五）：

发送议程+背景资料
包含核心要点的单页简报
数据/证据
提议的决策方案

会议（周一，45分钟）：

开场(5分钟) - 会议目标与所需决策
背景介绍(10分钟) - 事件重要性
方案提议(10分钟) - 推荐方案
讨论环节(15分钟) - 疑问与顾虑
决策确认(5分钟) - 明确决策与下一步行动

会后跟进（周二）：

发送会议摘要
记录决策内容
分配下一步任务
设置跟进时间线

Conflict Resolution

冲突解决

When stakeholders disagree:

Listen deeply - Understand both perspectives
Find common ground - What do both care about?
Reframe - Bigger goal both support
Propose trade-off - Can you do both phased?
Decide - If needed, PM makes call (with escalation path)

Example:

Engineering wants more technical debt cleanup. Sales wants new features for customers.

Reframe: Both want happy, sticky customers.

Cleanup: Makes new features faster, higher quality
Features: What customers actively need

Trade-off: 70% features, 30% cleanup each sprint

当利益相关者意见不一致时：

深度倾听 - 理解双方立场
寻找共同点 - 双方共同关注的点是什么？
重新框架 - 聚焦双方都支持的更大目标
提议折中方案 - 能否分阶段实现两者？
做出决策 - 必要时由PM拍板（含升级路径）

示例：

工程部门希望更多时间清理技术债务。销售部门希望为客户开发新功能。

重新框架： 双方都希望拥有满意、粘性高的客户。

技术债务清理：让新功能开发更快、质量更高
新功能：满足客户的实际需求

折中方案： 每个迭代70%精力用于新功能，30%用于技术债务清理

Regular Cadence Meetings

定期会议节奏

Weekly:

Product standup (15 min) - Progress update
Engineering sync (30 min) - Technical discussions
Design review (30 min) - Design progress

Bi-Weekly:

Product council (60 min) - Roadmap decisions
Cross-functional planning (60 min) - Upcoming work

Monthly:

All hands (30 min) - Company updates
Customer advisory board (60 min) - Customer feedback

Quarterly:

Planning (8 hours) - Next quarter roadmap
Retrospective (2 hours) - Learnings

每周：

产品站会（15分钟）- 进度更新
工程同步会（30分钟）- 技术讨论
设计评审会（30分钟）- 设计进展

每两周：

产品委员会（60分钟）- 路线图决策
跨职能规划会（60分钟）- 后续工作安排

每月：

全员大会（30分钟）- 公司更新
客户咨询委员会（60分钟）- 客户反馈

每季度：

规划会（8小时）- 下季度路线图
回顾会（2小时）- 经验总结

Product Advocacy

产品推广

Internal Advocacy

内部推广

Get team excited about vision:

Tell compelling stories
Share customer quotes
Celebrate wins
Make impact visible
Create ownership

Communication:

Weekly email update
Monthly townhall
Slack announcements
One-on-ones

让团队对愿景充满热情：

讲述有吸引力的故事
分享客户评价
庆祝胜利
让成果可视化
建立主人翁意识

沟通方式：

每周邮件更新
月度全员大会
Slack公告
一对一沟通

External Advocacy

外部推广

Build authority and trust:

Writing:

Blog posts on industry trends
LinkedIn articles on product thinking
Case studies of successful customers

Speaking:

Conferences talks (be selective)
Podcast interviews
Webinars for customers
Media interviews

Community:

Twitter/LinkedIn engagement
Answer user questions
Share roadmap transparently
Ask for feedback publicly

建立权威与信任：

内容创作：

行业趋势博客
关于产品思维的LinkedIn文章
成功客户案例研究

演讲分享：

行业会议演讲（选择性参与）
播客访谈
客户网络研讨会
媒体采访

社区运营：

Twitter/LinkedIn互动
解答用户问题
透明分享路线图
公开征集反馈

Media & PR

媒体与PR

Press Release Template:

For Immediate Release

[Company] Launches [Product] to Help [Customer Type] [Benefit]

[City] - [Company] today announced the launch of [Product],
which [key benefit].

Key features:
- Feature 1
- Feature 2
- Feature 3

"[CEO quote about why this matters]," said [Name].

Availability: [Where/when available]

About [Company]: [1-2 sentence description]

Contact: [PR contact]

新闻稿模板：

For Immediate Release

[Company] Launches [Product] to Help [Customer Type] [Benefit]

[City] - [Company] today announced the launch of [Product],
which [key benefit].

Key features:
- Feature 1
- Feature 2
- Feature 3

"[CEO quote about why this matters]," said [Name].

Availability: [Where/when available]

About [Company]: [1-2 sentence description]

Contact: [PR contact]

Change Management

变更管理

When You Need to Change Course

当你需要调整方向时

Announcement Framework:

The Past - What we learned, why it was right then
The Present - New information/market reality
The Future - New direction and why it's better
The Impact - What changes for each group
The Support - How we'll help with transition

Example:

"We've learned that SMBs (not Enterprise) is our biggest opportunity. (Our focus was backwards.)

We're shifting all resources to SMB GTM starting next month. (The change.)

Enterprise sales team will transition to SMB sales team. (Impact.)

We'll provide training and offer roles in other departments. (Support.)"

公告框架：

过去 - 我们学到了什么，为什么当时的选择是正确的
现在 - 新信息/市场现状
未来 - 新方向及其优势
影响 - 对各团队的变化
支持 - 我们将如何协助过渡

示例：

"我们发现SMB（而非企业客户）是我们最大的机会。（之前的方向有误。）

从下个月开始，我们将所有资源转向SMB的GTM策略。（变更内容。）

企业销售团队将转型为SMB销售团队。（影响。）

我们将提供培训，并提供其他部门的岗位选择。（支持措施。）"

Communication Cadence

沟通节奏

Weekly

每周

Status email
1-on-1s with reports
Product standup
Stakeholder updates

状态邮件
与下属的一对一沟通
产品站会
利益相关者更新

Monthly

每月

All-hands presentation
Product email newsletter
Metrics review
Stakeholder meetings

全员演示
产品邮件通讯
指标评审
利益相关者会议

Quarterly

每季度

Strategic review
Roadmap presentation
Team offsite
Board update

战略评审
路线图演示
团队外出团建
董事会更新

Annually

每年

Company retreat
Vision refresh
Compensation/promotion cycle

公司团建
愿景更新
薪酬/晋升周期

Difficult Conversations

艰难对话

Delivering Difficult News

传达艰难消息

Structure:

Lead with empathy - "I know this affects you"
Be clear and direct - Not dancing around
Explain why - Context and reasoning
Give space - Let them react
Offer support - "Here's how I'll help"

Example:

"I know you were expecting the mobile app this quarter. We've made the difficult decision to delay it to focus on web performance, which is causing churn. This was a tough call but right for the business. I want to help you through the transition. What concerns you most?"

结构：

以同理心开场 - "我知道这会影响到你"
清晰直接 - 不绕弯子
解释原因 - 背景与推理
给予空间 - 让对方表达情绪
提供支持 - "我会这样帮你"

示例：

"我知道你原本期待本季度上线移动端应用。我们做出了艰难的决定，将其推迟，转而专注于导致用户流失的网页性能问题。这是一个艰难但对业务正确的选择。我会帮你度过过渡阶段。你最担心什么？"

Saying No

如何说不

To feature requests: "That's a great idea. It would solve [problem]. Right now we're focused on [strategic priority] which impacts [bigger opportunity]. I'm adding it to the roadmap for Q2. Can we put a placeholder?"

To stakeholder pressure: "I understand you need this. Our roadmap is full of higher-impact items. If this is truly critical, what would you deprioritize? I need to understand the trade-off."

针对功能请求： "这是个很棒的想法，能解决[问题]。目前我们正专注于[战略优先级]，它能带来[更大的机会]。我会把这个想法加入Q2的路线图。我们先留个占位符可以吗？"

针对利益相关者的压力： "我理解你需要这个功能。我们的路线图上已经排满了更高影响力的事项。如果这个功能确实至关重要，你愿意优先放弃哪项工作？我需要了解其中的权衡。"

Troubleshooting

问题排查

Yaygın Hatalar & Çözümler

常见错误与解决方案

Hata	Olası Sebep	Çözüm
Stakeholder resistance	Insufficient involvement	Early inclusion
Decision paralysis	Too many stakeholders	RACI matrix
Misalignment	Poor communication	Increase cadence
Conflict escalation	Unaddressed concerns	1:1 meetings

错误	可能原因	解决方案
利益相关者抵制	参与度不足	早期纳入
决策瘫痪	利益相关者过多	RACI矩阵
对齐不一致	沟通不畅	增加沟通频率
冲突升级	顾虑未被解决	一对一沟通

Debug Checklist

排查清单

[ ] Tüm stakeholder'lar identified mi?
[ ] RACI matrix var mı?
[ ] Communication cadence set mi?
[ ] Decision rights clear mi?
[ ] Conflict early identified mi?

[ ] Tüm stakeholder'lar identified mi?
[ ] RACI matrix var mı?
[ ] Communication cadence set mi?
[ ] Decision rights clear mi?
[ ] Conflict early identified mi?

Recovery Procedures

恢复流程

Stakeholder Conflict → 1:1 meetings, understand concerns
Decision Deadlock → Trade-off matrix, escalate
Change Resistance → Address concerns, show benefits

Master leadership and inspire your organization toward great products!

利益相关者冲突 → 一对一沟通，了解顾虑
决策僵局 → 权衡矩阵，升级处理
变更抵制 → 解决顾虑，展示收益

掌握领导力，激励你的组织打造卓越产品！