---
name: altitude-horizon-framework
description: Use when diagnosing why a PM-to-Director transition is stalling — or when a newly promoted Director needs to map the two axes that define the role shift (scope and time horizon) and build clarity for their team from incomplete organizational direction.
role: product-manager
intent: |
  Provides a two-axis mental model — Altitude (how wide you zoom out) and
  Horizon (how far forward you look) — to distinguish Director-level thinking
  from PM-level thinking. Use it to identify which of four transition zones is
  the friction point, and to run a Cascading Context Map when team direction is
  murky because strategy above hasn't been translated. The goal is not to stop
  thinking like a PM; it's to add the zoom level the Director role requires.
type: component
theme: career-leadership
best_for:
  - Diagnosing why a newly promoted Director isn't clicking in the role
  - Understanding what substantively changes — and what doesn't — in the PM-to-Director shift
  - Creating team-level clarity when organizational strategy is vague or incomplete
  - Preparing a senior PM for the transition before it happens
scenarios:
  - "I was just promoted to Director and something feels off — I can't tell what I'm supposed to be doing differently"
  - "My team keeps asking what our strategy means for them and I don't have a good answer"
  - "I'm a senior PM and want to understand what the Director role actually demands before I pursue it"
  - "One of my PMs is struggling with a stakeholder relationship and I keep jumping in to fix it — is that a problem?"
estimated_time: "10-20 minutes"
---

# Altitude-Horizon Framework

> v0 draft. Grounded in the career-transition thinking of Todd Blaquiere, Ryan Cantwell, and Joe Ghali (*The Product Porch*, E42, January 2026) and informed by Marty Cagan's organizational role-clarity work (*Empowered*, 2020). Julie Zhuo's IC-to-manager observations (*The Making of a Manager*, 2019) and Michael Watkins' transition structure (*The First 90 Days*, 2003) are used as secondary references. Editorial review recommended before production use.

## Purpose

Produce a clear diagnosis of where a PM-to-Director transition is stalling, using two axes — Altitude (breadth of scope) and Horizon (time span of thinking) — and four named transition zones that each require a distinct behavioral shift.

The framework is not a seniority ranking. A PM who operates at PM altitude is doing the right work. A Director who operates at PM altitude is leaving their actual job undone while accidentally doing someone else's. The goal is role clarity, not prestige signaling.

The primary artifact is a self-assessment across four zones, plus a Cascading Context Map when the team lacks clear direction. Total cycle time is 10-20 minutes for a personal diagnosis; 30-60 minutes if building a full Context Cascade for a team.

## Key Concepts

### The Two Axes (Blaquiere, Cantwell, Ghali)

The PM-to-Director shift is often described as "more strategic" or "higher level," which tells you almost nothing actionable. Blaquiere, Cantwell, and Ghali (*The Product Porch*, E42) give the shift two concrete dimensions:

**Altitude — breadth of scope**

A PM works close to the ground: specific customer problems, individual features, sprint decisions, one team's dynamics. A Director works at portfolio elevation: how products fit together, how cross-functional systems interact, how budget and headcount flow across competing bets, how the product org is perceived in market.

The shift is not a loss of customer empathy. Directors who lose touch with customer signal make worse portfolio calls. The shift is a change in the *unit of analysis*: from "this customer, this feature, this sprint" to "this portfolio, this system, this quarter-to-annual arc."

**Horizon — time span of thinking**

A PM's planning horizon runs days to weeks, with a quarter as the outer edge. A Director's planning horizon starts at a quarter and extends to annual cycles and multi-year market positioning. The Director plans backward from where the product ecosystem needs to be in a year, then works forward to what has to happen now to make that possible.

These two axes interact. A Director who has the right horizon but the wrong altitude (still thinking feature-by-feature but now about many features) is a busy PM, not a Director. A Director who has the right altitude but the wrong horizon (thinking portfolio-wide but only for the next sprint) is an architect without a calendar. Both axes must shift.

### The Operator vs. Waiter Distinction

The sharpest frame for what the role shift actually feels like comes from the restaurant analogy (*The Product Porch*, E42):

| Dimension | PM — Waiter | Director — Operator |
|---|---|---|
| Focus | One diner's experience | Full system: staffing, margins, menu, supply chain |
| Authority | Influence without control | Portfolio decisions, headcount, budget allocation |
| Success signal | Table seven is satisfied | Restaurant is profitable, consistent, and scalable |
| Relationship to users | Direct, daily, intimate | Aggregate patterns, buyer personas, market cohorts |
| Failure mode | Ignoring Table Seven | Obsessing over Table Seven's lemons |

