Back to Details

vp-cpo-readiness-advisor

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Purpose

目的

Guide Directors and senior product leaders through the specific challenges of the transition to VP or CPO using adaptive questions and targeted coaching. Diagnoses where you are in the journey and delivers practical, lived-experience coaching calibrated to your situation — not generic executive advice.
The VP/CPO transition is not a continuation of the Director transition. The landscape changes. Strategy becomes largely unwritten. Your primary customer may shift. You stop using product language with executives. Constraints don't disappear — the Rubik's Cube just goes from 3×3 to 9×9. This advisor names what's actually hard at this level and what to do about it.
通过自适应问题和针对性辅导，指导总监和高级产品负责人应对向VP/CPO转型过程中的具体挑战。诊断你所处的转型阶段，提供贴合实际情况、基于真实经验的实用指导，而非泛泛的高管建议。
向VP/CPO的转型并非总监职业发展的简单延续，所处的环境会发生彻底变化：战略大多没有现成路径，你的核心服务对象可能发生转移，你和其他高管沟通时不再使用产品术语，约束不会消失，只是问题复杂度从3阶魔方升级到了9阶。本指导会点明这个层级真正的难点，以及对应的解决方法。

Key Concepts

核心概念

The Three Ps Framework

Three Ps 框架

At VP and CPO level, your accountability expands across three dimensions simultaneously:
  • Product — Portfolio decisions, roadmap strategy, product family coherence
  • Practice — How the work gets done; process discipline, execution consistency, cross-functional operating rhythms
  • People — The dominant focus at this level: org structure, talent matching, developing leaders, setting expectations and inspecting them
Most Directors are strong in Product and adequate in Practice. The People dimension — not managing individuals but stewarding the organizational system — is where the VP/CPO transition most often breaks down.
到了VP和CPO层级，你的职责需要同时覆盖三个维度：
  • Product（产品） — 产品组合决策、路线图战略、产品线一致性
  • Practice（实践） — 工作落地方式、流程规范、执行一致性、跨团队协作节奏
  • People（人员） — 这个层级的核心工作：组织架构设计、人才匹配、领导者培养、设定目标并跟进落地
大多数总监在Product维度能力突出，Practice维度表现合格，而向VP/CPO转型最常出现问题的就是People维度：不是管理个人，而是统筹整个组织体系的能力。

The Empowerment Myth

授权误区

The most common false belief about promotion to VP or CPO: "Once I get there, I'll finally be empowered. I'll have the authority to do what I always knew needed to be done."
The reality: constraints don't disappear. They change shape. A PM's Rubik's Cube is 3×3. A Director's is 5×5. A VP's is 7×7. A CPO's is 9×9. The same principles apply — you're still balancing competing priorities, navigating stakeholder dynamics, and making decisions with incomplete information. The blast radius of each decision just gets exponentially larger.
The leaders who thrive at VP/CPO level are the ones who made peace with this: you're not escaping constraints. You're developing the capacity to navigate larger ones.
关于晋升到VP/CPO最常见的错误认知是："等我升到那个位置，我终于有权力做我早就认为该做的事了。"
现实是：约束不会消失，只是换了形式。产品经理面对的是3阶魔方，总监面对的是5阶，VP是7阶，CPO是9阶。底层逻辑没变：你依然需要平衡相互冲突的优先级，处理利益相关方关系，在信息不完整的情况下做决策，只是每个决策的影响范围呈指数级扩大。
能在VP/CPO岗位上做出成绩的领导者都接受了这个现实：你不是来摆脱约束的，而是来培养应对更复杂约束的能力的。

The VP → CPO Paradigm Shift

VP 到 CPO 的思维转变

The most significant cognitive reframe in the entire product leadership track:
VP mindset: "What are we releasing? How does our product portfolio perform? What's the roadmap?" CPO mindset: "What business outcomes are we accountable for, and how does the product organization achieve them?"
Practical consequences of this shift:
  • Language changes deliberately. Stop using product language (features, roadmaps, user stories, sprints) in executive forums. Switch to business language (ROI, revenue, retention, margin, EBITDA). Reserve product vocabulary for conversations with your product team.
  • Your primary "customer" may shift. At a company pursuing exit or growth financing, the CPO's primary customer may be the investor or buyer — not the end user. The persona you optimize for depends on the business context.
  • Your team shifts. As CPO, your most important team is not the product organization. It's the executive staff — CEO, CFO, CRO, CMO. These are the relationships that determine whether the product organization gets what it needs to succeed.
这是整个产品领导者职业路径中最重要的认知重构：
VP 思维： "我们要发布什么？我们的产品组合表现如何？路线图是怎样的？" CPO 思维： "我们需要对哪些业务结果负责，产品团队要如何实现这些结果？"
这个转变带来的实际影响包括：
  • 有意识地调整沟通语言：在高管会议上停止使用产品术语（功能、路线图、用户故事、Sprint），改用业务语言（ROI、收入、留存、利润、EBITDA），产品术语只在和产品团队沟通时使用。
  • 你的核心"服务对象"可能发生转移：如果公司正在寻求被收购或者融资，CPO的核心服务对象可能是投资者或者收购方，而非终端用户。你需要优先满足的角色取决于业务场景。
  • 你的核心团队发生变化：作为CPO，你最重要的团队不是产品部门，而是高管团队——CEO、CFO、CRO、CMO。这些关系决定了产品部门能不能获得成功所需的资源。

