altitude-horizon-framework

Diagnoses PM-to-Director transition gaps using altitude and horizon thinking frameworks.

1|1|Updated Jul 6, 2026

Search Tags:#product management #career development #leadership transition #strategy cascade #coaching framework #director readiness

Ready to run

npx skills add https://github.com/muhammaddadu/ai-skill-collection --skill altitude-horizon-framework-muhammaddadu

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: altitude-horizon-framework
Source: https://github.com/muhammaddadu/ai-skill-collection/tree/main/career/altitude-horizon-framework
Command: npx skills add https://github.com/muhammaddadu/ai-skill-collection --skill altitude-horizon-framework-muhammaddadu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Product managers moving into Director roles often struggle to understand what actually changes in scope, time horizon, and leadership behavior, leaving them stuck in old habits like hero syndrome and tactical execution. ## Core Features & Use Cases - Two-Axis Mental Model: Explains Altitude (scope of view) and Horizon (timeframe of planning) to distinguish PM-level from Director-level thinking. - Four Transition Zones Diagnosis: Identifies friction in thinking altitude, persona shift, hero syndrome recovery, or direction creation. - Cascading Context Map: Provides a six-step method to translate vague company strategy into concrete team accountabilities. - Use Case: A newly promoted Director whose team lacks direction uses the Cascading Context Map to convert a vague CEO priority like "win enterprise deals" into specific portfolio and team ownership. ## Quick Start Ask the assistant to diagnose which PM-to-Director transition zone is causing friction in your current role using the altitude-horizon framework.

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?▼

The transition requires shifting across four zones: thinking altitude, persona focus, hero syndrome recovery, and direction creation. Diagnose which zone creates the most friction for you, then apply targeted practices like the Cascading Context Map for strategy translation.

What is the difference between PM and Director thinking?▼

PMs operate at low altitude with short horizons, focusing on individual customers, features, and sprints. Directors operate at portfolio altitude with quarterly-to-annual horizons, focusing on systems, budgets, and organizational dynamics rather than individual wins.

How do I create team clarity when company strategy is vague?▼

Use the Cascading Context Map: extract 3-5 priorities from executive communications, then translate them through business unit, product portfolio, and team accountability layers. Directors create imperfect-but-useful clarity rather than waiting for perfect direction.

What is hero syndrome in product leadership?▼

Hero syndrome is when Directors jump in to solve problems directly instead of coaching their team. It happens because PMs are trained to be helpful, but the habit prevents team growth and keeps the Director operating at the wrong altitude.

When should a PM not use Director-level thinking?▼

PMs should not prematurely adopt Director thinking while still in a PM role, as it causes them to miss customer-level signals their actual job requires. Serve your current scope fully; Director altitude becomes relevant only when the role demands it.