Back to Details

altitude-horizon-framework

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Purpose

核心目标

Defines the two-axis mental model that distinguishes Director-level thinking from PM thinking: Altitude (how wide you zoom out) and Horizon (how far ahead you look). Use this to understand what actually changes in the transition, diagnose which transition zone is creating friction, and apply the Cascading Context Map when organizational direction is vague or absent.
This is not a seniority hierarchy. A PM operating at the right altitude for their role is doing excellent work. A Director operating at PM altitude is leaving their actual job undone.
本文定义了区分总监级思维和产品经理思维的双轴思维模型：高度（Altitude）（你能拉远到多大的全局视角）和视野（Horizon）（你能看多远的未来规划）。你可以用这个模型理解转型过程中究竟发生了哪些变化，定位造成阻碍的转型区间，在组织方向模糊或缺失时使用级联上下文地图对齐团队。
这不是一套论资排辈的等级标准：处于自身岗位对应高度开展工作的 PM 已经非常优秀，而停留在 PM 高度的 Director 则没有完成本职工作。

Key Concepts

核心概念

The Two Axes

双轴维度

Altitude — Scope
  • PM altitude: Close to the ground. Customer problems, individual features, sprint priorities, specific team dynamics.
  • Director altitude: High-level view. Product portfolio, cross-functional systems, organizational dynamics, budget allocation, market positioning.
  • The shift is not about losing empathy for customers — it's about zooming out to see the entire restaurant, not just one table.
Horizon — Time
  • PM horizon: Days, weeks, sprints. A quarter at most.
  • Director horizon: Quarter as the starting point. Annual planning cycles, multi-year strategy, market shifts.
  • Directors plan for where the product ecosystem needs to be in a year, then work backward.
高度 — 业务范围
  • PM 高度： 贴近一线，关注客户问题、单个功能特性、冲刺优先级、具体团队动态
  • Director 高度： 全局视角，关注产品组合、跨职能体系、组织动态、预算分配、市场定位
  • 这种转变不是要失去对客户的同理心，而是要拉远视角看到整家餐厅的运营，而不只是单桌的情况
视野 — 时间跨度
  • PM 视野： 按天、周、冲刺规划，最多覆盖一个季度
  • Director 视野： 以季度为起点，覆盖年度规划周期、多年度战略、市场变迁
  • 总监需要先规划产品生态一年后需要达到的目标，再倒推落地路径

The Waiter vs. Restaurant Operator

服务员 vs 餐厅运营者

The sharpest analogy for the role shift:
DimensionPM (Waiter)Director (Restaurant Operator)
FocusIndividual diner experienceEntire system — staffing, margins, menu, suppliers
AuthorityInfluence without controlPortfolio decisions, budget, resource allocation
Success metricTable seven is happyRestaurant is profitable, consistent, and scalable
Relationship to customersDirect, daily, intimateAggregate patterns, buyer personas, market cohorts
Failure modeIgnoring Table Seven's needsObsessing over Table Seven's lemons
The waiter excels at translating the experience of individual diners. The operator isn't ignoring diners — they're asking different questions: "Are we overspending on ingredients? Is a 75-page menu confusing customers? Do we need another server for the dinner rush?" Neither question is more important in absolute terms. They're appropriate to different roles.
这个角色转变最贴切的类比：
维度PM（服务员）Director（餐厅运营者）
关注重点单个食客的体验整套体系 — 人员配置、利润、菜单、供应商
权限无控制权的影响力产品组合决策、预算、资源分配权
成功指标7号桌的客人满意餐厅盈利、服务稳定、可规模化扩张
和客户的关系直接、日常、深入的接触整体用户 patterns、购买者画像、市场分群
失败模式忽视7号桌的需求纠结于7号桌要的柠檬这类细枝末节
服务员的长处是精准传递单个食客的体验，运营者并非不重视食客，而是要思考不同的问题：「我们的食材是不是超支了？75页的菜单会不会让顾客困惑？晚餐高峰要不要再加一名服务员？」两类问题没有绝对的高下之分，只是适配不同的角色定位。

Four Transition Zones

四个转型区间

The PM → Director shift requires movement across four zones. Most people struggle with one or two more than the others — diagnosing which one is the leverage point.
Zone 1 — Thinking Altitude
  • Stop: Solving individual customer problems directly
  • Start: Designing systems and teams that solve classes of problems
Zone 2 — Persona Shift
  • Stop: Obsessing over individual user personas and daily customer touchpoints
  • Start: Thinking in buyer personas, market cohorts, organizational stakeholders, and executive dynamics
