Back to Details

building-a-promotion-case

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Building a Promotion Case

构建晋升案例

Scope

范围

Covers
  • Turning “I want a promotion” into a concrete promotion thesis tied to company priorities
  • Mapping your work to the next-level expectations (career ladder / competency model)
  • Building an evidence-backed impact log (metrics + artifacts + stakeholder proof)
  • Creating a submission-ready promotion doc (one-pager + appendix) that makes the decision easy
  • Aligning with your manager using a partnership loop (a.k.a. “Magic Loop”) and planning the next 4–12 weeks
  • Building a lightweight sponsor/visibility plan (political capital without being sleazy)
When to use
  • “Help me write a promotion packet / promotion doc.”
  • “I need a promotion case that maps to our career ladder.”
  • “I want to get promoted this cycle—what should I do and how do I prove it?”
  • “My manager says ‘keep doing what you’re doing’—I need crisp promotion criteria and a plan.”
  • “I want to level up, but I’m not sure what evidence counts.”
When NOT to use
  • You need compensation negotiation tactics for a new offer (this pack is about internal promotion readiness, not external offers)
  • You are in an HR/performance escalation (PIP, investigation, termination risk) — involve HR/manager process first
  • You don’t want to involve your manager at all (promotion decisions are manager- and org-mediated; this pack assumes partnership)
  • You only need a resume/LinkedIn rewrite (use a resume-focused workflow instead)
涵盖
  • 将“我想要晋升”转化为与公司优先级挂钩的具体晋升论点
  • 将你的工作成果与下一职级的期望要求（职业阶梯/能力模型）进行匹配
  • 构建有证据支持的影响日志（包含指标+成果物+利益相关方证明）
  • 创建可直接提交的晋升文档（单页摘要+附录），让决策过程更简单
  • 通过“协作循环”（又称“魔法循环”）与你的经理对齐，并规划未来4–12周的工作
  • 构建轻量化的支持者/曝光度计划（合理积累职场影响力，而非投机取巧）
适用场景
  • “帮我撰写晋升材料/晋升文档。”
  • “我需要一份符合职业阶梯要求的晋升案例。”
  • “我想在本次晋升周期获得晋升——我该做什么，又该如何证明自己的成果？”
  • “我的经理说‘继续保持当前工作即可’——我需要清晰的晋升标准和计划。”
  • “我想提升职级，但不确定哪些成果可以作为有效证据。”
不适用场景
  • 你需要针对新offer的薪酬谈判策略（本工具包聚焦于内部晋升准备，而非外部offer）
  • 你正处于HR/绩效提升流程中（如绩效改进计划PIP、调查、解雇风险）——请先遵循HR/经理的流程
  • 你完全不想让经理参与（晋升决策由经理和组织主导；本工具包默认基于协作模式）
  • 你只需要简历/LinkedIn资料改写（请使用专注于简历的工作流）

Inputs

输入要求

Minimum required
  • Your role + scope today (team, product area, what you own)
  • Target level/role and timing (desired promo cycle/date)
  • Your company’s leveling rubric / ladder (or a description of expectations if you can’t share the doc)
  • 3–8 work examples from the last 6–12 months (projects, launches, decisions, cross-functional leadership)
  • Evidence signals (metrics, customer outcomes, reliability, revenue/cost, quality, speed, adoption)
  • Stakeholders involved (manager, partners, potential sponsors, promo committee style if known)
Missing-info strategy
  • Ask up to 5 questions from references/INTAKE.md (3–5 at a time).
  • If the ladder/process is unclear, proceed with a generic ladder mapping and label assumptions for the user to correct.
  • Don’t request confidential/PII; use anonymized numbers and redacted descriptions.
最低要求输入
  • 你当前的岗位+职责范围（团队、产品领域、负责事项）
  • 目标职级/岗位及时间节点（期望的晋升周期/日期）
  • 公司的职级评定标准/职业阶梯（如果无法分享文档，可提供期望要求的描述）
  • 过去6–12个月的3–8个工作案例（项目、发布、决策、跨职能领导工作）
  • 成果证据信号（指标、客户成果、可靠性、收入/成本、质量、速度、采用率）
  • 涉及的利益相关方（经理、合作伙伴、潜在支持者、已知的晋升委员会风格）
缺失信息处理策略
  • 从references/INTAKE.md中最多提出5个问题（每次3–5个）。
  • 如果职级标准/流程不明确，先使用通用职级映射，并标注假设供用户修正。
  • 不要要求提供机密/PII信息；使用匿名数字和模糊描述。

Outputs (deliverables)

产出物（交付件）

Produce a Promotion Case Pack (Markdown in-chat; or as files if requested) in this order:
  1. Promotion thesis + target role/timeline (what you’re asking for, why now)
  2. Next-level expectations map (ladder/competencies → what “good” looks like)
  3. Evidence log (impact table with metrics + artifacts + stakeholders)
  4. Competency mapping (claims → evidence; gaps → plan)
  5. Impact narrative (1-page story + “company problem solved” framing)
  6. Manager alignment plan (“Magic Loop”) (asks, commitments, check-ins, decision criteria)
  7. Sponsor/visibility map (who needs to believe what; how you’ll socialize)
  8. Risks / Open questions / Next steps (always)
