Back to Details

stakeholder-alignment

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Stakeholder Alignment

利益相关者对齐

Scope

适用范围

Covers
  • Getting to shared understanding on goal, decision, and success criteria
  • Mapping stakeholders (deciders/influencers/blockers) and tailoring messaging to what they care about
  • Turning “opinions” into decision principles + evaluation criteria
  • Running a no-surprises pre-brief loop to surface objections early
  • Facilitating an alignment/decision meeting and locking follow-through with clear comms
When to use
  • “Help me get exec buy-in for this roadmap change.”
  • “We keep leaving meetings ‘aligned’ and then un-aligning—fix the process.”
  • “Map stakeholders and create a plan to align them on a proposal.”
  • “I need cross-functional alignment (Eng/Design/Sales/Legal) before we commit.”
  • “Draft an alignment pre-read + meeting plan + follow-up comms.”
When NOT to use
  • You don’t yet have a clear problem to solve (use problem definition first).
  • You mainly need a decision framework/roles for a complex choice (use a decision-process skill; this skill assumes you can name the decision and stakeholders).
  • You only need a polished deck (use a presentation skill; this focuses on alignment mechanics and artifacts).
  • The request is interpersonal/HR/legal or requires specialist counsel.
包含
  • 就目标、决策及成功标准达成共识
  • 绘制利益相关者图谱（决策者/影响者/阻碍者）并根据其关注点定制沟通内容
  • 将“观点”转化为决策原则+评估标准
  • 开展“无意外”的预沟通循环，提前发现反对意见
  • 主持对齐/决策会议，并通过清晰的沟通确保后续执行
适用场景
  • “帮我获取高管对此次路线图变更的支持。”
  • “我们开完会总说‘对齐了’，之后又出现分歧——优化这个流程。”
  • “绘制利益相关者图谱，并制定计划让他们对齐某提案。”
  • “在我们做出承诺前，需要获得跨职能（工程/设计/销售/法务）的对齐。”
  • “起草对齐预读材料+会议计划+后续沟通内容。”
不适用场景
  • 你尚未明确要解决的问题（先使用问题定义工具）。
  • 你主要需要针对复杂选择的决策框架/角色定义（使用决策流程工具；本工具假设你已明确决策内容和利益相关者）。
  • 你只需要一份精美的演示文稿（使用演示工具；本工具聚焦于对齐机制和相关产出物）。
  • 请求涉及人际/HR/法务问题，或需要专业顾问支持。

Inputs

输入信息

Minimum required
  • Alignment goal: inform / align / decide (and by when)
  • The proposal (or decision) in one sentence + why now
  • Stakeholder list (or org context to infer it)
  • Constraints/non-negotiables (timeline, budget, policy, compliance, customer commitments)
  • Current state: what’s already been discussed, and where alignment breaks down
Missing-info strategy
  • Ask 3–5 questions from references/INTAKE.md at a time.
  • If key info is unavailable, proceed with explicit assumptions and label unknowns.
最低要求
  • 对齐目标：告知/对齐/决策（及截止时间）
  • 一句话描述提案（或决策）+ 为何是现在
  • 利益相关者列表（或可推断的组织背景）
  • 约束条件/不可协商项（时间线、预算、政策、合规要求、客户承诺）
  • 当前状态：已讨论的内容，以及对齐出现分歧的地方
缺失信息处理策略
  • 每次从references/INTAKE.md中选取3–5个问题询问。
  • 如果关键信息不可用，基于明确假设推进，并标注未知项。

Outputs (deliverables)

产出物

Produce a Stakeholder Alignment Pack (Markdown in-chat; or files if requested) in this order:
  1. Alignment Brief (1-pager) (goal, decision/ask, why now, user value, success criteria, constraints, tradeoffs)
  2. Stakeholder Map + “How They Think” notes (roles, incentives, likely objections, decision principles)
  3. Alignment Plan (pre-brief sequence, artifacts, timeline, and “no surprises” plan)
  4. Alignment Pre-read + Meeting Plan (agenda, vital questions, options/tradeoffs, decision capture)
  5. Decision Summary + Comms Draft (what we decided, why, what changes, owners, next steps)
  6. Risks / Open questions / Next steps (always)
Templates: references/TEMPLATES.md
Expanded guidance: references/WORKFLOW.md
生成利益相关者对齐工具包（聊天内以Markdown格式呈现；若有需求可生成文件），顺序如下：
  1. 对齐简报（单页）（目标、决策/请求、为何是现在、用户价值、成功标准、约束条件、取舍权衡）
  2. 利益相关者图谱+“他们的关注点”说明（角色、激励因素、可能的反对意见、决策原则）
  3. 对齐计划（预沟通顺序、产出物、时间线、“无意外”计划）
  4. 对齐预读材料+会议计划（议程、关键问题、选项/取舍权衡、决策记录）
  5. 决策总结+沟通草稿（决策内容、原因、变更点、负责人、下一步行动）
  6. 风险/待解决问题/下一步行动（必含项）
