Altitude Horizon Framework

Altitude Horizon Framework

Understand the PM-to-Director transition through altitude and horizon thinking. Use when diagnosing scope, time-horizon, or leadership-level gaps

Category: development Source: deanpeters/Product-Manager-Skills

What Is This?

Overview

The Altitude Horizon Framework is a two-axis mental model designed to clarify what actually changes when a Product Manager transitions into a Director-level role. Rather than describing the shift in vague terms like "thinking more strategically," this framework gives precise language to two distinct dimensions: Altitude, which describes how wide you zoom out across the organization, and Horizon, which describes how far ahead in time you are planning and reasoning.

Altitude refers to the scope of your thinking. A PM operating at low altitude focuses on a single product, a specific feature set, or a defined user problem. A Director operating at high altitude must hold multiple products, teams, and business lines in view simultaneously. Horizon refers to the temporal dimension of your thinking. A PM typically operates on a horizon of weeks to a few months, optimizing for sprint delivery and quarterly goals. A Director must extend that horizon to one, two, or even three years, anticipating market shifts, organizational needs, and capability gaps before they become urgent.

Together, these two axes form a diagnostic grid. When friction appears during a leadership transition, this framework helps identify whether the gap is in scope awareness, time-horizon planning, or both. It removes ambiguity from performance conversations and gives individuals a concrete map for their own development.

Who Should Use This

  • Product Managers preparing for or recently promoted into Director roles
  • Engineering or Design leads moving into cross-functional leadership positions
  • Managers of Managers diagnosing performance gaps in their direct reports
  • HR and Talent Development professionals building leadership competency frameworks
  • Executive coaches working with mid-level leaders on scope and strategy
  • Organizational designers structuring role expectations across product leadership levels

Why Use It?

Problems It Solves

  • Vague feedback like "you need to think more strategically" gives no actionable direction, this framework replaces that with specific, measurable dimensions
  • Leaders in transition often optimize for the wrong time horizon, staying focused on immediate delivery when organizational health requires longer-range planning
  • Scope creep in thinking, where a new Director micromanages a single product instead of balancing a portfolio, becomes visible and diagnosable
  • Teams and stakeholders receive inconsistent leadership because the leader has not adjusted their operating altitude to match their new role
  • Performance reviews lack precision when evaluating senior ICs or managers moving into leadership, this model provides a shared vocabulary

Core Highlights

  • Two-axis model: Altitude (scope width) and Horizon (time depth)
  • Applies to both self-assessment and manager-to-report feedback conversations
  • Identifies the specific transition zone creating friction, not just that friction exists
  • Portable across product, engineering, design, and data leadership roles
  • Supports career development planning with concrete, observable behaviors
  • Complements existing frameworks like OKRs, RACI, and product strategy templates
  • Scales from individual coaching to team-wide leadership development programs

How to Use It?

Basic Usage

Start by plotting your current operating patterns on both axes. Use a simple scoring exercise to calibrate your position.

Altitude Assessment (1-5 scale):
1 = Single feature or task focus
2 = Single product focus
3 = Product area or domain focus
4 = Multi-product or business unit focus
5 = Full portfolio or company-wide focus

Horizon Assessment (1-5 scale):
1 = Days to two weeks (sprint level)
2 = One to three months (quarterly)
3 = Three to six months (half-year)
4 = Six to twelve months (annual)
5 = One to three years (multi-year strategy)

A PM operating effectively typically scores 2 to 3 on Altitude and 2 to 3 on Horizon. A Director operating effectively typically scores 4 to 5 on both axes.

Specific Scenarios

Scenario 1: New Director still acting like a PM. A newly promoted Director continues to attend every sprint review, write detailed acceptance criteria, and focus exclusively on one product team. Their Altitude score is 2, Horizon score is 2. The gap is clear: they need structured exposure to portfolio-level decisions and multi-year planning cycles.

Scenario 2: PM ready for promotion. A senior PM consistently raises cross-team dependencies in planning, flags risks six months out, and proposes solutions that account for adjacent teams. Their Altitude score is 4, Horizon score is 4. The framework confirms readiness.

Real-World Examples

Director Weekly Agenda Template (Altitude 4-5, Horizon 4-5):
- Monday: Portfolio health review across all product areas
- Tuesday: Stakeholder alignment on 12-month roadmap priorities
- Wednesday: Org capability gap assessment
- Thursday: Cross-functional leadership sync
- Friday: Strategic narrative review and external signal scanning

A PM weekly agenda, by contrast, centers on sprint goals, user research synthesis, and feature delivery status.