Templates: references/TEMPLATES.md
Expanded guidance: references/WORKFLOW.md
生成一份晋升案例包（聊天中用Markdown格式；若有需求可提供文件），按以下顺序排列：
  1. 晋升论点 + 目标岗位/时间线（你的诉求及当前申请的原因）
  2. 下一职级期望映射表（职业阶梯/能力要求 → “达标”的具体表现）
  3. 影响日志（包含指标+成果物+利益相关方的影响表格）
  4. 能力匹配表（主张→证据；差距→计划）
  5. 影响叙事（1页篇幅的故事 + “解决公司问题”的框架）
  6. 经理对齐计划（“魔法循环”）（诉求、承诺、跟进检查、决策标准）
  7. 支持者/曝光度地图（需要哪些人认可什么；你将如何进行沟通）
  8. 风险 / 待解决问题 / 下一步行动（必须包含）
模板：references/TEMPLATES.md
扩展指南：references/WORKFLOW.md

Workflow (8 steps)

工作流（8个步骤）

1) Intake + promotion process snapshot

1) 信息收集 + 晋升流程快照

  • Inputs: user context; references/INTAKE.md.
  • Actions: Confirm the goal (promotion vs broader career planning). Capture timing, process, and decision-makers. Identify constraints (confidentiality, limited metrics, org politics).
  • Outputs: Promotion context snapshot + assumptions/unknowns list.
  • Checks: Target level and promo window are explicit; boundaries are respected.
  • 输入：用户背景信息；references/INTAKE.md。
  • 行动：确认目标（晋升 vs 更广泛的职业规划）。记录时间节点、流程和决策者。识别约束条件（保密性、有限指标、组织政治）。
  • 产出：晋升背景快照 + 假设/未知事项列表。
  • 检查项：目标职级和晋升窗口期明确；边界得到尊重。

2) Define the promotion thesis (make the decision easy)

2) 定义晋升论点（简化决策过程）

  • Inputs: company priorities; your work themes; target level expectations.
  • Actions: Draft a 1–2 sentence thesis: “Promote me to X because I already operate at X by doing Y which solves Z.” Tie to a concrete company problem.
  • Outputs: Promotion thesis + 3–5 proof points (bullets).
  • Checks: Thesis is falsifiable and specific (not “I worked hard”).
  • 输入：公司优先级；你的工作主题；目标职级期望。
  • 行动：撰写1–2句话的论点：“请将我晋升至X职级，因为我已通过完成Y工作达到X职级要求，而这些工作解决了Z公司问题。” 论点需紧扣具体的公司问题。
  • 产出：晋升论点 + 3–5个支撑要点（项目符号列表）。
  • 检查项：论点可验证且具体（避免“我工作很努力”这类表述）。

3) Map next-level expectations (promotion ≠ career, but they should align)

3) 匹配下一职级期望（晋升≠职业规划，但二者应保持一致）

  • Inputs: ladder/rubric (or proxy); target role definition.
  • Actions: Translate the ladder into a small set of competencies and “next-level signals.” Separate: (a) table stakes, (b) differentiators, (c) visibility/scope expectations.
  • Outputs: Expectations map + initial gap list.
  • Checks: Each competency has observable behaviors; gaps are concrete.
  • 输入：职级标准/能力模型（或替代参考）；目标岗位定义。
  • 行动：将职级标准转化为一组精简的能力要求和“下一职级信号”。分为三类：(a) 基础要求，(b) 差异化表现，(c) 曝光度/职责范围期望。
  • 产出：期望映射表 + 初始差距清单。
  • 检查项：每项能力要求都有可观察的行为表现；差距描述具体。

4) Build an evidence log (receipts, not vibes)

4) 构建影响日志（用证据而非主观感受说话）

  • Inputs: 3–8 work examples; available metrics; artifacts.
  • Actions: Create an evidence table that captures: problem, your role, scope, decisions, outcomes, metrics/proxies, and partners. Identify where you need stakeholder quotes.
  • Outputs: Evidence log + “evidence missing” list.
  • Checks: Each major claim has at least 2 evidence types (metric/proxy + artifact/partner proof).
  • 输入：3–8个工作案例；可用指标；成果物。
  • 行动：创建影响表格，包含：问题、你的角色、职责范围、决策、成果、指标/替代指标、合作伙伴。明确需要获取利益相关方评价的环节。
  • 产出：影响日志 + “缺失证据”清单。
  • 检查项：每个核心主张至少有2种证据类型（指标/替代指标 + 成果物/合作伙伴证明）。

5) Convert evidence into a promotion doc draft (one-pager + appendix)