Zone 3 — Hero Syndrome Recovery
  • Stop: Being the person who saves the day and earns the pat on the back
  • Start: Getting satisfaction from team success — your product is your people, not the roadmap
Zone 4 — Direction Creation
  • Stop: Waiting for clear direction from above before moving
  • Start: Creating context cascades that translate company strategy into team clarity, even when inputs are incomplete
从 PM 到 Director 的转型需要跨越四个区间，大部分人都会在其中1-2个区间遇到困难，找到核心阻碍区间就是破局的关键。
区间1 — 思维高度转变
  • 停止：直接解决单个客户的问题
  • 开始：设计能解决一类问题的体系和团队
区间2 — 关注对象转变
  • 停止：纠结于单个用户画像和日常客户触点
  • 开始：关注购买者画像、市场分群、组织利益相关方、高管层动态
区间3 — 摆脱英雄综合征
  • 停止：做那个冲出来解决问题、赢得表扬的救火队员
  • 开始：从团队的成功中获得成就感 — 你的产品就是你的团队，而不是 roadmap
区间4 — 主动创造方向
  • 停止：等上层给出明确方向再行动
  • 开始：搭建上下文传导链路，哪怕输入信息不完整，也能把公司战略转化为团队的清晰目标

Named Failure Modes

典型失败模式

Hero Syndrome What it looks like: Jumping in to solve problems directly. Staying close to the tactical work. Wanting visibility on individual wins. Why it happens: PMs are trained to be helpful and responsive. Directors get fewer pats on the back, so they regress to the old reward loop. The cost: You under-perform as a Director while over-functioning as a senior IC. Your team doesn't develop because you're in their way.
Allergic to Process What it looks like: Resisting shared structures. Letting high-performing PMs run their own playbooks independently. Why it happens: PMs naturally resist bureaucracy. Early director permissiveness can feel like "great leadership" and "trusting the team." The cost: Stakeholders across marketing, finance, and leadership can't synthesize inconsistent outputs. Without shared processes, teams become "monkeys in the room breaking glass."
People-Pleaser Leadership What it looks like: Wanting the team to like you. Avoiding hard feedback. Saying yes to stakeholder requests to preserve relationships. Why it happens: The skills that made you a great PM — listening, empathy, responsiveness — become liabilities at organizational scale. The cost: You confuse "popular" with "effective." Respect is built through clarity and hard calls, not niceness.
Instant Gratification Trap What it looks like: Reading leadership books, collecting certifications, asking "what do I need to do to get promoted?" Why it happens: PMs are good at optimization. They try to shortcut the experience requirement. The cost: Director readiness requires war stories and lived humility. You can study your way to fluency in the vocabulary, but not to readiness for the role.
Black-and-White Thinking What it looks like: "This seems like an obvious decision." "Why can't we fund both?" "Why is everything so political here?" Why it happens: PMs operate in cleaner problem spaces with clearer cause-and-effect. Director decisions involve competing constraints, limited information, and organizational dynamics. The cost: Fast decisions with low confidence create downstream chaos. The grayscale is not a failure of leadership — it's the actual terrain.
英雄综合征 表现：直接跳进去解决问题，停留在战术层面工作，想要在单个成果上刷存在感 原因：PM 过往被训练要乐于助人和快速响应，而总监获得的公开表扬更少，所以会退回到熟悉的奖励循环里 代价：你作为总监的表现不达标，同时还越权做了高级个人贡献者的工作，你挡了团队的路，他们也得不到成长
流程过敏症 表现：抵触公共规则，允许高绩效PM按自己的方式独立运作 原因：PM 天生抵触官僚主义，刚上任的总监往往会把宽松管理当成「优秀领导力」和「信任团队」的表现 代价：市场、财务、管理层等跨部门 stakeholder 没法对齐不一致的产出，没有统一流程，团队就会变成「房间里乱砸玻璃的猴子」，带来额外的协同成本
讨好型领导力 表现：想要团队都喜欢你，回避给出尖锐反馈，为了维护关系对 stakeholder 的请求来者不拒 原因：让你成为优秀PM的技能 — 倾听、同理心、响应快 — 在组织规模变大后就变成了劣势 代价：你把「受欢迎」和「有能力」搞混了，尊重来自清晰的决策和敢啃硬骨头，而不是和稀泥的好人态度
即时满足陷阱 表现：读各种领导力书籍、考一堆证书，总问「我要做什么才能晋升？」 原因：PM 擅长做优化，总想走捷径跳过经验积累的要求 代价：要达到总监的胜任要求需要足够的实战经历和打磨出来的谦卑心态，你可以靠学习把理论术语说的很溜，但没法靠看书获得胜任岗位的能力
非黑即白思维 表现：「这个决策看起来很明显啊」「为什么我们不能两个都投？」「为什么这里的一切都这么政治化？」 原因：PM 工作的问题空间更纯粹，因果关系更清晰，而总监的决策要平衡互相冲突的约束、有限的信息和复杂的组织动态 代价：低质量的快速决策会带来后续的混乱，灰度不是领导力的失效，而是真实的工作常态