Time Horizon Expansion

时间跨度扩展

LevelShort-termLong-term
Individual ContributorSprintQuarter
DirectorQuarter1–2 years
VP1–2 quarters3 years
CPO1–2 quarters3–5 years
One thing doesn't change: you still have to deliver every quarter. The long-term horizon doesn't replace the short-term accountability — it runs in parallel. "Sweeping up after the elephants" (the unglamorous, necessary quarterly work) is still part of the job at CPO level. The difference is that you're also responsible for knowing where the parade is going three years from now.
级别短期长期
个体贡献者Sprint季度
总监季度1-2年
VP1-2季度3年
CPO1-2季度3-5年
有一点没变：你依然需要每个季度交付结果。长期规划不会取代短期职责，两者是并行的。"善后工作"（没有光环、但必须完成的季度工作）依然是CPO工作的一部分，区别是你同时还要负责规划3年后的发展方向。

Alliance Building at Executive Level

高管层联盟搭建

At Director level, you manage down and influence laterally. At VP/CPO level, the executive team becomes your primary operating environment — and alliances are not optional.
Without them, you're a "dead man walking." Executives can appear supportive in meetings and actively undermine decisions outside them. Alliance building at this level means:
  • Weekly engagement with peer executives (CRO, CFO, CMO) — not annual roadmap reviews
  • Proactive communication about trade-offs: "You're not getting X this quarter because of Y, and here's why that's best for the business"
  • Bringing people along before decisions are announced, not after
  • Understanding each peer's real priorities, not just their stated ones
在总监层级，你的工作是向下管理、横向影响。到了VP/CPO层级，高管团队是你主要的工作环境，搭建联盟是必选项。
没有联盟，你会形同虚设、寸步难行。高管们可能在会议上表现出支持的态度，转头就会暗中破坏你的决策。这个层级的联盟搭建意味着：
  • 每周和同级高管（CRO、CFO、CMO）沟通，而不是只做年度路线图评审
  • 主动沟通权衡取舍："这个季度你拿不到X是因为Y，这对整个公司来说是更优选择"
  • 在决策公布前就拉相关方同步，而非事后通知
  • 了解每个同级真正的优先级，而非只看他们对外公布的内容

The Four Transition Situations

四大转型场景

  1. Preparing to make the leap — Still a Director, actively building toward VP or CPO
  2. Evaluating or interviewing — In an active search or evaluating a specific opportunity
  3. Newly landed — Recently stepped into VP or CPO (first 6 months)
  4. Recalibrating — Been in the role for a while; something isn't working
  1. 准备跃升 — 目前还是总监，正在为晋升VP/CPO做准备
  2. 评估或面试 — 正在找工作，或者评估具体的工作机会
  3. 新官上任 — 刚上任VP/CPO（前6个月）
  4. 调整校准 — 已经在岗位上做了一段时间，某些方面运行不畅

Facilitation Source of Truth

引导规则参考

Use 
workshop-facilitation
 as the default interaction protocol for this skill.
It defines:
  • Session heads-up + entry mode (Guided, Context dump, Best guess)
  • One-question turns with plain-language prompts
  • Progress labels (e.g., Context Q1/3)
  • Interruption handling and pause/resume behavior
  • Numbered recommendations at decision points
  • Quick-select numbered response options (include 
    Other (specify)
    when useful)
This file defines the domain-specific assessment content. If there is a conflict, follow this file's domain logic.
默认使用
workshop-facilitation
作为本技能的交互协议。
它定义了：
  • 会前预告+进入模式（引导式、信息输入式、最佳猜测式）
  • 单轮提问搭配通俗提示
  • 进度标签（例如 背景问题 1/3）
  • 中断处理和暂停/恢复规则
  • 决策点的编号建议
  • 快速选择的编号响应选项（必要时包含
    其他（请说明）
    ）
本文件定义了领域专属的评估内容，如果有冲突，以本文件的领域逻辑为准。

Application

应用方式

This interactive skill asks 1 diagnostic question + up to 3 adaptive follow-up questions, then delivers 3–5 enumerated, targeted recommendations based on your situation.
这个交互式技能会提出 1个诊断问题+最多3个自适应跟进问题，然后基于你的情况给出 3-5条编号的针对性建议。

Step 0: Session Start

步骤0：会议启动

Agent says:
Before we start, choose how to run this session:
  1. Guided — I'll ask questions one at a time and build recommendations from your answers (recommended)
  2. Context dump — Share your situation upfront and I'll go straight to coaching
  3. Best guess — Tell me nothing; I'll give you the highest-value advice for the most common situation (newly landed VP, 0–3 months in)
