altitude-horizon-framework

Define a two-axis mental model distinguishing Director-level from PM thinking.

8|1|Updated Dec 28, 2025
One-click install
npx skills add https://github.com/officebeats/beats-pm-kit --skill altitude-horizon-framework-officebeats
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: altitude-horizon-framework
Source: https://github.com/officebeats/beats-pm-kit/tree/main/.agent/skills/altitude-horizon-framework
Command: npx skills add https://github.com/officebeats/beats-pm-kit --skill altitude-horizon-framework-officebeats

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps Product Managers understand and navigate the critical shift in thinking and responsibilities required to transition into a Director-level role, addressing common friction points and providing a framework for effective leadership.

Core Features & Use Cases

  • Conceptual Framework: Introduces the "Altitude" (scope) and "Horizon" (time) axes to differentiate PM and Director thinking.
  • Transition Zone Diagnosis: Helps identify specific areas of difficulty in the PM-to-Director shift (e.g., Thinking Altitude, Persona Shift, Hero Syndrome Recovery, Direction Creation).
  • Cascading Context Map: Provides a structured method for Directors to create clarity and translate vague company strategy into actionable team direction.
  • Use Case: A Senior PM preparing for a Director promotion can use this Skill to understand the key differences in responsibilities and mindset. A newly promoted Director can use it to diagnose why they might be struggling to adapt and apply the Cascading Context Map to align their team.

Quick Start

Use the altitude-horizon-framework skill to understand the difference between PM and Director thinking.

Frequently Asked Questions about altitude-horizon-framework

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How does a Product Manager transition to a Director role?

A Product Manager transitions to a Director by shifting their thinking across two axes: Altitude (scope) and Horizon (time). This framework helps identify transition friction points like Persona Shift and Hero Syndrome Recovery to adopt Director-level leadership.

What is the difference between PM and Director thinking in product management?

The main difference between PM and Director thinking involves scope and time-horizon. Directors operate at a higher Altitude managing broader scope and a longer Horizon for strategy, whereas PMs focus on specific execution and shorter timeframes.

How do I create clarity from vague company strategy as a new Director?

You create clarity from vague strategy by applying the Cascading Context Map. This structured method helps Directors translate ambiguous company direction into actionable, clear team objectives and leadership alignment.

Why do newly promoted Product Directors struggle with team leadership?

Newly promoted Product Directors often struggle due to Hero Syndrome Recovery and a failure to shift their thinking Altitude. This framework diagnoses these specific transition gaps to help adapt leadership responsibilities and mindset.

What is the best framework for diagnosing PM to Director transition friction?

The Altitude-Horizon framework is designed for diagnosing PM to Director transition friction. It evaluates gaps in Direction Creation, scope management, and time-horizon perspective to pinpoint why a career transition is struggling.

Can I use the altitude horizon framework for Senior PM career transition preparation?

Yes, a Senior PM preparing for a Director promotion can use the Altitude-Horizon framework. It clarifies the key differences in responsibilities, scope, and leadership mindset required for a successful career transition.