Back to Details

executive-onboarding-playbook

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Purpose

目的

Structure the first 90 days of a VP or CPO transition as a diagnostic process, not an execution sprint. The single most common failure in senior product leadership transitions is acting before understanding — changing structures, replacing people, or announcing strategy before building the evidence base that makes those decisions defensible.
This playbook runs in three phases: Diagnose (Month 1), Validate (Month 2), Act with Evidence (Month 3). Each phase builds on the last. Skipping phases doesn't accelerate results — it guarantees expensive reversals.
This is not a 100-day plan for impressing your new boss. It's a diagnostic protocol for making durable decisions.
将VP或CPO入职过渡的前90天设定为诊断流程，而非执行冲刺。高层产品领导力交接最常见的失败原因就是在充分了解情况前贸然行动——在构建起足以支撑决策的证据体系之前，就调整组织架构、替换人员或者发布新战略。
本手册分为三个阶段：诊断（第1个月）、验证（第2个月）、依据证据行动（第3个月）。每个阶段都以上一阶段的成果为基础，跳过阶段不仅不会加速取得成果，反而必然会导致后续付出高昂代价推倒重来。
这不是用来讨好新老板的100天表现计划，而是一套帮你做出长期有效决策的诊断方案。

Key Concepts

核心理念

The Consultant Mindset

顾问思维

Enter every new VP/CPO role as if you're an external consultant hired to assess the organization — before you're the person responsible for changing it.
What this means in practice:
  • Observe before diagnosing. Don't form opinions in the first week based on first impressions.
  • Ask questions before making declarations. "Help me understand how this works" is more powerful than "here's what we're going to do differently."
  • Understand how the steering connects to the rudder. In any organization, there are systems and relationships that look one way on paper and work completely differently in practice. Map that reality before you touch anything.
  • Don't throw the big red switch. If you walked into a power plant you'd never operated before and saw a large red switch, you probably wouldn't throw it. The same logic applies to org structures, processes, reporting lines, and team compositions you've inherited. Understand what they control first.
Negotiate this upfront: tell your boss and peers that Month 1 is explicitly a learning phase. Set the expectation that your first major recommendations will come in Month 2. Executives who've been through transitions will respect this; executives who want action in Week 1 are a signal worth noting.
担任任何新的VP/CPO职位时，先把自己当成受雇评估组织的外部顾问，再把自己当成负责变革的管理者。
实践中的具体要求：
  • 诊断前先观察，不要在第一周就凭借第一印象形成固定判断。
  • 发表声明前先提问，“麻烦帮我理解下这个是怎么运作的”比“我们接下来要做这些调整”更有力量。
  • 搞清楚表层机制和底层逻辑的关联，任何组织里都有很多系统和关系纸面上是一套，实际运行是另一套，在动手调整之前先摸清楚真实情况。
  • 不要随便拍大红色紧急开关，如果你走进一个从没操作过的发电厂，看到一个大红色开关肯定不会随便按。这个逻辑同样适用于你接手的组织架构、流程、汇报线和团队构成，先搞清楚它们的作用再动手。
提前和相关方沟通：明确告诉你的老板和同级，第一个月是明确的学习阶段，让大家预期你会在第二个月才拿出第一批核心建议。经历过管理层交接的高管会尊重这个安排，如果有高管要求你第一周就拿出行动方案，这是值得留意的信号。

Unwritten Strategy

不成文战略

At VP and CPO level, significant strategy is never fully written down. It lives in:
  • The CEO's head, shaped by conversations you weren't in
  • Board meeting dynamics and investor preferences
  • Last night's executive dinner
  • Off-the-record conversations between founders
  • Tribal knowledge that long-tenured leaders treat as obvious
This isn't dysfunction — it's how every organization works at the executive level. Treating written strategy as complete strategy will get you into trouble fast.
Your job in the first 90 days is to surface the unwritten layer. How:
  • Ask indirect questions: "What's the history here?" / "How did we end up with this approach?" / "What did we try before that didn't work?"
  • Let information find you. People who want to shape the new leader's perspective will seek you out. Take those meetings. Take notes.
  • Reality-check with your boss: "Here's what I'm hearing from the organization. This is different from what you told me. Help me understand." This is not confrontational — it's how you triangulate toward the truth.