5) 将证据转化为晋升文档草稿（单页摘要+附录）

  • Inputs: thesis, expectations map, evidence log.
  • Actions: Draft the promo doc using the template. Write in exec-friendly language: impact, scope, leadership, leverage, and why you’re low-risk at the next level.
  • Outputs: Promotion doc draft + appendix (evidence snippets).
  • Checks: The doc is skimmable in 3 minutes; every claim has a pointer to evidence.
  • 输入：晋升论点、期望映射表、影响日志。
  • 行动：使用模板撰写晋升文档。采用高管友好型语言：聚焦影响、职责范围、领导力、杠杆作用，以及你在下一职级的低风险性。
  • 产出：晋升文档草稿 + 附录（证据片段）。
  • 检查项：文档可在3分钟内快速浏览；每个主张都有证据指向。

6) Manager alignment loop (“Magic Loop”) + criteria agreement

6) 经理对齐循环（“魔法循环”）+ 标准共识

  • Inputs: draft doc; manager context; promo process.
  • Actions: Create a plan to align with your manager: ask what would make them confident, commit to what they ask, and schedule check-ins. Draft your “ask” script and the next 4–12 week plan.
  • Outputs: Manager alignment plan + 1:1 agenda/script.
  • Checks: Manager expectations are explicit; next check-in date is scheduled; you’ve made it easy to sponsor you.
  • 输入：文档草稿；经理背景信息；晋升流程。
  • 行动：制定与经理对齐的计划：询问哪些因素能让他们信服，承诺完成他们要求的事项，并安排跟进检查。撰写你的“诉求”脚本和未来4–12周的计划。
  • 产出：经理对齐计划 + 1对1会议议程/脚本。
  • 检查项：经理的期望明确；已安排下一次跟进检查日期；你已简化经理支持你的流程。

7) Sponsor/visibility plan (politics as logistics)

7) 支持者/曝光度计划（将职场政治转化为可执行步骤）

  • Inputs: stakeholder map; known promo committee dynamics.
  • Actions: Identify 3–8 people whose belief matters. Plan how you will: (a) increase visibility of outcomes, (b) request feedback/endorsements, (c) avoid surprises.
  • Outputs: Sponsor/visibility map + outreach templates.
  • Checks: Every key stakeholder has a specific next action and a low-friction ask.
  • 输入：利益相关方地图；已知的晋升委员会动态。
  • 行动：识别3–8位其认可至关重要的人员。规划如何：(a) 提升成果的曝光度，(b) 请求反馈/背书，(c) 避免意外情况。
  • 产出：支持者/曝光度地图 + 沟通模板。
  • 检查项：每位关键利益相关方都有具体的下一步行动和低门槛的诉求。

8) Quality gate + finalize

8) 质量校验 + 最终定稿

  • Inputs: full pack draft.
  • Actions: Run references/CHECKLISTS.md and score with references/RUBRIC.md. Tighten weak sections. Add Risks / Open questions / Next steps. Produce a submission-ready doc and a short “manager email” version.
  • Outputs: Final Promotion Case Pack.
  • Checks: Pack is evidence-based, ladder-aligned, and process-ready; risks and unknowns are explicit.
  • 输入：完整的工具包草稿。
  • 行动：使用references/CHECKLISTS.md和references/RUBRIC.md进行校验和评分。优化薄弱环节。添加风险 / 待解决问题 / 下一步行动。生成可提交的最终文档和简短的“经理邮件版”。
  • 产出：最终晋升案例包。
  • 检查项：工具包基于证据、符合职级标准、可直接用于流程；风险和未知事项明确。

Quality gate (required)

质量校验（强制要求）

  • Use references/CHECKLISTS.md and references/RUBRIC.md.
  • Always include: Risks, Open questions, Next steps.
  • 使用references/CHECKLISTS.md和references/RUBRIC.md。
  • 必须包含：风险、待解决问题、下一步行动。

Examples

示例

Example 1 (typical): “I’m a Senior PM and want to get promoted to Staff PM in the next cycle (May). Here’s our ladder excerpt and 5 projects I led. Build a promotion case doc + evidence log + manager alignment plan.”
Expected: Promotion Case Pack with a ladder-mapped narrative and concrete manager check-ins.
Example 2 (limited metrics): “I’m a PM on an internal platform team. My impact is hard to measure. Help me build a promotion case using proxy metrics, stakeholder evidence, and artifacts.”
Expected: Evidence log with proxies (cycle time, reliability, adoption, internal NPS) and explicit proof pointers.
Boundary example: “My manager refuses to discuss promotions and HR is involved in a performance process.”
Response: recommend following HR/manager process first; offer to help later with evidence capture, role expectations, and a future readiness plan.
示例1（典型场景）：“我是高级产品经理，想在下一个晋升周期（5月）晋升为资深产品经理。这是我们的职级标准节选和我主导的5个项目。帮我构建晋升案例文档 + 影响日志 + 经理对齐计划。”
预期产出：包含职级匹配叙事和具体经理跟进计划的晋升案例包。
示例2（指标有限场景）：“我是内部平台团队的产品经理，我的工作影响难以量化。帮我用替代指标、利益相关方证明和成果物构建晋升案例。”
预期产出：包含替代指标（周期时间、可靠性、采用率、内部NPS）和明确证据指向的影响日志。
边界场景示例：“我的经理拒绝讨论晋升，且HR已介入绩效流程。”
回应：建议先遵循HR/经理的流程；后续可提供证据收集、岗位期望梳理和未来准备计划的帮助。