The waiter's expertise is translating individual diners' needs into real-time execution. The operator's expertise is the system: "Are we overspending on ingredients? Is a 75-item menu confusing customers before they even order? Do we have the staffing for Friday night?" Neither expertise is more important in absolute terms. They are appropriate to different roles. A great waiter who becomes an operator must stop reflexively picking up tables and start asking system questions.

### Four Transition Zones

Most Directors who stall are not struggling in all four zones — they're struggling in one or two. Naming the zone is the leverage point. Treating all four simultaneously produces diffuse effort. (*The Product Porch*, E42.)

**Zone 1 — Thinking Altitude**
The PM habit: solve the customer problem in front of you. The Director skill: design systems and teams that solve *classes* of problems repeatedly, without the Director present.

**Zone 2 — Persona Shift**
The PM habit: obsess over user personas, daily touchpoints, individual customer interviews. The Director skill: think in buyer cohorts, market segments, organizational stakeholders, and executive dynamics. Individual user empathy remains valuable as input; it is no longer the primary operating mode.

**Zone 3 — Hero Syndrome Recovery**
The PM habit: be the person who saves the situation and earns the acknowledgment. The Director skill: derive satisfaction from team success, not personal saves. The Director's product is the team — the roadmap is the team's product. Directors who rescue too often build teams that cannot function without being rescued.

**Zone 4 — Direction Creation**
The PM habit: wait for clear direction from above before committing. The Director skill: produce clarity downward even when organizational direction is incomplete or ambiguous. When strategy from above is vague, the Director's job is to translate the available signal into team-level direction — not to wait for perfect clarity before moving.

### The Cascading Context Map

Zone 4 has a named tool. When organizational direction is vague, Directors translate rather than wait. The Cascading Context Map is that translation mechanism (*The Product Porch*, E42):

1. Absorb top-level strategy — QBRs, exec communications, company messaging
2. Extract 3-5 load-bearing priorities, not 20 bullet points
3. Translate: "How does our business unit advance these priorities?"
4. Translate one level down: "How does our product portfolio serve the business unit's translation?"
5. Translate one level further: "What specific accountabilities does each team own to drive that portfolio contribution?"
6. Communicate the cascade: not just *what* but *why it connects upward*

The cascade does not require perfect input. The point is to generate useful direction from available signal and own the translation gap. A Director who waits for complete clarity is practicing PM-era deference in a role that requires direction creation. Cagan (*Empowered*, ch. 3) frames this same obligation as a product leader's accountability to create "product vision" that fills the strategic gap between company goals and team-level work — the Cascading Context Map is the tactical expression of that obligation.

## Application

### Diagnosing a Stalled Transition (15-20 minutes)

Use when a Director is newly promoted and something isn't clicking, or when a senior PM wants to understand where they're weakest before the transition.

**Step 1 — Locate yourself on the two axes (5 minutes)**

Answer these honestly:
- When you encounter a problem, do you instinctively move to solve it yourself, or to frame it for the team to solve? (Altitude signal.)
- When you set priorities, are you thinking in sprints or in annual cycles? (Horizon signal.)

If the answer to both is "more like the PM version," the axes haven't shifted yet. That's normal at 30 days. It's a flag at 90 days.

**Step 2 — Score yourself across the four zones (5-10 minutes)**

For each zone, mark: *natural*, *uncomfortable but progressing*, or *actively regressing*.

- Zone 1 (Altitude): Do I design systems, or do I solve problems?
- Zone 2 (Persona Shift): Do I think in cohorts and stakeholders, or in individual users?
- Zone 3 (Hero Syndrome): Do I coach, or do I rescue?
- Zone 4 (Direction Creation): Do I create clarity from incomplete signal, or do I wait for better direction?

One zone scoring "actively regressing" is your leverage point. Fix that before spreading attention across all four.

**Step 3 — Name the friction (2-3 minutes)**

Write one sentence: "I am stalling in Zone [X] because [specific habit I haven't broken]." Vague diagnosis produces vague prescription.

### Running a Cascading Context Map (30-60 minutes)

Use when your team is uncertain what organizational strategy means for their near-term work.