到了VP和CPO级别，核心战略永远不会完全写在纸面上，它存在于：
  • CEO的脑子里，由你没参与过的对话塑造而成
  • 董事会会议的动态和投资者的偏好
  • 前一天晚上的高管聚餐交流
  • 创始人之间的私下对话
  • 任职时间长的老领导默认人尽皆知的部落知识
这不是组织 dysfunction，这是所有组织高层的正常运行逻辑。把书面战略当成完整战略很快就会遇到麻烦。
你前90天的工作就是挖掘出这层不成文的内容，方法如下：
  • 问间接问题：“这件事的背景是什么？”/“我们为什么会选择这个方案？”/“我们之前试过哪些没奏效的方法？”
  • 主动接收信息，想要影响新领导者判断的人会主动来找你，接受这些约谈，做好记录。
  • 和你的老板核实信息：“我从团队那边听到了这些信息，和你之前告诉我的不一样，麻烦帮我理解下背后的原因。”这不是 confrontation，而是你逼近真相的方法。

The Body of Evidence

证据体系

Every significant decision you make in Month 3 and beyond should rest on a body of evidence collected in Months 1 and 2. This means:
  • Detailed notes from every diagnostic conversation
  • Patterns noted across multiple independent sources (not just one vocal person)
  • Reality-checks completed with your manager and key peers
  • A clear picture of what's working, what's broken, and why
The body of evidence is what separates confident decisions from guesses. It's also what makes hard decisions defensible — to your team, to your peers, and to the board.
你在第3个月及之后做出的每一个重大决策，都应该基于前2个月收集的证据体系，包括：
  • 每一次诊断对话的详细记录
  • 从多个独立信息源（而不只是一个说话声音大的人）总结出的共性规律
  • 和你的上级以及核心同级完成过真实性核验的信息
  • 对哪些行之有效、哪些存在问题、背后原因是什么的清晰认知
证据体系是区分自信决策和拍脑袋猜测的核心，也能帮你在团队、同级和董事会面前证明艰难决策的合理性。

People Assessment: Two Categories

人员评估：两类情况

Two distinct people situations require different responses:
Diamonds in the rough — Capable, undervalued people who haven't had a champion. They exist in almost every organization. You'll find them in Months 1-2 by listening for: "She's really talented but nobody gives her the hard problems" or noticing who gives you the most useful, unvarnished information in your diagnostic interviews. These people become critical early allies.
Strong people in wrong roles — Not weak performers; people whose strengths are mismatched to their current scope. This is more common in organizations that grew fast, went through acquisitions, or promoted based on tenure. A former sales rep who became a PM because they knew the product. A brilliant individual contributor managing a team that needs a coach. These situations require honest, compassionate conversations — coach up if they're coachable, find them another role, or part ways. All three outcomes are better than leaving the mismatch in place.
两种不同的人员情况需要不同的应对方案：
璞玉型人才——有能力、被低估、一直没遇到伯乐的员工，几乎每个组织里都有这类人。你会在第1-2个月发现他们：比如听到别人说“她很有天赋，但没人愿意把难题交给她”，或者注意到谁在诊断访谈中给你提供了最有用、最坦诚的信息。这些人会成为你早期的核心盟友。
放错位置的优秀人才——他们不是绩效差的员工，只是能力和当前岗位职责不匹配。这种情况在快速增长、经历过收购或者按任职年限晋升的组织里更常见：比如之前的销售因为熟悉产品成了PM，比如优秀的个人贡献者现在管理的团队需要的是擅长辅导的管理者。这种情况需要坦诚、有同理心的沟通：如果他们愿意成长就提供辅导，帮他们找更适合的岗位，或者和平分手。这三种结果都比让不匹配的情况持续下去要好。

Phase 0: Before Day 1

第0阶段：入职前