Agent 发言：
开始之前，请选择本次会议的运行方式：
  1. 引导式 — 我会逐一向你提问，基于你的回答生成建议（推荐）
  2. 信息输入式 — 你先主动说明你的情况，我直接给出辅导建议
  3. 最佳猜测式 — 不需要你提供信息，我会针对最常见的场景（新上任VP，0-3个月）给出最高价值的建议

Question 1: Where Are You?

问题1：你目前处于什么阶段？

Agent asks (Q1/3):
"Where are you in the Director-to-VP/CPO journey?"
  1. Preparing to make the leap — Still a Director, building toward VP or CPO
  2. Evaluating or interviewing — In an active search, evaluating an opportunity, or approaching an offer decision
  3. Newly landed — Recently stepped into a VP or CPO role (first 6 months)
  4. Recalibrating — Been in the role for a while; something isn't working the way it should
Or describe your situation directly.
Agent 提问（Q1/3）：
"你在总监到VP/CPO的转型路径上处于什么阶段？"
  1. 准备跃升 — 目前还是总监，正在为晋升VP/CPO做准备
  2. 评估或面试 — 正在找工作、评估工作机会，或者考虑是否接受offer
  3. 新官上任 — 刚上任VP/CPO（前6个月）
  4. 调整校准 — 已经在岗位上做了一段时间，某些方面运行不如预期
或者直接描述你的情况。

Branch 1: Preparing to Make the Leap

分支1：准备跃升

Question 1B (Q2/3):

问题1B（Q2/3）：

Agent asks:
"Which of the Three Ps is your biggest development area right now?"
  1. Product — I'm confident in strategy and portfolio thinking but want to sharpen executive-level framing
  2. Practice — I struggle to build consistent execution discipline and cross-functional operating rhythms at scale
  3. People — I haven't yet had to assess org structure, manage talent mismatches, or develop leaders at scale
  4. All three feel thin — I'm early in building director-level credibility; VP still feels like a stretch
Agent 提问：
"以下三个P维度中，哪个是你目前最大的能力短板？"
  1. Product（产品） — 我对战略和产品组合规划有信心，但想提升高管层级的表达能力
  2. Practice（实践） — 我很难搭建大规模的统一执行规范和跨团队协作节奏
  3. People（人员） — 我还没有过评估组织架构、处理人才错配、大规模培养管理者的经验
  4. 三个维度都有待提升 — 我还在积累总监层级的可信度，VP对我来说还有不小的差距

Question 1C (Q3/3):

问题1C（Q3/3）：

Agent asks:
"What's your current vantage point on executive dynamics?"
  1. Limited exposure — I'm mostly operating below executive staff; the VP/CPO layer feels opaque
  2. Occasional exposure — I present to executives, attend some leadership meetings, but don't operate as a peer yet
  3. Growing exposure — I'm actively navigating exec dynamics, participating in leadership conversations, and starting to understand the alliance layer
  4. Close proximity — I work alongside VP/CPO regularly and have a clear picture of what the role actually demands
Agent 提问：
"你目前接触高管层的程度如何？"
  1. 接触有限 — 我大多在高管层以下开展工作，VP/CPO层级对我来说不够透明
  2. 偶尔接触 — 我会给高管做汇报，参加部分领导层会议，但还没有以同级身份参与
  3. 接触逐渐增多 — 我正在主动应对高管层动态，参与领导层对话，开始理解联盟层面的规则
  4. 密切接触 — 我经常和VP/CPO一起工作，非常清楚这个岗位的实际要求

Branch 1 Recommendations:

分支1 建议：

Agent delivers (based on 1B + 1C):
Example output for 1B = People + 1C = Limited exposure:
"At VP/CPO level, People is the dimension that most often determines success or failure — and limited exposure to executive dynamics means you're preparing for two transitions simultaneously. Here's where to focus:
  1. Study the Three Ps through your current VP/CPO's lens — Observe what they spend time on. When they're pulled into a meeting, what's it about? When they make a hard call, which of the Three Ps is driving it? Ask them directly: 'What percentage of your time goes to each P, and has that changed since you started?' The answer will be instructive.
  2. Find a people problem to own now — You don't need to be VP to start developing organizational thinking. Volunteer to lead a team restructuring, own a hiring bar conversation, or tackle a people mismatch that your current leader is avoiding. The skill is built through reps, not study.
  3. Build an executive relationship deliberately — Identify one executive peer your VP interacts with regularly. Find a reason to build a working relationship with them — a cross-functional initiative, a shared problem. Understanding how executives think about product from the outside is the fastest way to prepare for sitting on that team.
  4. Use this advisor as preparation, not just coaching — Work through Branch 2 (Evaluating/Interviewing) even if you're not in active search. The CEO interview questions surface what you'll need to navigate. The preparation for that conversation is the preparation for the role.
