JavaScript is disabled. Some features may not work.
altitude-horizon-framework — ★ 5.3K GitHub Stars — Install Guide | SkillsNav
🇺🇸 English🇨🇳 中文
SkillsNav
Home

altitude-horizon-framework

★ 5.3K repogenerationN/AIntermediateClaude
🤖 AI Summary

This skill defines a two-axis mental model (Altitude for scope, Horizon for time) to diagnose role friction between PM and Director thinking, and provides a Cascading Context Map to create direction when organizational strategy is vague or absent.

How to Install

Claude Code:
git clone --depth 1 https://github.com/deanpeters/Product-Manager-Skills.git && cp Product-Manager-Skills/skills/altitude-horizon-framework ~/.claude/skills/altitude-horizon-framework -r
## 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. ## 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. --- ### The Waiter vs. Restaurant Operator The sharpest analogy for the role shift: | 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, and scalable | | Relationship to customers | Direct, daily, intimate | Aggregate patterns, buyer personas, market cohorts | | Failure mode | Ignoring Table Seven's needs | Obsessing 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. --- ### 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 - Sta

Details

Category Coding → generation
Sourcedeanpeters/Product-Manager-Skills
SKILL.mdView on GitHub →
Repo Stars★ 5.3K
Est. per SkillN/A (shared across 54 skills from this repo)
DifficultyIntermediate
Risk LevelN/A

Related Skills

Works Well With

Skills from the same repository — often designed to work together