If you're evaluating whether to take the role, use this phase to interview the organization before it interviews you.
Five questions to probe with the hiring CEO:
  1. "What are you expecting from the product organization in the first 90 days? The first year?" — Surfaces unrealistic transformation timelines early. Red flag: "I expect the roadmap to be fully overhauled by Q2."
  2. "Who are the all-stars on your product team, and why?" — Reveals the CEO's perceptions and biases. They're often wrong, but knowing their mental model matters.
  3. "Who has gaps, and why?" — What does the CEO believe the org's weakness is? Is it accurate?
  4. "What constraints are we working with that I should understand upfront?" — Financial, organizational, market. Understand your actual degrees of freedom before you accept.
  5. "What does success look like for this role at one year?" — Force specificity. Vague answers ("transformed the product culture") are red flags. Specific answers ("85% on-time delivery, two new enterprise accounts, one rebuilt team") are workable.
Red flags that change the calculus:
  • "You can't change the existing product roadmap" — loss of basic authority before you start
  • "We need you to transform the organization in six months" — sets you up to fail
  • Misalignment between CEO's talent assessment and what you learn elsewhere in conversations
如果你还在评估要不要接受这个职位，利用这个阶段反过来面试这个组织，而不是等着组织面试你。
问招聘你的CEO的5个问题：
  1. “你对产品团队前90天的预期是什么？第一年的预期是什么？”——提前发现不切实际的转型时间要求。危险信号：“我希望第二季度之前就能彻底调整完路线图。”
  2. “你的产品团队里哪些人是明星员工，为什么？”——了解CEO的认知和偏见，他们的判断往往不准确，但知道他们的思维模式非常重要。
  3. “哪些人存在能力缺口，原因是什么？”——了解CEO认为团队的短板是什么，这个判断是否准确？
  4. “我们有哪些需要提前了解的约束条件？”——财务、组织、市场层面的约束，在接受offer之前搞清楚你实际有多少自主权。
  5. “这个职位入职一年的成功标准是什么？”——要求对方给出具体答案，模糊的回答（“改造产品文化”）是危险信号，具体的回答（“85%的需求按时交付，新增2个企业客户，重建1支团队”）是可落地的。
会改变决策的危险信号：
  • “你不能修改现有的产品路线图”——入职前就失去了基本权限
  • “我们需要你在6个月内完成组织转型”——摆明了让你失败
  • CEO对人才的评估和你从其他渠道了解到的信息严重不符

Application

落地执行

Phase 1: Diagnose (Month 1)

第1阶段：诊断（第1个月）

Objective: Build the body of evidence. Understand reality, not the official version.
Step 1: Interview everyone Schedule 30-minute conversations with your direct reports, key cross-functional peers (CRO, CFO, CMO, Engineering leadership), and a sample of the PMs in your organization. The question set is simple:
  • "What's working well that I should understand and protect?"
  • "What's not working that you've been hoping someone would fix?"
  • "What do you think I need to know that I probably won't hear in official briefings?"
  • "Who are the people in this organization I should make sure to talk to?"
Step 2: Let people find you Don't do all the seeking. Some of the most valuable information comes from people who proactively schedule time with the new leader. They have an agenda — surface it, evaluate it, and note the signal (both in what they say and in that they came to you at all).
Step 3: Take detailed notes Every conversation. Note not just content but context: who said it, what their incentive might be, whether you heard the same thing from multiple independent sources. Patterns that appear across multiple conversations are much more reliable than strong opinions from single sources.
Step 4: Resist action When you see something obviously broken in Month 1, your instinct will be to fix it. Resist. You don't yet have the context to know why it's broken, whether previous attempts to fix it failed, or what it's connected to. Note it in your evidence log instead.
Deliverable: A detailed notebook of organizational reality, not yet interpreted.
目标： 构建证据体系，了解真实情况，而非官方版本的情况。
步骤1：和所有人访谈 和你的直接下属、核心跨部门同级（CRO、CFO、CMO、技术负责人）以及抽样的PM团队成员安排30分钟的沟通，问题很简单：
  • “有哪些运作良好的部分是我需要了解并保留的？”
  • “有哪些运行不畅的部分是你一直希望有人来解决的？”
  • “你觉得有哪些我需要知道，但官方简报里大概率不会提到的信息？”
  • “这个组织里还有哪些人我一定要去聊聊？”