模板：references/TEMPLATES.md
扩展指南：references/WORKFLOW.md

Workflow (8 steps)

工作流程（8步）

1) Define the alignment target (what does “aligned” mean?)

1) 定义对齐目标（“对齐”的具体含义是什么？）

  • Inputs: user context; references/INTAKE.md.
  • Actions: Classify the goal (inform/align/decide) and name the decision/commitment (or the output of alignment). Set a date and what “done” looks like.
  • Outputs: Alignment Brief sections: Goal, Decision/Ask, Deadline, Scope boundaries.
  • Checks: You can finish the sentence: “After alignment, stakeholders will commit to _____ by _____.“
  • 输入：用户背景；references/INTAKE.md
  • 行动：分类目标（告知/对齐/决策）并明确决策/承诺内容（或对齐的产出）。设定截止日期及“完成”的标准。
  • 产出：对齐简报中的：目标、决策/请求、截止日期、范围边界。
  • 检查项：你可以完成这句话：“对齐后，利益相关者将承诺在_____前完成_____。”

2) Map stakeholders and decision rights (who matters, and why)

2) 绘制利益相关者图谱及决策权限（谁是关键角色，原因是什么？）

  • Inputs: org context; prior meeting notes; known stakeholders.
  • Actions: Build a stakeholder map: decider(s), approvers, influencers, implementers, blockers, and “silent veto” risks. Identify who must not be surprised.
  • Outputs: Stakeholder Map (table) + “pre-brief required” list.
  • Checks: Every critical function affected (e.g., Eng, Design, Sales, Support, Legal/Compliance, Finance) is either included or explicitly out of scope.
  • 输入：组织背景；过往会议记录；已知的利益相关者
  • 行动：构建利益相关者图谱：决策者、审批者、影响者、执行者、阻碍者，以及“隐性否决”风险。识别哪些利益相关者不能被突然告知信息。
  • 产出：利益相关者图谱（表格）+“需要预沟通”的列表
  • 检查项：所有受影响的关键职能（如工程、设计、销售、支持、法务/合规、财务）要么被纳入范围，要么被明确排除在外。

3) Decode “how they think” (principles, not just opinions)

3) 解读“他们的思考逻辑”（原则，而非单纯的观点）

  • Inputs: prior feedback; exec writings/talks; observed patterns.
  • Actions: Convert stakeholder feedback into 3–7 decision principles (e.g., “must feel like the future”, “minimize enterprise risk”). Note what evidence persuades them.
  • Outputs: “How They Think” notes (per key stakeholder) + principles list.
  • Checks: For each key stakeholder, you can explain: “In what world does their viewpoint make sense?”
  • 输入：过往反馈；高管文稿/讲话；观察到的模式
  • 行动：将利益相关者的反馈转化为3–7条决策原则（例如：“必须符合未来发展方向”、“最小化企业风险”）。记录哪些证据能说服他们。
  • 产出：“他们的思考逻辑”说明（针对关键利益相关者）+ 原则列表
  • 检查项：对于每个关键利益相关者，你可以解释：“在什么情况下他们的观点是合理的？”

4) Anchor on user value + business constraints (cut through noise)

4) 聚焦用户价值+业务约束（排除干扰）

  • Inputs: proposal; user/customer context; constraints.
  • Actions: Draft the narrative spine: user value (the “vital question”), why now, and the unavoidable tradeoffs. Make constraints explicit (compliance, monetization, go-to-market, reliability).
  • Outputs: Alignment Brief sections: User value, Why now, Constraints, Tradeoffs.
  • Checks: A skeptical stakeholder can’t dismiss the proposal as “nice to have” without disputing a stated assumption.
  • 输入：提案；用户/客户背景；约束条件
  • 行动：起草核心叙事：用户价值（“关键问题”）、为何是现在，以及不可避免的取舍权衡。明确约束条件（合规、盈利、市场推广、可靠性）。
  • 产出：对齐简报中的：用户价值、为何是现在、约束条件、取舍权衡
  • 检查项：持怀疑态度的利益相关者无法在不质疑既定假设的情况下，将提案斥为“锦上添花”。

5) Define evaluation criteria and “what good looks like”

5) 定义评估标准及“成功的样子”

  • Inputs: goals, constraints, stakeholder principles.
  • Actions: Create evaluation criteria (and weights if helpful). Set expectations that agreement may feel uncomfortable at first; focus stakeholders on criteria over gut feel.
  • Outputs: Criteria list (and optional criteria table) + “discomfort is normal” expectation-setting line for meetings.
  • Checks: Criteria are few (3–7), mutually meaningful (real tradeoffs), and tied to stakeholder principles.
  • 输入：目标、约束条件、利益相关者原则
  • 行动：制定评估标准（如有帮助可添加权重）。设定预期：最初的共识可能会让人不适；引导利益相关者关注标准而非直觉判断。
  • 产出：评估标准列表（及可选的标准表格）+ 会议中用于设定预期的“不适是正常的”表述
  • 检查项：标准数量少（3–7条）、具有共同意义（涉及实际取舍）、且与利益相关者原则挂钩。