**Step 1 — Collect available signal (10-15 minutes)**

Pull the last QBR summary, the most recent exec all-hands, any written company strategy. You are not looking for a perfect strategic document; you are looking for 3-5 themes that leadership has signaled, even loosely.

**Step 2 — Draft the four-layer cascade (15-20 minutes)**

Use this template:

```markdown
## Context Cascade — [team / quarter]

**Company priority:** [What leadership said, in their words or close paraphrase]

**Business unit translation:** [How your BU contributes to that priority — what it means for your segment]

**Portfolio translation:** [What each product in your portfolio owns toward the BU translation]

**Team accountabilities:** [What each team specifically owns — named outcomes, not just feature areas]

**Why it connects:** [The so-what — what changes in how the team works, and what stays the same]
```

One page. Comprehensiveness is not the goal; actionable direction is.

**Step 3 — Pressure-test before sharing (5-10 minutes)**

Ask yourself: if a PM reads this and disagrees with a prioritization call, can they trace the logic back to the company priority? If not, the cascade has a gap. Fill the gap before sharing; a broken cascade erodes trust faster than no cascade.

**Step 4 — Share and revisit (5 minutes setup; revisit quarterly)**

Present the cascade to the team — not as handed-down direction, but as "here is how I am translating the available strategy for our work." Invite challenges. Update it at major inflection points: planning cycles, exec changes, pivots, org restructures. A cascade that never updates becomes a stale document the team learns to ignore.

### For Senior PMs Preparing for the Transition (10-15 minutes)

Use this as a readiness lens, not a promotion checklist. Performing Director behaviors while in a PM role can underserve the current scope.

**Step 1 — Observe, don't act (ongoing)**

Identify which transition zone you are weakest in — not to work on it in the current role, but to know what to watch for. The observation builds vocabulary.

**Step 2 — Practice Zone 4 in 1-on-1s**

Ask your manager: "How does my team's work connect to the business strategy I can't see from here?" This is Zone 4 thinking at a safe scope — you're practicing direction-creation cognition without needing the full organizational authority.

**Step 3 — Audit Zone 3 habits now**

Watch for Hero Syndrome precursors: do you step in to solve problems that a 20-minute coaching conversation could have resolved? The habit that makes you an effective PM (responsive, helpful, direct) is the habit that will slow you down as a Director. Catching it now is cheaper than unlearning it post-promotion.

## Examples

### Example 1 — Direction Creation from a Vague Company Priority

**Situation.** The CEO opens the QBR with: "We need to win enterprise this year." Three PMs report to a newly promoted Director. All three ask variants of: "What does enterprise mean for our roadmaps?"

**Wrong response (PM altitude).**
"Let's add enterprise features to our backlogs this sprint."

This response skips the cascade entirely. It treats a vague company priority as a feature request. The result: three teams sprint toward enterprise-flavored work with no shared logic, creating inconsistent signals for sales, support, and marketing.

**Right response (Director altitude).**
The Director runs a Cascading Context Map before the next planning session:

```markdown
## Context Cascade — Q2

**Company priority:** Win larger enterprise deals this year.

**Business unit translation:** Increase average contract value and reduce
time-to-security-approval for enterprise prospects. Deals are stalling at
procurement, not at interest.

**Portfolio translation:**
- Product A: admin controls and role permissions story
- Product B: API documentation and integration reliability story
- Product C: SOC 2 certification and SSO adoption story

**Team accountabilities:**
- Team A owns audit logs and admin controls — target: procurement-grade
- Team B owns SDK quality and integration docs — target: self-serve enterprise evaluation
- Team C owns security certifications and SSO implementation — target: deal-blocker removal

**Why it connects:** Enterprise growth means removing blockers that stall
procurement, not adding enterprise-branded features to every backlog.
Q2 backlog changes: Teams A-C reprioritize to named accountabilities.
Q2 backlog non-changes: Consumer-facing features continue on existing cadence.
```

**Why it works.** The Director did not wait for the CEO to produce a detailed strategic document. They took the available signal ("win enterprise"), translated it through the business unit and portfolio layers, and handed the teams specific ownership. Each PM now has a directional anchor for Q2 planning.

---

### Example 2 — Hero Syndrome Anti-Pattern

**Situation.** A PM on the team escalates a conflict with a sales counterpart who is making roadmap commitments without PM input.

**Wrong response (Hero Syndrome).**
"I'll jump on a call with the sales lead directly — I'll get it sorted out."