步骤2：主动接收找上门的信息 不要全部自己主动去找人，很多最有价值的信息来自主动约新领导时间的人。他们有自己的诉求，挖掘出来、评估价值，同时记录信号（既包括他们说的内容，也包括他们主动来找你这件事本身）。
步骤3：做好详细记录 每一次对话都要记录，不仅记内容，还要记背景：是谁说的，他们可能有什么动机，你有没有从多个独立信息源听到过同样的内容。多轮对话里出现的共性规律，比单一信息源的强烈观点可靠得多。
步骤4：克制行动的冲动 第1个月你看到明显有问题的地方，本能反应会是马上修复，克制住。你还没有足够的背景信息知道它为什么出问题、之前的修复尝试为什么失败、它和哪些其他部分有关联，把它记到你的证据日志里就行。
交付物： 一份记录组织真实情况的详细笔记，暂不做解读。

Phase 2: Validate (Month 2)

第2阶段：验证（第2个月）

Objective: Surface patterns, challenge your emerging conclusions, identify the people situations.
Step 1: Reality-check with your boss Take your emerging picture of the organization back to your manager:
  • "I'm hearing [X] from multiple people. This is different from what I understood coming in. Help me understand the history."
  • "I'm seeing [Y] pattern across the team. Is that consistent with what you've observed?"
This is not confrontational. It's how you separate signal from noise and build a shared baseline of organizational reality.
Step 2: Map the unwritten strategy By now you've had enough conversations to start seeing the gap between stated priorities and actual organizational behavior. Ask directly: "What does the organization actually optimize for when things get hard?" The answer is usually different from the mission statement.
Step 3: Complete your people assessment By end of Month 2, you should have a preliminary read on:
  • Who your diamonds in the rough are (and how to give them more scope)
  • Who is strong but in the wrong role (and what the right conversation looks like)
  • Who is genuinely not coachable to the level the org needs (and what timeline is appropriate)
Step 4: Identify your 3-5 highest-leverage changes Not a full transformation plan — three to five specific changes that would most improve organizational effectiveness. These become your Month 3 agenda.
Deliverable: An interpreted organizational assessment with people map and initial strategic priorities.
目标： 提炼共性规律，挑战你初步形成的结论，识别人员情况。
步骤1：和你的老板核验信息 把你初步形成的组织画像同步给你的上级：
  • “我从很多人那边听到了[X]，和我入职前了解的情况不一样，麻烦帮我讲讲背后的历史。”
  • “我在团队里看到了[Y]这个规律，和你观察到的情况一致吗？”
这不是对抗，而是帮你区分信号和噪音，建立对组织真实情况的共同认知的方法。
步骤2：梳理不成文战略 到这个阶段你已经聊了足够多的人，可以开始看到公开优先级和组织实际行为之间的差距了。直接问：“遇到困难的时候，这个组织实际优先保障的是什么？”答案通常和使命宣言不一样。
步骤3：完成人员评估 到第2个月底，你应该对以下内容有初步判断：
  • 哪些是璞玉型人才（以及怎么给他们更大的权责）
  • 哪些是放错位置的优秀人才（以及怎么开展合适的沟通）
  • 哪些人确实达不到组织要求的能力、也没有成长空间（以及对应的处理 timeline）
步骤4：确定3-5个最高杠杆率的调整动作 不需要完整的转型计划，只需要找3-5个能最大程度提升组织效率的具体调整，这就是你第3个月的工作重心。
交付物： 经过解读的组织评估报告，包含人员地图和初步战略优先级。

Phase 3: Act with Evidence (Month 3)

第3阶段：依据证据行动（第3个月）

Objective: Begin making decisions grounded in the body of evidence. Introduce structure and direction, not transformation.
Step 1: Share your organizational assessment Don't keep it private. Bring your key findings to your boss and your direct reports: "Here's what I've learned about how this organization works, where it's strong, and where it needs to develop. Here's my initial plan for the next quarter." This builds trust through transparency and surfaces disagreements before you act on them.
Step 2: Run your first Cascading Context Map Use the organizational and strategic clarity you've built to create direction for your team — even if company strategy above you is still ambiguous. (See 
skills/altitude-horizon-framework/SKILL.md
for the full technique.) Your team has been waiting for context. Give them your best current translation and commit to refining it.
Step 3: Start the people conversations Now that you have evidence, have the hard conversations:
  • Diamonds in the rough: give them a stretch assignment or expanded scope
  • People in wrong roles: a direct, honest conversation about the mismatch and the options
  • Exits: begin with honesty and care, not avoidance