6) Run the pre-brief loop (no surprises; watch reactions)

6) 开展预沟通循环（无意外；关注反应）

  • Inputs: draft pack; pre-brief list.
  • Actions: Meet key stakeholders 1:1 (or small groups). Observe what lands (and what causes “dead eyes”), capture objections, and update the pack. Keep a change log.
  • Outputs: Pre-brief notes + objections log + updated pack + change log.
  • Checks: No major stakeholder sees the core ask for the first time in the live meeting.
  • 输入：草稿工具包；预沟通列表
  • 行动：与关键利益相关者进行1对1（或小团体）沟通。观察哪些内容被接受（哪些内容引发“无动于衷”），记录反对意见，并更新工具包。保留变更日志。
  • 产出：预沟通记录+反对意见日志+更新后的工具包+变更日志
  • 检查项：没有重要利益相关者在现场会议中第一次看到核心请求。

7) Facilitate the alignment/decision meeting (commitments, not vibes)

7) 主持对齐/决策会议（聚焦承诺，而非氛围）

  • Inputs: final pre-read; agenda; decision capture plan.
  • Actions: Open with the alignment target and vital question. Walk through options/tradeoffs against criteria. Confirm the decision and commitments (owner + due dates). Record dissent and follow-ups.
  • Outputs: Meeting notes + decision capture + action list.
  • Checks: Everyone leaves knowing: what we decided, why, what changes tomorrow, and who owns what.
  • 输入：最终预读材料；议程；决策记录计划
  • 行动：开场说明对齐目标和关键问题。对照标准梳理选项/取舍权衡。确认决策和承诺（负责人+截止日期）。记录不同意见和后续跟进事项。
  • 产出：会议记录+决策记录+行动列表
  • 检查项：所有人离开时都清楚：我们做出了什么决策、原因是什么、明天会有什么变化、谁负责什么。

8) Communicate and lock alignment (prevent re-litigation)

8) 沟通并锁定对齐结果（避免重新讨论）

  • Inputs: decision capture; action list; stakeholder map.
  • Actions: Send a crisp summary to all stakeholders (including those not in the room). Document rationale and tradeoffs. Set a review/checkpoint date.
  • Outputs: Decision Summary + Comms Draft + review checkpoint.
  • Checks: Follow-up comms contains: decision, rationale, tradeoffs, owners, dates, and what would trigger a revisit.
  • 输入：决策记录；行动列表；利益相关者图谱
  • 行动：向所有利益相关者（包括未参会者）发送简洁的总结。记录理由和取舍权衡。设定回顾/检查点日期。
  • 产出：决策总结+沟通草稿+回顾检查点
  • 检查项：后续沟通内容包含：决策、理由、取舍权衡、负责人、日期，以及会触发重新讨论的情况。

Quality gate (required)

质量检查（必做）

  • Run references/CHECKLISTS.md and score with references/RUBRIC.md.
  • Always include: Risks, Open questions, Next steps.
  • 运行references/CHECKLISTS.md并根据references/RUBRIC.md评分。
  • 必须包含：风险、待解决问题、下一步行动。

Examples

示例

Example 1: “We need exec alignment on a 6-week pause of Feature A to address reliability. Draft the alignment brief, stakeholder map, pre-brief plan, and the decision meeting plan.”
Expected: Alignment Brief, Stakeholder Map, pre-brief plan + notes template, meeting plan + comms draft.
Example 2: “Sales and Legal are blocking a self-serve launch. Create a cross-functional alignment plan that surfaces constraints early and lands on a committed path.”
Expected: explicit constraints, evaluation criteria, no-surprises pre-brief loop, decision capture, and follow-up comms.
Boundary example: “Make them agree with me; they’re irrational.”
Response: refuse to ‘win politics’; reframe to an evidence-based alignment process (principles, criteria, tradeoffs). If the user can’t name a decision/goal, do problem definition first.
示例1：“我们需要高管对齐暂停功能A开发6周以解决可靠性问题的方案。起草对齐简报、利益相关者图谱、预沟通计划和决策会议计划。”
预期产出：对齐简报、利益相关者图谱、预沟通计划+记录模板、会议计划+沟通草稿。
示例2：“销售和法务阻碍了自助服务的上线。制定跨职能对齐计划，提前明确约束条件并确定可行方案。”
预期产出：明确的约束条件、评估标准、无意外预沟通循环、决策记录、后续沟通内容。
边界示例：“让他们同意我；他们不讲理。”
回应：拒绝参与“政治博弈”；重新定位为基于证据的对齐流程（原则、标准、取舍权衡）。如果用户无法明确决策/目标，先进行问题定义。