This solves the immediate friction and creates a lasting problem. The PM learns that escalating to the Director produces rescue. The Director reinforces the pattern. Next quarter, the same PM escalates a similar conflict — because the Director-as-rescuer is a reliable solution path.

**Right response (Zone 3).**
"Walk me through what you've tried and where it broke down. Let's figure out what you'll do differently in the next conversation — you'll lead it."

Followed by: debrief the PM's framing, align on one clear message and one fallback position, let the PM lead with the Director available if needed, and conduct a brief post-call retrospective on one thing to improve next time.

**Why it matters.** The first response solves the problem at PM altitude while in a Director role. The second response builds the PM's capacity to solve this class of problem without Director involvement. The Director's product is a team that functions — not a team that is well-served.

---

### Example 3 — Altitude Self-Audit (Quick Check)

Before any significant decision, run this four-question audit:

1. Am I deciding at backlog altitude or portfolio altitude?
2. Who should own this decision given my role?
3. If I step in, am I building system clarity or rescuing execution?
4. What context translation is missing for the team right now?

If most answers point to rescue and backlog, you are operating at PM altitude in a Director role. Name it, redirect, and move up the stack.

## Common Pitfalls

### Pitfall 1 — Altitude Theater

**Symptom.** The Director uses portfolio language — "ecosystem," "long-term positioning," "capability investment" — but continues making sprint-level decisions and owning individual deliverables.

**Consequence.** The team receives contradictory signals about who is deciding and at what scope. PMs do not know when to escalate and when to own. Trust in the Director's decision-making clarity erodes because the stated altitude doesn't match the actual altitude.

**Fix.** The rule is binary: either you are in the details and you own it explicitly, or you have delegated it and you are fully out. Mixing altitude without signaling is the problem. When you catch yourself in the details, either own the decision cleanly or hand it back with a coaching frame and stay out.

---

### Pitfall 2 — One-Time Context Cascade

**Symptom.** The Director runs the Cascading Context Map once — typically at annual or Q1 planning — and treats it as permanent.

**Consequence.** Team direction and actual organizational priorities diverge as the year progresses. By Q3, teams are executing work that was coherent in January but no longer reflects executive direction. The mismatch surfaces as a planning-cycle surprise rather than a manageable mid-course adjustment.

**Fix.** Treat the cascade as a living document with defined refresh triggers: quarterly planning, significant leadership changes, pivots, org restructures, and any moment when team members start asking "why are we working on this?" with genuine uncertainty. A cascade that hasn't been updated in two quarters should be treated as suspect.

---

### Pitfall 3 — Hero Syndrome Relapse Under Pressure

**Symptom.** In normal conditions the Director coaches well. Under deadline pressure, a difficult stakeholder, or a high-visibility incident, the Director reverts to direct problem-solving — jumping into accounts, writing specs, joining sales calls to rescue deals.

**Consequence.** The regression communicates that the Director's stated approach (coaching, delegation) is conditional. The team learns to create urgency signals to unlock Director involvement, which reinforces the dependency the Director was trying to break.

**Fix.** Identify personal Hero Syndrome triggers before they occur: "I tend to regress when [deadline / VIP account / executive visibility]." Name those triggers to your manager or a trusted peer. When a trigger fires, pause before acting and ask: "Is this mine to solve, or mine to enable?" Even a 60-second pause breaks the reflex.

---

### Pitfall 4 — Kindness Mistaken for Leadership

**Symptom.** The Director avoids giving direct critical feedback, softens hard decisions until the message is lost, and shields the team from difficult organizational realities to preserve morale.

**Consequence.** Zhuo (*The Making of a Manager*, 2019) identifies this as one of the most reliable early-manager failure modes: the skills that made you a great peer — listening, empathy, responsiveness — become liabilities at organizational scale when they prevent the clarity people actually need. Teams operating without honest feedback and real organizational context cannot make good decisions. Trust erodes when reality arrives unannounced.

**Fix.** Separate transparency from kindness. Being clear about why a decision is hard, what constraints you're holding, and what the honest assessment of performance is — that is kindness at the right scope. Softening the message until it is no longer actionable is not kindness; it is discomfort avoidance with team-level consequences.

---

### Pitfall 5 — Premature Director Thinking in a PM Role

**Symptom.** A senior PM spends significant attention on portfolio dynamics, organizational strategy, and Director-level concerns while still in a PM role.