Step 4: Build your executive alliance deliberately By Month 3 you know who the key players are and what they need from product. Start the weekly alignment practice: regular touchpoints with CRO, CFO, and CMO to ensure they understand product's priorities and the trade-offs being made. Don't wait for them to be surprised. (See 
skills/vp-cpo-readiness-advisor/SKILL.md
for the Alliance Building branch.)
Deliverable: A shared organizational assessment, an initial strategic direction, and three to five active changes underway with clear rationale.
目标： 开始基于证据体系做决策，引入架构和方向，而非大规模转型。
步骤1：同步你的组织评估结果 不要自己藏着，把核心发现同步给你的老板和直接下属：“这是我了解到的这个组织的运作情况、优势和需要提升的地方，这是我下一季度的初步计划。”通过透明度建立信任，在行动前提前暴露分歧。
步骤2：运行你的第一份层级上下文地图 利用你建立的组织和战略清晰度，为团队指明方向——哪怕上层的公司战略还不明确。（完整方法见
skills/altitude-horizon-framework/SKILL.md
）你的团队一直在等上下文信息，给出你当前最准确的判断，并且承诺后续会迭代优化。
步骤3：启动人员沟通 现在你有证据支撑了，可以开展那些艰难的沟通了：
  • 璞玉型人才：给他们挑战性任务或者扩大权责范围
  • 放错位置的优秀人才：直接坦诚地沟通不匹配的情况和可选方案
  • 需要离职的人员：坦诚有温度地沟通，不要逃避
步骤4：有意识地建立高管联盟 到第3个月你已经知道核心参与者是谁，以及他们对产品团队的诉求是什么。启动每周对齐机制：定期和CRO、CFO、CMO沟通，确保他们了解产品的优先级和做出的取舍，不要等他们被动收到消息感到意外。（联盟搭建部分见
skills/vp-cpo-readiness-advisor/SKILL.md
）
交付物： 公开同步的组织评估报告、初步战略方向，以及3-5个正在推进、有明确合理性的调整动作。

Examples

示例

See 
examples/sample.md
for a full 30-60-90 diagnostic walkthrough with concrete artifacts and decisions by month.
完整的30-60-90天诊断流程、对应具体产出和每月决策示例见
examples/sample.md
。

Good: Consultant Mindset Preventing a Costly Mistake

正面案例：顾问思维避免高额损失

Situation: New CPO joins and immediately notices the team's longest-tenured PM is resistant, slow to deliver, and visibly unpopular with engineering.
Impulsive response: Put her on a performance plan in Month 1.
Consultant response: Keeps notes, asks questions. Discovers in Month 2 that she's the only person on the team who understands the legacy platform's architecture — and that a previous CPO already tried to push her out, creating the defensive behavior. She's strong but in the wrong role (PM scope requires stakeholder management she struggles with; technical architecture is where she adds irreplaceable value).
Outcome: She's moved into a technical product owner role by Month 3. Engineering's delivery velocity improves. The CPO avoids destroying an irreplaceable relationship.
场景： 新任CPO入职后马上发现团队任职时间最长的PM很抵触变化、交付慢，而且明显不受技术团队欢迎。
冲动应对： 第1个月就给她开绩效改进计划。
顾问思维应对： 做好记录，多问问题。第2个月发现她是团队里唯一一个懂 legacy 平台架构的人，之前的CPO就曾经想把她挤走，才导致她有防御行为。她是优秀人才但放错了位置：PM岗位需要的利益相关方沟通是她的短板，而技术架构是她能提供不可替代价值的地方。
结果： 第3个月她被调整为技术产品负责人，技术团队的交付速度提升，CPO避免了损失一位不可替代的核心员工。

Bad: Acting Before Understanding

反面案例：了解情况前贸然行动