The Cascading Context Map

级联上下文地图

When organizational direction is vague or absent, Directors don't wait — they cascade.
The six steps:
  1. Listen to the top-level strategy — QBRs, company messaging, executive communications
  2. Extract key priorities leadership stated — Identify 3–5 themes, not 20 bullet points
  3. Map the second layer: "How does our business unit accomplish these objectives?"
  4. Map the third layer: "How does our product portfolio accomplish that?"
  5. Map the fourth layer: "What are my team's specific accountabilities that drive success at layer three?"
  6. Communicate the cascade to the team — Not just what to do, but why it connects upward
What this fixes: Teams "wandering in the wilderness" — shipping work that doesn't connect to strategy because the context was never translated for them.
The core principle: Even with incomplete direction from above, a Director's job is to fill the gap downward. Waiting for perfect clarity is a PM habit. Creating imperfect-but-useful clarity is a Director skill.
当组织方向模糊或者缺失的时候，总监不会等，而是会主动向下传导上下文。
六个步骤：
  1. 聆听上层战略 — 从QBR、公司公开信息、高管沟通内容中提取信息
  2. 提取领导层明确的核心优先级 — 找3-5个核心主题，而不是20条零散的要点
  3. 映射第二层：「我们业务单元要怎么达成这些目标？」
  4. 映射第三层：「我们的产品组合要怎么支撑这个目标？」
  5. 映射第四层：「我的团队要承担哪些具体职责，才能推动第三层目标的成功？」
  6. 把级联关系同步给团队 — 不仅要说要做什么，还要说清楚和上层目标的关联逻辑
解决的问题： 避免团队「在荒野里瞎逛」 — 因为上下文从来没有向下传导，做出来的成果和战略完全不挂钩
核心原则： 哪怕上层给的方向不完整，总监的工作就是向下补全信息差，等完美的清晰方向是PM的习惯，创造不完美但有用的清晰方向是总监的能力

Application

应用方法

Using This Framework as a PM (Pre-Transition)

作为还没转型的PM怎么用这套框架

  1. Identify which transition zone you're weakest in — not to act on it yet, but to know what to observe
  2. Use 1-on-1s with your manager to practice Zone 4: "How does my work connect to business strategy? What's the organizational context I'm not seeing?"
  3. Watch for Hero Syndrome habits now: do you jump in to solve things that others could solve with your coaching?
  4. Don't over-invest in Director thinking while you're still in a PM role. Serve your current scope with full commitment — director altitude will be available when the context requires it
  1. 识别你在哪个转型区间最薄弱 — 不用现在就强行改变，先知道要观察什么
  2. 和上级的1对1沟通里练习第四区间的思维：「我的工作怎么和公司战略挂钩？有哪些我没看到的组织上下文？」
  3. 现在就留意自己有没有英雄综合征的习惯：你是不是总会跳进去解决那些你指导一下别人就能搞定的问题？
  4. 你还在PM岗位的时候不要过度投入到总监思维里，全身心做好当前权责范围内的事 — 当环境需要的时候，总监级的视角自然会到来

Using This Framework as a Newly Promoted Director

作为刚晋升的总监怎么用这套框架

  1. First 30 days: Draw your new Altitude & Horizon map. Who are your new stakeholders? What does a quarter-to-annual planning horizon actually look like in this organization?
  2. First 60 days: Identify your Hero Syndrome triggers. When do you feel the pull to jump in directly instead of coaching?
  3. First 90 days: Run your first Cascading Context Map. Even if company strategy is unclear, make your best translation and share it with your team
  4. Ongoing: When friction appears, name which transition zone it lives in. Diagnosis before prescription
  1. 头30天： 画出你新的高度和视野地图，你的新 stakeholder 有哪些？在这个组织里，季度到年度的规划周期实际是什么样的？
  2. 头60天： 找到触发你英雄综合征的场景，什么时候你会忍不住直接跳进去解决问题，而不是做辅导？
  3. 头90天： 运行你的第一次级联上下文地图，哪怕公司战略不清晰，也尽你所能做转译，同步给你的团队
  4. 日常： 出现摩擦的时候，先定位属于哪个转型区间的问题，先诊断再开药方