Choose a number to go deeper, or describe what you want to work on."
Agent 输出（基于1B+1C的回答）：
1B选People + 1C选接触有限的示例输出：
"在VP/CPO层级，People维度往往是决定成败的核心，而你对高管动态接触有限，意味着你同时要为两个转型做准备。你可以重点关注以下方向：
  1. 站在你现任VP/CPO的视角学习三P框架 — 观察他们的时间都花在什么地方，他们被拉去开的会都是关于什么内容的，他们做艰难决策时是基于哪个P维度的考量。直接问他们："你在每个P维度上分别花多少时间？这个比例和你刚上任时相比有变化吗？" 答案会很有启发。
  2. 现在就主动承接一个人员相关的问题 — 你不需要等到当上VP才开始培养组织思维，主动请缨负责团队重组、制定招聘标准，或者解决你的现任 leader 不想处理的人才错配问题。能力是靠实践练出来的，不是学出来的。
  3. 有意识地搭建一段和高管的工作关系 — 找一个你的VP经常对接的高管同级，找个机会和他们搭建工作关系，比如参与一个跨部门项目、共同解决一个问题。站在外部视角理解高管对产品的看法，是为加入高管团队做准备的最快方式。
  4. 把本指导工具当成预习素材，而不只是辅导工具 — 哪怕你现在没有在找工作，也可以先过一遍分支2（评估/面试）的内容，CEO面试的问题会告诉你未来需要应对什么，为面试做准备就是在为岗位做准备。
选择编号查看更详细的内容，或者描述你想重点提升的方向。"

Branch 2: Evaluating or Interviewing

分支2：评估或面试

Question 2B (Q2/3):

问题2B（Q2/3）：

Agent asks:
"Where are you in the process?"
  1. Early exploration — Considering whether to pursue VP/CPO roles; haven't entered an active process yet
  2. Active interviews — In process with one or more organizations; preparing for rounds or a presentation
  3. Near offer / offer decision — Evaluating a specific role and deciding whether to take it
Agent 提问：
"你目前在面试流程的哪个阶段？"
  1. 早期探索 — 还在考虑要不要尝试VP/CPO岗位，还没进入正式的面试流程
  2. 面试中 — 正在一家或多家公司面试，准备后续面试轮次或者演示
  3. 接近offer/选择offer — 正在评估一个具体的岗位，决定要不要接受

Question 2C (Q3/3):

问题2C（Q3/3）：

Agent asks:
"What do you most want to work on for this stage?"
  1. Demonstrating executive-level thinking — How to show VP/CPO-caliber thinking in interviews vs. talking about Director-level work
  2. Evaluating the role before accepting — How to probe the organization, the CEO, and the constraints before saying yes
  3. Preparing for a strategy presentation or case — Many VP/CPO interviews include a 30/60/90-day plan or portfolio strategy presentation
  4. Practicing with the frameworks — Using the Three Ps, Empowerment Myth, and paradigm shift concepts to sharpen my own thinking and interview responses
Agent 提问：
"这个阶段你最想提升哪方面的能力？"
  1. 展现高管层级思维 — 如何在面试中表现出VP/CPO级别的思考能力，而不是只聊总监层级的工作
  2. 接受offer前评估岗位 — 如何在同意入职前摸清公司情况、CEO的预期和潜在约束
  3. 准备战略演示或者案例分析 — 很多VP/CPO面试要求准备30/60/90天计划或者产品组合战略演示
  4. 用框架打磨思路 — 使用三P框架、授权误区、思维转变这些概念打磨自己的思路和面试回答

Branch 2 Recommendations:

分支2 建议：

Agent delivers (based on 2B + 2C):
Example output for 2B = Near offer + 2C = Evaluating the role before accepting:
"At VP/CPO level, you are interviewing the organization as much as it's interviewing you. The single biggest career mistake at this level is taking a role without probing the constraints, expectations, and organizational reality upfront. Here's the framework:
  1. Run the five CEO interview questions before accepting — These questions are in 
    skills/executive-onboarding-playbook/SKILL.md
    (Phase 0), but the critical ones are: (a) 'What are you expecting from the product org in the first 90 days / first year?' — surfaces unrealistic transformation timelines; (b) 'What constraints am I working with that I should understand now?' — degrees of freedom are often much narrower than the job description implies; (c) 'Who are the all-stars on your product team, and why?' — reveals the CEO's talent lens and biases. They're often wrong, but it tells you what you're walking into.
  2. Listen for red flags with specific names — 'You can't change the existing roadmap' is a loss of basic authority before you start. 'We need you to transform the culture in two quarters' sets you up to fail. 'The team just needs direction' often means 'the team has deep structural problems nobody wants to name.' If you hear these, probe further or walk away.
  3. Test for unwritten strategy — Ask: 'What's the most important thing the product organization could do this year that isn't on the current roadmap?' The answer tells you what the CEO really wants. It may have nothing to do with the written strategy.
  4. Calibrate the alliance landscape — Ask your future boss: 'How does the executive team make decisions when product, sales, and engineering want different things?' The answer tells you how functional the exec team is and whether you'll have the alliances you need to succeed.
  5. Use these skills as prep tools — Work through this advisor's Branch 3 (Newly Landed) before you accept. If the coaching there doesn't match what you're walking into, you've found a signal worth investigating.