Situation: New VP of Product hears in Week 2 that three PMs each have completely different formats for their roadmap documentation. She standardizes them in Week 3.
What she didn't know: Each format exists because of specific requirements from different internal stakeholder groups. The "inconsistency" was a feature, not a bug.
Outcome: Three sets of stakeholders lose the views they relied on. The VP spends Month 2 rebuilding goodwill she spent three weeks burning.
The diagnostic question she should have asked first: "Why does each team use a different format? What would break if they were unified?"
场景： 新任产品VP第2周听说3个PM的路线图文档格式完全不一样，第3周就要求统一格式。
她不知道的背景： 每个格式对应不同内部利益相关方的具体要求，“不统一”是特性而非bug。
结果： 三个利益相关方失去了他们依赖的视图，这位VP第2个月全在修复她三周消耗掉的好感度。
她本来应该先问的诊断问题： “为什么每个团队用不同的格式？如果统一的话会影响什么？”

Good: Surfacing Unwritten Strategy

正面案例：挖掘不成文战略

Situation: VP joins a company whose stated priority is "enterprise expansion." After 30 diagnostic conversations, he realizes the CEO has a specific enterprise customer in mind — a reference customer that would unlock a Series B — that has never been mentioned in any written strategy document.
How it surfaces: He asks an indirect question in his Month 2 reality-check: "When you imagine what success looks like at the end of this year, what does the portfolio look like?" The CEO mentions the target customer by name.
Outcome: The VP realigns two product teams' priorities around the capabilities that matter to that specific customer. Strategy becomes executable. Without surfacing the unwritten layer, he would have pursued a generic enterprise strategy that didn't move the actual needle.
场景： VP入职的公司公开优先级是“企业服务扩张”，经过30轮诊断沟通，他发现CEO有一个明确的目标企业客户——这个标杆客户能帮公司拿到B轮融资——但从来没在任何书面战略里提到过。
挖掘方法： 他在第2个月的信息核验里问了一个间接问题：“你想象今年年底的成功状态时，我们的产品组合是什么样的？”CEO提到了这个目标客户的名字。
结果： VP调整了两个产品团队的优先级，优先开发对这个特定客户重要的能力，战略变得可落地。如果没有挖掘出这层不成文的内容，他会做通用的企业服务战略，对实际目标完全没帮助。

Common Pitfalls

常见陷阱

Pitfall 1: Performing Action Instead of Building Evidence

陷阱1：为了表现果断而行动，而非构建证据

Symptom: Making structural announcements or process changes in Month 1 to signal decisive leadership
Consequence: You build on incomplete understanding. Reversals in Month 3 damage credibility more than patience in Month 1 would have.
Fix: Reframe patience as methodology, not passivity. "I'm in diagnostic mode for the first 30 days" is a confident statement when said clearly to your boss and team.
症状： 第1个月就发布架构调整或者流程变更公告，来展示自己是果断的领导者
后果： 你基于不完整的信息做决策，第3个月推翻之前的决定对公信力的损害，远大于第1个月表现出耐心的影响。
解决方法： 把耐心重新定义为方法论，而非被动。明确告诉老板和团队“我前30天处于诊断阶段”是很自信的表达。

Pitfall 2: Staying in Consultant Mode Too Long

陷阱2：停留在顾问模式太久

Symptom: Still gathering information in Month 3; no visible actions or decisions
Consequence: Organizational confidence erodes. People start to wonder if the new leader has opinions. Your boss starts to wonder if you can make decisions.
Fix: Month 3 is the action phase. You won't have complete information — no one ever does. Act on your best current evidence and commit to learning from what follows.
症状： 第3个月还在收集信息，没有可见的行动或者决策
后果： 组织信心下降，大家会怀疑新领导有没有自己的判断，你的老板会怀疑你能不能做决策。
解决方法： 第3个月就是行动阶段，你永远不会拿到100%完整的信息，基于当前最优的证据行动，并且承诺从后续结果中学习。

Pitfall 3: Trusting the Loudest Voice

陷阱3：相信声音最大的人