Running a Cascading Context Map

运行级联上下文地图的方法

Use when your team is unclear on what organizational strategy means for their work.
markdown
undefined
当你的团队不清楚组织战略对他们的工作意味着什么的时候就可以用。
markdown
undefined

Context Cascade

Context Cascade

Company Priority: [What leadership said — in their words] Business Unit Translation: [How your BU contributes to that priority] Product Portfolio Translation: [How your products contribute to that] Team Accountabilities: [What each team owns specifically] Why this matters: [The so-what for your team — what changes, what stays the same]

One page is better than ten. The goal is clarity, not comprehensiveness.

---
Company Priority: [What leadership said — in their words] Business Unit Translation: [How your BU contributes to that priority] Product Portfolio Translation: [How your products contribute to that] Team Accountabilities: [What each team owns specifically] Why this matters: [The so-what for your team — what changes, what stays the same]

一页纸就比十页好，目标是清晰，不是大而全。

---

Examples

示例

See 
examples/sample.md
for a full worked scenario with a completed Cascading Context Map and anti-pattern contrast.
查看 
examples/sample.md
获得完整的实操场景，包含填好的级联上下文地图和反模式对比。

Good: Director Creates Clarity from a Vague Company Priority

正面示例：总监从模糊的公司优先级里创造清晰方向

Situation: CEO announces at QBR: "We're doubling down on enterprise." Three PMs ask their Director: "What does that mean for our roadmaps?"
PM response (wrong altitude): "Let's add enterprise features to our sprint backlogs."
Director response (right altitude): Runs a Cascading Context Map. Translates: "Enterprise means larger deal sizes, longer sales cycles, and more integration requirements. For our portfolio: Product A owns the admin controls story, Product B owns the API documentation story, Product C owns the security certification story. Here's what changes in Q3 planning and what doesn't."
Why it works: Director didn't wait for more clarity. They created it from available signal.
场景： CEO在QBR上宣布「我们要加倍投入企业服务」，三个PM问他们的总监：「这对我们的roadmap意味着什么？」
PM的回答（高度错误）：「我们把企业级功能加到冲刺待办列表里吧」
总监的回答（高度正确）： 运行级联上下文地图，转译后给出答案：「企业服务意味着更大的订单金额、更长的销售周期、更多的集成需求。对我们的产品组合来说：产品A负责管控能力的搭建，产品B负责API文档的建设，产品C负责安全认证的相关工作。下面是Q3规划里要变的和不变的内容。」
为什么有效： 总监没有等更多的信息，而是从现有信号里创造了清晰的方向

Bad: Hero Syndrome in Action

负面示例：英雄综合征的实际表现

Situation: A PM on the team is struggling with a difficult stakeholder relationship.
Director response (wrong): "Let me just talk to that stakeholder directly — I'll get it sorted out."
Director response (right): "Walk me through what you've tried. Let's figure out where it broke down and what you'll do differently."
Why it matters: The first response solves the problem and creates dependency. The second response grows the PM. Directors who rescue too often build teams that can't function without them.
场景： 团队里的一个PM在处理一段难搞的stakeholder关系上遇到了困难
总监的错误回答：「我直接去和那个 stakeholder 聊吧，我能搞定」
总监的正确回答：「和我说说你都试过什么方法，我们一起找找哪里出了问题，以及你接下来可以怎么调整」
为什么重要： 第一种回答解决了当下的问题，但制造了依赖，第二种回答帮PM获得了成长，总去救火的总监带出来的团队离开他就转不动

Good: Shifting from Waiter to Operator

正面示例：从服务员到运营者的转变

Situation: A high-performing PM insists on documenting requirements in a different format from the rest of the team because "my stakeholders prefer it."
Director response (wrong): "That's fine, she's our best PM — if it works for her team, let it go."
Director response (right): "Joe is crushing it individually. But when marketing tries to synthesize across all three PMs' work, they can't. Shared process isn't bureaucracy — it's what makes the system legible to everyone outside it."
Why it matters: Protecting high-performer exceptions creates invisible coordination costs. The Restaurant Operator's job is the system, not the star waiter.
场景： 一个高绩效PM坚持用和团队其他人不一样的格式写需求文档，理由是「我的 stakeholder 更喜欢这个格式」
总监的错误回答：「没问题，她是我们最好的PM，只要对她的团队有用就随她去」
总监的正确回答：「Joe 个人表现确实很棒，但市场部要对齐三个PM的工作的时候，他们根本没法处理不同格式的内容。统一流程不是官僚主义，是让体系外的所有人都能看懂我们工作的基础」
为什么重要： 给高绩效者开例外会制造看不见的协同成本，餐厅运营者的工作是维护整个体系，而不是照顾明星服务员