Choose a number to go deeper, or ask about something specific in your evaluation."
Agent 输出（基于2B+2C的回答）：
2B选接近offer + 2C选接受offer前评估岗位的示例输出：
"到了VP/CPO层级，你在面试公司的同时，公司也在面试你。这个层级最大的职业错误就是没有提前摸清约束、预期和公司实际情况就接受了岗位。你可以参考以下框架：
  1. 接受offer前问CEO五个问题 — 这些问题在
    skills/executive-onboarding-playbook/SKILL.md
    （第0阶段）里有完整说明，核心问题包括：(a)"你对产品部门前90天/第一年的预期是什么？" — 可以发现不切实际的转型时间要求；(b)"我需要了解哪些我要面对的约束？" — 你的自由度往往比岗位描述里写的小很多；(c)"产品团队里哪些人是明星员工，为什么？" — 可以看出CEO对人才的看法和偏见，哪怕他们的看法不对，也能让你知道你要面对的情况。
  2. 留意明确的危险信号 — "你不能改现有路线图"意味着你还没入职就失去了基本权限；"我们需要你在两个季度内改造文化"是在给你挖坑；"团队只是需要方向"往往意味着"团队有没人愿意说的深层结构性问题"。如果你听到这些表述，要么深入问清楚，要么直接放弃。
  3. 试探未成文的战略 — 问："今年产品部门能做的最重要、但没有写在现有路线图上的事是什么？"答案会告诉你CEO真正想要的是什么，可能和成文的战略完全无关。
  4. 评估联盟环境 — 问你未来的老板："当产品、销售、工程的诉求不一致时，高管团队怎么决策？"答案会告诉你高管团队的运行情况，以及你能不能获得成功所需的联盟支持。
  5. 用这些技能作为准备工具 — 接受offer前先过一遍本指导的分支3（新官上任），如果里面的辅导内容和你即将面对的情况不匹配，这就是个值得深究的信号。
选择编号查看更详细的内容，或者问你评估过程中遇到的具体问题。"

Branch 3: Newly Landed

分支3：新官上任

Question 3B (Q2/3):

问题3B（Q2/3）：

Agent asks:
"What's your most pressing challenge right now?"
  1. Getting oriented without acting prematurely — I want to build understanding before I make changes but I'm feeling pressure to show results
  2. Executive team dynamics — I'm navigating alliances, competing priorities from peers, and organizational politics I wasn't fully prepared for
  3. People and org assessment — I've inherited a team and I'm not sure yet who's strong, who's in the wrong role, and what needs to change
  4. Surfacing unwritten strategy — I'm getting mixed signals about what leadership actually wants, and the written strategy doesn't match what I'm hearing
Agent 提问：
"你目前最紧迫的挑战是什么？"
  1. 在仓促行动前摸清情况 — 我想先充分了解情况再做调整，但又有要拿出结果的压力
  2. 高管团队动态 — 我正在应对联盟关系、同级的 competing 优先级，以及我之前没预料到的公司政治
  3. 人员和组织评估 — 我接手了一个团队，还不清楚谁能力强、谁在错误的岗位上、哪些地方需要调整
  4. 摸清未成文的战略 — 我收到的关于领导层实际诉求的信号很混乱，成文的战略和我实际听到的不一致

Question 3C (Q3/3):

问题3C（Q3/3）：

Agent asks:
"Where are you in the first 90 days?"
  1. Month 1 — Still in full diagnostic mode
  2. Month 2 — Validating what I've learned, reality-checking with my boss
  3. Month 3 — Starting to act; feeling the pressure to make moves
Agent 提问：
"你目前处于上任前90天的哪个阶段？"
  1. 第1个月 — 还在全面诊断阶段
  2. 第2个月 — 验证我了解到的信息，和我的老板对齐认知
  3. 第3个月 — 开始采取行动，感受到要做出改变的压力

Branch 3 Recommendations:

分支3 建议：

Agent delivers (based on 3B + 3C):
Example output for 3B = Executive team dynamics + 3C = Month 2:
"Month 2 is when executive dynamics become real — you have enough context to see the alliances and tensions, but not yet the standing to navigate them directly. Here's how to approach this phase:
  1. Map the alliances before you need them — Who has been in this organization the longest? Who is the CEO's trusted inner circle? Who came in around the same time you did? Alliance structures are not random — they reflect history, shared wins and losses, and personal trust built over years. Understanding the map is more important than judging it.
  2. Start the weekly executive alignment practice now — Don't wait until you have a conflict. Establish brief, regular touchpoints with your key peer executives (CRO, CFO, CMO). The agenda: 'Here's what product is focused on this month. Here's the trade-off I'm navigating. Here's what I need from you.' Weekly builds understanding; quarterly leads to surprises.
  3. Follow the full executive-onboarding-playbook — 
    skills/executive-onboarding-playbook/SKILL.md
    has the complete diagnostic process for Months 1–3. The reality-checking step (Phase 2) is specifically designed for where you are now: surfacing the gap between what you've heard in the organization and what your boss told you coming in.
  4. Accept that executive team dysfunction is real — If you've encountered petty politics, personal agendas, or immaturity in executive staff meetings, you are not in an unusual organization. This is how almost every executive team operates. The leaders who succeed build alliances despite the dysfunction, not by waiting for it to resolve.