Symptom: Forming early opinions based on the most vocal, most accessible, or most persuasive person you met in Month 1
Consequence: You adopt one person's organizational narrative as ground truth. Decisions built on single-source information collapse when the rest of the organization provides context.
Fix: Pattern-match across multiple independent conversations. Only act on themes you've heard from three or more unrelated sources.
症状： 基于第1个月遇到的最敢说、最容易接触到、最有说服力的人的观点形成早期判断
后果： 你把某一个人的组织叙事当成客观事实，基于单一信息源做的决策，在其他团队成员补充背景信息后就会站不住脚。
解决方法： 跨多个独立对话匹配共性规律，只对三个以上不相关信息源都提到的主题采取行动。

Pitfall 4: Skipping the CEO Interview (Before Accepting)

陷阱4：接受offer前没和CEO沟通清楚

Symptom: Taking the CPO role without probing constraints, expectations, and talent assessment upfront
Consequence: You walk into a situation where the roadmap is locked, the timeline is impossible, or the CEO's mental model of the team is so wrong that your first six months are spent managing their misperceptions instead of leading.
Fix: The five questions in Phase 0 are not optional. Walk away from roles where the answers reveal fundamental misalignment. No role is worth a death march.
症状： 没提前问清楚约束、预期、人才评估就接受了CPO职位
后果： 你入职后发现路线图是锁死的、时间要求完全不可能、CEO对团队的判断错得离谱，你前6个月都在纠正他的错误认知，而不是做领导工作。
解决方法： 第0阶段的5个问题不是可选的，如果答案显示存在根本的认知不匹配，就放弃这个职位，没有什么工作值得你去做死亡行军。

Pitfall 5: Ignoring Executive Dysfunction

陷阱5：忽视高管层的 dysfunction

Symptom: Assuming that executive staff meetings will be mature, collaborative, and politics-free
Consequence: You're blindsided by alliances, personal agendas, and interpersonal dynamics that operate beneath the surface of every executive team.
Fix: Expect dysfunction. Patrick Lencioni's Five Dysfunctions of a Team applies to leadership teams as much as any other. Integrity gets tested more at higher levels, not less. Map the alliances in Month 1 as carefully as you map the product portfolio.
症状： 默认高管团队会议是成熟、协作、没有办公室政治的
后果： 你会对每个高管团队都存在的私下联盟、个人诉求、人际动态毫无准备，被打个措手不及。
解决方法： 预设存在dysfunction，帕特里克·兰西奥尼（Patrick Lencioni）的《团队协作的五大障碍》（Five Dysfunctions of a Team）对领导团队和其他团队都适用，层级越高对诚信的考验越大，而非越小。第1个月像梳理产品 portfolio 一样仔细梳理高管层的联盟关系。

References

参考资料

Related Skills

相关技能

  • skills/vp-cpo-readiness-advisor/SKILL.md
    — Interactive advisor for all four VP/CPO transition situations; the Alliance Building branch covers ongoing executive relationship management
  • skills/altitude-horizon-framework/SKILL.md
    — The Cascading Context Map technique referenced in Phase 3
  • skills/director-readiness-advisor/SKILL.md
    — The Director-level transition equivalent; relevant if you're coaching a new Director through their own onboarding
  • skills/vp-cpo-readiness-advisor/SKILL.md
    ——应对四类VP/CPO交接场景的交互式顾问，联盟搭建分支覆盖持续的高管关系管理
  • skills/altitude-horizon-framework/SKILL.md
    ——第3阶段提到的层级上下文地图技术
  • skills/director-readiness-advisor/SKILL.md
    ——总监级别的交接对应指南，如果你要辅导新总监入职可以参考

Source Material

来源资料

External Frameworks

外部框架

  • Michael Watkins, The First 90 Days — Foundational reference for structured leadership transitions
  • Patrick Lencioni, Five Dysfunctions of a Team — Diagnostic for executive team dysfunction
  • Marty Cagan, Empowered — Organizational dynamics and product leadership at scale
  • 迈克尔·沃特金斯（Michael Watkins）《上任头90天》（The First 90 Days）——结构化领导力交接的基础参考
  • 帕特里克·兰西奥尼（Patrick Lencioni）《团队协作的五大障碍》（Five Dysfunctions of a Team）——高管团队功能障碍诊断框架
  • 马蒂·卡根（Marty Cagan）《赋能》（Empowered）——规模化下的组织动态和产品领导力参考