altitude-horizon-framework

Map Product Manager to Director transitions using altitude and horizon zones.

Updated Feb 16, 2026
One-click install
npx skills add https://github.com/MMXC/openclaw-back --skill altitude-horizon-framework-mmxc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: altitude-horizon-framework
Source: https://github.com/MMXC/openclaw-back/tree/main/pm-skills/skills/altitude-horizon-framework
Command: npx skills add https://github.com/MMXC/openclaw-back --skill altitude-horizon-framework-mmxc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a mental model to navigate the transition from Product Manager to Director, addressing the shift in scope, time horizon, and responsibilities.

Core Features & Use Cases

  • Altitude & Horizon Model: Understand the difference in scope (altitude) and time (horizon) between PM and Director roles.
  • Role Transition Diagnosis: Identify friction points in the transition using four distinct zones (Thinking Altitude, Persona Shift, Hero Syndrome Recovery, Direction Creation).
  • Cascading Context Map: Learn to create clarity by translating vague company strategy into actionable team priorities.
  • Failure Mode Identification: Recognize and avoid common pitfalls like Hero Syndrome and Allergic to Process.
  • Use Case: A senior PM preparing for a Director promotion can use this framework to understand the expected changes and proactively address potential challenges. A new Director can use it to diagnose why their new role feels misaligned.

Quick Start

Use the altitude-horizon-framework skill to understand the core differences between a PM and a Director role.

Frequently Asked Questions about altitude-horizon-framework

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

FAQPage Schema
How do I transition from Product Manager to Director successfully?

To transition from Product Manager to Director, you must shift your thinking altitude and time horizon. This framework provides a mental model focusing on strategic thinking, system design, and cascading context to navigate the role change and avoid common failure modes.

What is the difference in time horizon and scope between a PM and a Director?

The difference between a PM and a Director lies in altitude (scope) and horizon (time). Directors operate at a higher thinking altitude, focusing on system design and organizational dynamics, while extending their time horizon beyond immediate product delivery to establish long-term strategic direction.

How do I translate vague company strategy into actionable team priorities?

Translating vague company strategy into actionable team priorities requires the Cascading Context Map. This tool creates organizational clarity by systematically breaking down high-level strategic goals into specific, actionable directions for your product teams.

Why does my new Director role feel misaligned and how can I diagnose it?

Your new Director role feels misaligned due to friction in transition zones like Persona Shift or Hero Syndrome. Diagnose this misalignment by evaluating your thinking altitude and checking if you are still acting as an individual contributor instead of creating organizational direction.

What are common failure modes when moving into a product leadership role?

Common failure modes when moving into a product leadership role include Hero Syndrome and being Allergic to Process. These pitfalls occur when new Directors fail to shift their altitude, continuing to act as individual contributors rather than establishing systemic organizational clarity.

Do I need to change my leadership style for a Director promotion in product management?

A Director promotion in product management requires a Persona Shift in your leadership style. You must move from direct execution to system design and stakeholder management, ensuring your new leadership style aligns with the expected thinking altitude and time horizon.