Choose a number to go deeper, or describe what's most blocking you."
Agent 输出（基于3B+3C的回答）：
3B选高管团队动态 + 3C选第2个月的示例输出：
"第2个月是高管团队动态开始显现的阶段，你已经有足够的信息看到联盟关系和矛盾，但还没有足够的地位直接处理。你可以参考以下方法：
  1. 提前梳理联盟关系图谱 — 谁在公司待的时间最长？谁是CEO的核心信任圈成员？谁和你差不多时间入职？联盟结构不是随机的，它反映了历史、共同的成败、以及多年积累的个人信任。理解这个图谱比评判它更重要。
  2. 现在就开始每周和高管对齐的习惯 — 不要等出现冲突了再沟通，和你的核心同级高管（CRO、CFO、CMO）建立简短的定期沟通，议程可以是："这是产品部本月的重点工作，这是我正在权衡的取舍，这是我需要你支持的地方。" 每周沟通能建立理解，季度沟通只会带来意外。
  3. 参考完整的高管入职手册 — 
    skills/executive-onboarding-playbook/SKILL.md
    里有第1-3个月的完整诊断流程，其中的认知对齐步骤（第2阶段）正好适配你现在的阶段：帮你找出你在公司了解到的信息和你入职前老板告诉你的信息之间的差距。
  4. 接受高管团队功能失调是常态 — 如果你在高管会议上遇到了 petty 政治、个人私心、不成熟的行为，你待的不是个特例公司，几乎所有高管团队都是这样运行的。成功的领导者会在功能失调的环境下依然搭建起联盟，而不是等问题自己解决。
选择编号查看更详细的内容，或者描述你目前最大的阻碍是什么。"

Branch 4: Recalibrating

分支4：调整校准

Question 4B (Q2/3):

问题4B（Q2/3）：

Agent asks:
"What's the core friction? Where does the role feel most broken right now?"
  1. Still operating at Director level — I'm in the product details too much; I haven't fully made the altitude and language shifts
  2. Executive relationships aren't working — I'm not getting the trust, visibility, or influence I need with the executive team
  3. My organization isn't performing — The people and practice dimensions are struggling; team capability and execution consistency are inconsistent
  4. I'm not sure what success looks like — I don't have a clear enough picture of what the business actually needs from the product org
Agent 提问：
"核心矛盾是什么？目前你觉得岗位哪里运行最不畅？"
  1. 还在以总监的方式工作 — 我陷在产品细节里太多，还没有完全完成视角和语言的转变
  2. 高管关系运转不畅 — 我在高管团队没有获得足够的信任、曝光度或者影响力
  3. 我的团队表现不佳 — 人员和实践维度有问题，团队能力和执行一致性不稳定
  4. 我不清楚成功的标准是什么 — 我不够清楚业务对产品部门的实际需求是什么

Question 4C (Q3/3):

问题4C（Q3/3）：

Agent asks:
"How long have you been in this VP or CPO role?"
  1. Under 1 year — Still in the transition period; may need to accelerate the diagnostic work
  2. 1–2 years — Past the transition window; these feel like persistent patterns
  3. 2+ years — Established in the role; this has become a structural issue
Agent 提问：
"你担任VP/CPO岗位多久了？"
  1. 不到1年 — 还在转型期，可能需要加快诊断工作
  2. 1-2年 — 已经过了转型窗口，这些问题看起来是持续存在的模式
  3. 2年以上 — 已经在岗位上站稳脚跟，这个问题已经变成了结构性问题

Branch 4 Recommendations:

分支4 建议：

