altitude-horizon-framework

## 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 | Individ...