Common Pitfalls

常见陷阱

Pitfall 1: Altitude Theater

陷阱1：高度表演

Symptom: Using strategy language ("portfolio," "ecosystem," "long-term vision") while still making sprint-level decisions
Consequence: You sound like a Director but function like a PM. Your team is confused about who's actually deciding and at what level.
Fix: If you're in the details, own it. If you're not, delegate it fully. Mixing altitude levels without signaling creates ambiguity that erodes team trust.
症状： 满嘴都是战略术语（「产品组合」「生态」「长期愿景」），但实际还在做冲刺级的决策 后果： 你听起来像个总监，但实际干的是PM的活，你的团队会搞不清到底谁在什么层级做决策 解决方法： 如果你要管细节就明说，如果你不管就完全放权，不打招呼就切换高度会制造模糊性，侵蚀团队信任

Pitfall 2: One-and-Done Context Cascade

陷阱2：一次性上下文传导

Symptom: Running the Cascading Context Map once at annual planning, then never revisiting it
Consequence: Team aligns in Q1 and drifts as strategy evolves. By Q3, team work is decoupled from current priorities.
Fix: Revisit the cascade at major inflection points — quarterly planning, significant exec changes, pivots, or org restructuring.
症状： 年度规划的时候做了一次级联上下文地图，之后就再也不更新了 后果： 团队Q1还是对齐的，随着战略演变就慢慢跑偏了，到Q3的时候团队工作已经和当前优先级完全脱钩 解决方法： 在关键节点重新复盘传导链路 — 季度规划、重大高管变动、战略转向、组织架构调整的时候都要更新

Pitfall 3: Confusing Kindness with Leadership

陷阱3：把友善和领导力搞混

Symptom: Shielding the team from hard decisions, over-explaining constraints you're holding, softening feedback into meaninglessness
Consequence: Team operates without accurate context; trust erodes when reality eventually lands without warning.
Fix: Be transparent about the "why" behind hard decisions. You don't need to share everything — but what you share should be honest and actionable.
症状： 帮团队挡掉所有难的决策，过度解释你面临的约束，把反馈软化到毫无意义的程度 后果： 团队在没有准确上下文的环境里工作，等现实毫无预警砸下来的时候，信任就会崩塌 解决方法： 对艰难决策背后的「原因」保持透明，你不用什么都分享，但你分享的内容必须是诚实且可落地的

Pitfall 4: Premature Director Thinking as a PM

陷阱4：作为PM过早启用总监思维

Symptom: Spending PM years worried about portfolio strategy, organizational dynamics, and "thinking above your pay grade"
Consequence: You under-serve your current role. PMs who think like Directors often miss the customer-level signal their actual role requires.
Fix: Play your current role with full commitment. The transition will demand Director thinking soon enough — you'll be ready because you did your PM work well, not because you rehearsed the Director role prematurely.
症状： 还在做PM的时候就天天操心产品组合战略、组织动态，总「思考超过你薪资等级的问题」 后果： 你没法做好当前的工作，像总监一样思考的PM往往会错过他们岗位要求的客户层面的信号 解决方法： 全身心投入当前的角色，转型很快就会需要你用总监的思维 — 你能做好准备是因为你PM的工作做的足够好，而不是因为你提前排练了总监的角色

References

参考资料

Related Skills

相关技能

  • skills/director-readiness-advisor/SKILL.md
    — Interactive advisor that uses this framework to diagnose and coach your specific transition situation
  • skills/director-readiness-advisor/SKILL.md
    — 交互式咨询工具，用这套框架诊断和指导你具体的转型场景

Source Material

来源材料

External Frameworks

外部框架

  • Marty Cagan, Empowered — Organizational dynamics and role clarity in product leadership
  • Julie Zhuo, The Making of a Manager — IC-to-manager transition with practical war stories
  • Michael Watkins, The First 90 Days — Structured approach to leadership transitions
  • Marty Cagan, 《Empowered》（赋能） — 产品领导力相关的组织动态和角色清晰度内容
  • Julie Zhuo, 《The Making of a Manager》（成为管理者） — 从个人贡献者到管理者转型的实战经验
  • Michael Watkins, 《The First 90 Days》（新管理者的第一个90天） — 领导力转型的结构化方法