Altitude & Horizon Framework (PM → Director)
Understand the PM-to-Director transition through altitude (scope) and horizon (time). Diagnose which of four transition zones is creating friction and apply the Cascading Context Map when direction from above is vague.
You got promoted to Director and something isn't clicking. You're still solving individual customer problems, still obsessing over user stories, still waiting for clarity from leadership that never comes. The skills that made you a great PM are now liabilities — and nobody told you which ones.
Who it's for: senior PMs preparing for Director roles, newly promoted Directors diagnosing transition friction, CPOs coaching their leadership bench, product leaders whose teams feel directionless, anyone trying to translate vague company strategy into team clarity
Example
"My team has no clear direction and company strategy feels vague — help me fix it" → Cascading Context Map translating top-level priorities → business unit → product portfolio → team accountabilities, with a one-page team-facing summary that says what changes, what stays the same, and why
New here? 3-minute setup guide → | Already set up? Copy the template below.
# Altitude & Horizon Framework
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 PM→Director transition, diagnose which transition zone is creating friction, and apply the Cascading Context Map when organizational direction is vague.
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.
## 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.
**Horizon — Time**
- **PM horizon:** Days, weeks, sprints. A quarter at most.
- **Director horizon:** Quarter as the starting point. Annual planning, multi-year strategy, market shifts.
## The Waiter vs. Restaurant Operator
| Dimension | PM (Waiter) | Director (Restaurant Operator) |
|---|---|---|
| Focus | Individual diner experience | Entire system — staffing, margins, menu, suppliers |
| Authority | Influence without control | Portfolio decisions, budget, resource allocation |
| Success metric | Table seven is happy | Restaurant is profitable, consistent, scalable |
| Relationship to customers | Direct, daily, intimate | Aggregate patterns, buyer personas, cohorts |
| Failure mode | Ignoring Table Seven's needs | Obsessing over Table Seven's lemons |
## Four Transition Zones
1. **Thinking Altitude** — Stop solving individual problems; start designing systems that solve classes of problems
2. **Persona Shift** — Stop obsessing over user personas; start thinking in buyer personas, market cohorts, executive dynamics
3. **Hero Syndrome Recovery** — Stop saving the day; get satisfaction from team success
4. **Direction Creation** — Stop waiting for direction from above; create context cascades
## Named Failure Modes
- **Hero Syndrome** — Jumping in to solve problems directly; regressing to old IC reward loops
- **Allergic to Process** — Resisting shared structures; creating coordination chaos
- **People-Pleaser Leadership** — Avoiding hard feedback; confusing popular with effective
- **Instant Gratification Trap** — Reading leadership books to shortcut war-story experience
- **Black-and-White Thinking** — Expecting clean cause-and-effect in grayscale terrain
## The Cascading Context Map
When organizational direction is vague or absent, Directors don't wait — they cascade:
1. Listen to top-level strategy (QBRs, exec communications)
2. Extract 3-5 key priorities leadership stated
3. Map second layer: how does our business unit accomplish these?
4. Map third layer: how does our product portfolio accomplish that?
5. Map fourth layer: what are my team's specific accountabilities?
6. Communicate the cascade to the team — not just what, but why it connects upward
**Template:**
```markdown
## 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. Clarity, not comprehensiveness.
## Application
### As a PM (Pre-Transition)
- Identify your weakest transition zone (to observe, not act)
- Use 1-on-1s to practice Zone 4: ask about strategic context
- Watch for Hero Syndrome now
- Don't over-invest in Director thinking while still PM
### As a Newly Promoted Director
- **First 30 days:** Map new Altitude & Horizon. New stakeholders. New planning horizon.
- **First 60 days:** Identify Hero Syndrome triggers
- **First 90 days:** Run first Cascading Context Map
- **Ongoing:** Name which transition zone friction lives in. Diagnosis before prescription.
## Common Pitfalls
1. **Altitude Theater** — Using strategy language while making sprint decisions
2. **One-and-Done Context Cascade** — Running it once at annual planning, then never revisiting
3. **Confusing Kindness with Leadership** — Shielding team from hard truths erodes trust when reality lands
4. **Premature Director Thinking as a PM** — Under-serving current role while rehearsing future one
Get new playbooks like this one
One email a week with new Claude Code workflows. Free, like everything here.
No spam. Unsubscribe anytime.
What This Does
Defines the two-axis mental model that distinguishes Director thinking from PM thinking: Altitude (scope) and Horizon (time). Helps you diagnose which of four transition zones is creating friction in your current role, and apply the Cascading Context Map to translate vague company strategy into team clarity.
Not a seniority hierarchy. A PM operating at the right altitude is doing excellent work. A Director operating at PM altitude is leaving their actual job undone.
Quick Start
mkdir -p ~/Documents/AltitudeHorizon
mv ~/Downloads/CLAUDE.md ~/Documents/AltitudeHorizon/
cd ~/Documents/AltitudeHorizon
claude
Then describe your role, current scope, and friction. Claude will diagnose which transition zone is blocking you and walk you through a Cascading Context Map if your team is unclear on strategy.
Four Transition Zones
- Thinking Altitude — From solving individual problems to designing systems that solve classes of problems
- Persona Shift — From user personas to buyer personas, market cohorts, and executive dynamics
- Hero Syndrome Recovery — From saving the day to growing others
- Direction Creation — From waiting for clarity to creating context cascades
Five Named Failure Modes
- Hero Syndrome — regressing to old IC reward loops
- Allergic to Process — protecting star-PM exceptions, creating coordination chaos
- People-Pleaser Leadership — confusing popular with effective
- Instant Gratification Trap — reading leadership books to shortcut war-story experience
- Black-and-White Thinking — expecting clean cause-and-effect in grayscale terrain
The Cascading Context Map
Six steps to translate vague company strategy into team clarity:
- Listen to top-level strategy (QBRs, exec communications)
- Extract 3-5 key priorities
- Map how your business unit contributes
- Map how your product portfolio contributes
- Map specific team accountabilities
- Communicate the cascade — what, plus why it connects upward
One page is better than ten. Revisit quarterly, not annually.
Tips & Best Practices
- Diagnosis before prescription. When friction appears, name which zone it lives in first.
- Don't over-invest in Director thinking while still a PM — serve your current scope with full commitment.
- Revisit the cascade at inflection points — quarterly planning, exec changes, pivots, re-orgs.
- Be transparent about the "why" behind hard decisions. You don't need to share everything, but what you share should be honest and actionable.