**Consequence.** The PM underserves the current scope. PM work demands close customer contact, sharp feature-level diagnosis, and sprint-horizon responsiveness. A PM thinking at Director altitude too early misses the customer signal their role requires and produces weaker output in the job they actually have.

**Fix.** Practice director-mode *observation*, not director-mode *operation*, while in the PM role. Use 1-on-1s with your manager to understand the organizational context you can't see from your current scope — that is useful preparation. Running portfolio-level strategy as a PM is not useful preparation; it is scope drift.

---

### Pitfall 6 — Treating the Framework as a Promotion Checklist

**Symptom.** A senior PM uses the four transition zones as a checklist to demonstrate Director-readiness: "I've read the leadership books, I've worked on my coaching style, I understand the cascade — I'm ready."

**Consequence.** Director readiness is built from lived experience with organizational ambiguity, not from vocabulary acquisition. Watkins (*The First 90 Days*, 2003) documents consistently that leaders who arrive in new roles having studied the theory but not having accumulated the relevant judgment under pressure tend to move too fast, misread organizational dynamics, and overcorrect when early signals are negative. The study can be done; the war stories cannot be shortcut.

**Fix.** Use the framework to identify what to seek out in the current role, not to declare readiness. Pursue Zone 3 and Zone 4 experiences — coaching through a difficult cross-functional conflict, creating direction when strategy is incomplete — within your current scope. The experience is the qualification; the vocabulary describes it after the fact.

## References

- **Todd Blaquiere, Ryan Cantwell, Joe Ghali** — *The Product Porch*, Episode 42: "From Product Manager to Director: How to Make the Shift (Part 1)" (January 2026, Simplecast). Primary source for the two axes (Altitude / Horizon), the four transition zones, the Cascading Context Map, and the waiter-to-operator analogy. All structural frameworks in this skill are grounded in this episode.
- **Marty Cagan** — *Empowered: Ordinary People, Extraordinary Products* (2020, Wiley). Chapter 3 addresses the product leader's accountability to create vision and direction when organizational strategy is incomplete — the theoretical grounding for the Zone 4 direction-creation obligation. The organizational role-clarity framing throughout the skill draws on Cagan's distinction between PM-level and leadership-level work.
- **Julie Zhuo** — *The Making of a Manager: What to Do When Everyone Looks to You* (2019, Portfolio/Penguin). Pitfall 4 (kindness mistaken for leadership) and the broader Hero Syndrome recovery pattern draw on Zhuo's documented observations of the IC-to-manager transition, particularly her account of how collaborative strengths become liabilities at scale.
- **Michael Watkins** — *The First 90 Days: Proven Strategies for Getting Up to Speed Faster and Smarter* (2003, Harvard Business Review Press). Used in Pitfall 6: Watkins' research on leader transitions documents the gap between theoretical readiness and operational judgment — the basis for cautioning against treating this framework as a promotion checklist rather than an experience map.
- **Related Hornero skills:**
  - [`strategy-kernel`](../strategy-kernel/SKILL.md) — the Director's Zone 4 work (direction creation) produces or consumes a strategy kernel. A well-run Cascading Context Map translates the kernel's guiding policy into team-level accountability. If the organization has no kernel, the cascade is the Director's substitute until one exists.
  - [`okrs`](../okrs/SKILL.md) — OKR outcomes are the quarterly expression of the cascade's team accountabilities. A cascade without OKRs is direction without measurable commitment; OKRs without a cascade are targets without organizational lineage.
  - [`cross-functional-orchestration`](../cross-functional-orchestration/SKILL.md) — Directors in Zone 2 (persona shift) frequently encounter cross-functional dynamics that require explicit orchestration. This skill handles those structured decision-making moments; the altitude-horizon framework provides the role clarity that tells the Director when to orchestrate versus when to delegate.
  - [`jobs-to-be-done`](../jobs-to-be-done/SKILL.md) — Zone 2 persona shift (from individual user empathy to buyer cohorts and market segments) is informed by JTBD framing. Understanding the jobs customers hire the product to do at cohort level — rather than individual interview level — is the Director altitude expression of JTBD thinking.

*Synthesis cue: adapted from Dean Peters' [Product-Manager-Skills](https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/altitude-horizon-framework) (CC BY-NC-SA 4.0). Hornero's re-synthesis is MIT.*