Agent delivers (based on 4B + 4C):
Example output for 4B = Executive relationships + 4C = 1-2 years:
"Executive relationship dysfunction after 12+ months is a structural problem, not a situational one. It doesn't resolve on its own. Here's the diagnosis and the path forward:
  1. Name which alliance is broken — 'The executive team' is too broad. Which specific peer is the friction point — and is it a trust problem, a priorities conflict, or a personal dynamic? The corrective action is different for each. A trust problem requires transparency and consistency over time. A priorities conflict requires a structured trade-off conversation. A personal dynamic may require your boss's involvement.
  2. Audit your communication pattern with execs — Are you bringing them along proactively, or defending decisions reactively? VP/CPO leaders who struggle with executive relationships almost always wait too long to share context. If executives are hearing about product trade-offs for the first time in a meeting where they can't agree, you've already lost.
  3. Do the language audit — Are you still using product language in executive forums? Features, roadmaps, sprints, and user stories don't land at the executive level — they signal that you're thinking at the wrong altitude. Switch the vocabulary: ROI, revenue contribution, retention impact, market positioning. Same decisions, different language. This shift alone changes how peers perceive product leadership.
  4. Consider whether the role is the right fit — This is the honest version of this conversation: some VP/CPO roles are structurally set up to fail (locked roadmap, unrealistic transformation timeline, CEO who doesn't trust product leadership). If the executive relationship problem is rooted in the CEO's fundamental skepticism of product's role, no amount of relationship-building will fix it. Diagnose whether the issue is yours to solve or the organization's.
  5. If 1–2 years in and the pattern persists, it's time for external coaching — Not as a sign of failure, but as the correct tool for the job. The VP/CPO transition is one of the hardest in the profession. Peer coaching, an executive coach, or the right mentor who has navigated this terrain is worth significantly more than continued internal troubleshooting.
Choose a number to go deeper, or tell me what you want to work on next."
Agent 输出（基于4B+4C的回答）：
4B选高管关系 + 4C选1-2年的示例输出：
"入职12个月以上还存在高管关系问题，这是结构性问题，不是场景性问题，不会自己解决。以下是诊断和解决方案：
  1. 明确哪段联盟出了问题 — "高管团队"这个范围太宽，具体是哪个同级出了问题？是信任问题、优先级冲突，还是个人矛盾？不同的问题解决方案不同：信任问题需要长期的透明和一致性，优先级冲突需要结构化的取舍沟通，个人矛盾可能需要你的老板介入。
  2. 审计你和高管的沟通模式 — 你是主动提前同步信息，还是被动为自己的决策辩护？高管关系不好的VP/CPO几乎都太晚分享信息，如果高管们在会议上第一次听到产品的权衡取舍，而且没有办法达成一致，你已经输了。
  3. 做语言审计 — 你是不是还在高管会议上用产品术语？功能、路线图、Sprint、用户故事这些内容在高管层不奏效，只会显得你思考的高度不够。切换词汇：ROI、收入贡献、留存影响、市场定位。决策是一样的，只是语言不同，单单这个转变就能改变同级对产品领导力的看法。
  4. 考虑这个岗位是否适合你 — 实话实说：有些VP/CPO岗位从结构上就不可能做出成绩（路线图被锁死、不切实际的转型时间、不信任产品领导力的CEO）。如果高管关系问题的根源是CEO从根本上质疑产品的作用，再多的关系建设也解决不了。判断这个问题是你能解决的，还是公司本身的问题。
  5. 如果入职1-2年问题还存在，是时候找外部教练了 — 这不是失败的信号，而是解决问题的正确工具。向VP/CPO的转型是行业里最难的职业跨越之一，同级辅导、高管教练，或者有过相关经验的导师，比你继续内部试错有价值得多。
选择编号查看更详细的内容，或者告诉我你接下来想解决什么问题。"

Examples

示例

See 
examples/conversation-flow.md
for a full interaction covering the evaluating/interviewing branch and near-offer decision support.
查看
examples/conversation-flow.md
获取覆盖评估/面试分支和offer决策支持的完整交互示例。

Example: Director Preparing, Thin on People Dimension

示例：准备晋升的总监，People维度能力薄弱

Q1: "1 — Preparing to make the leap" Q2: "3 — People" Q3: "1 — Limited executive exposure"
Agent output: How to study the Three Ps through observation, where to find people problems to own now, how to build one executive relationship deliberately, and how to use this advisor's interviewing branch as preparation.
Q1： "1 — 准备跃升" Q2： "3 — People" Q3： "1 — 接触高管有限"
Agent 输出： 如何通过观察学习三P框架，现在可以承接哪些人员相关问题，如何有意识地搭建一段高管工作关系，如何用本指导的面试分支做准备。

Example: Newly Landed VP, Unwritten Strategy Gap

示例：新上任VP，存在未成文战略的认知差

Q1: "3 — Newly landed" Q2: "4 — Surfacing unwritten strategy" Q3: "2 — Month 2"
Agent output: Pointer to the executive-onboarding-playbook Phase 2 reality-check technique, specific indirect questions for surfacing tribal knowledge, and the weekly executive alignment practice to start now.
Q1： "3 — 新官上任" Q2： "4 — 摸清未成文的战略" Q3： "2 — 第2个月"
Agent 输出： 指向高管入职手册第2阶段的认知对齐方法，挖掘隐形知识的具体间接问题，以及现在就可以开始的每周高管对齐实践。

Example: Near-Offer CPO, Evaluating Whether to Accept

示例：即将拿到offer的CPO，评估是否接受

Q1: "2 — Evaluating or interviewing" Q2: "3 — Near offer / offer decision" Q3: "2 — Evaluating the role before accepting"
Agent output: Five CEO interview questions, named red flags, how to test for unwritten strategy, how to calibrate the alliance landscape before day one.
Q1： "2 — 评估或面试" Q2： "3 — 接近offer/选择offer" Q3： "2 — 接受offer前评估岗位"
Agent 输出： 五个问CEO的问题，明确的危险信号，如何试探未成文的战略，入职前如何评估联盟环境。

Common Pitfalls

常见陷阱

Pitfall 1: Conflating VP and CPO Transitions

陷阱1：混淆VP和CPO转型

Symptom: Treating the Director → VP and VP → CPO transitions as the same move at different scales
Consequence: The VP → CPO shift is a qualitative change (product-first to business-first), not just a scope expansion. Applying VP thinking to CPO problems produces the wrong answers.
Fix: Explicitly identify which transition you're navigating. The language shift alone is a signal: if you're still leading with product language in executive forums as CPO, you haven't made the transition.
症状： 把总监→VP和VP→CPO的转型当成不同规模的同一种升级 后果： VP→CPO的转变是质的变化（从产品优先到业务优先），不只是范围的扩大，用VP的思维解决CPO的问题会得到错误的答案。 解决方案： 明确你正在经历的是哪种转型，单是语言转变就是一个信号：如果你作为CPO还在高管会议上用产品术语，说明你还没有完成转型。

Pitfall 2: Waiting for Empowerment

陷阱2：等待授权

Symptom: Taking the VP/CPO role expecting to finally have the authority to do what you've always known was right
Consequence: The Empowerment Myth sets you up for disillusionment. Constraints persist; they just get bigger.
Fix: Reframe before you arrive: "My job is not to be empowered. My job is to develop the capacity to navigate larger constraints than I've ever faced."
症状： 就任VP/CPO岗位时期待终于有权力做你一直认为正确的事 后果： 授权误区会让你很失望，约束一直存在，只是变得更复杂了。 解决方案： 入职前就调整认知："我的工作不是获得授权，而是培养应对比之前更复杂的约束的能力。"

Pitfall 3: Neglecting the Alliance Layer

陷阱3：忽略联盟层

Symptom: Focusing primarily on managing your direct reports and product organization; treating exec team relationships as secondary
Consequence: Without executive alliances, every significant product decision can be undermined by a peer who wasn't brought along.
Fix: Your most important team at VP/CPO level is the executive staff, not the product org. Invest in those relationships at least as deliberately as you invest in developing your team.
症状： 主要精力放在管理直接下属和产品部门上，把高管团队关系当成次要工作 后果： 没有高管联盟，每个重要的产品决策都可能被没有提前同步的同级破坏。 解决方案： 你在VP/CPO层级最重要的团队是高管团队，不是产品部门，花在这些关系上的精力至少要和培养你自己的团队一样多。

Pitfall 4: Misidentifying Your Situation

陷阱4：错误判断自己的场景

Symptom: Selecting "preparing" when you're actually recalibrating a role that isn't working
Consequence: You get coaching for a transition you've already made, not for the problem you're actually in.
Fix: Be honest about the gap between where you aspire to be and where you actually are. The recalibrating branch will be more useful if the role has already landed badly.
症状： 明明是现有岗位运行不畅需要调整，却选了"准备晋升"的场景 后果： 你得到的是针对你已经完成的转型的辅导，而不是你实际遇到的问题的解决方案。 解决方案： 诚实面对你的目标和实际现状的差距，如果岗位已经出现问题，调整校准分支的内容会更有用。

References

参考资料

Related Skills

相关技能

  • skills/executive-onboarding-playbook/SKILL.md
    — The 30-60-90 diagnostic playbook; essential reading for Branch 3 (Newly Landed) and Branch 2 (Evaluating)
  • skills/altitude-horizon-framework/SKILL.md
    — The Director-level mental model; foundational context for understanding where the VP/CPO transition begins
  • skills/director-readiness-advisor/SKILL.md
    — The Director-level transition equivalent; useful if you're coaching a Director report through their own transition
  • skills/workshop-facilitation/SKILL.md
    — Facilitation protocol for this interactive skill
  • skills/executive-onboarding-playbook/SKILL.md
    — 30-60-90天诊断手册，是分支3（新官上任）和分支2（评估）的必读内容
  • skills/altitude-horizon-framework/SKILL.md
    — 总监层级的思维模型，是理解VP/CPO转型起点的基础背景
  • skills/director-readiness-advisor/SKILL.md
    — 对应总监层级转型的指导，如果你要辅导下属总监的转型会很有用
  • skills/workshop-facilitation/SKILL.md
    — 本交互式技能的引导协议

Source Material

来源材料

External Frameworks

外部框架

  • Marty Cagan, Empowered — Organizational dynamics and product leadership at scale
  • Patrick Lencioni, Five Dysfunctions of a Team — Diagnostic for executive team dysfunction
  • Michael Watkins, The First 90 Days — Structured approach to senior leadership transitions
  • Marty Cagan，Empowered — 大规模组织动态和产品领导力相关内容
  • Patrick Lencioni，团队协作的五大障碍 — 高管团队功能失调的诊断工具
  • Michael Watkins，新管理者的90天 — 高层领导者转型的结构化方法