altitude-horizon-framework

Diagnose PM-to-Director transition friction using altitude and horizon axes.

24|3|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/Prorise-cool/prorise-claude-skills --skill altitude-horizon-framework
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: altitude-horizon-framework
Source: https://github.com/Prorise-cool/prorise-claude-skills/tree/main/.claude/skills/product-specialist/references/domains/product-management/altitude-horizon-framework
Command: npx skills add https://github.com/Prorise-cool/prorise-claude-skills --skill altitude-horizon-framework

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 required to transition into a Director role, addressing common friction points and providing a framework for effective leadership.

Core Features & Use Cases

  • Altitude & Horizon Model: Differentiates PM and Director thinking across scope and time.
  • Transition Zone Diagnosis: Identifies specific areas of struggle in the PM-to-Director move.
  • Cascading Context Map: Provides a method to create clarity from vague organizational strategy.
  • Use Case: A newly promoted Director can use this to understand why they feel misaligned with their new responsibilities and how to better translate company strategy to their team.

Quick Start

Use the altitude-horizon-framework skill to understand the differences between a PM and a Director's scope and time horizon.

Frequently Asked Questions about altitude-horizon-framework

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

FAQPage Schema
How does the transition from Product Manager to Director change scope and time horizon?

The PM to Director transition requires shifting your altitude (organizational scope) and horizon (strategic time frame). Directors must move beyond individual product execution to define broader organizational clarity and translate vague company strategy for their teams.

What is Hero Syndrome and how do I avoid it when promoted to a Product Director?

Hero Syndrome is a common failure mode during the PM to Director transition where leaders micromanage execution instead of guiding strategy. To avoid this friction, Directors must use frameworks like the Cascading Context Map to delegate effectively and align team scope.

How do I translate vague company strategy into actionable context for my product team?

You translate vague company strategy into actionable context using the Cascading Context Map. This method helps new Directors diagnose transition friction zones and create organizational clarity by systematically mapping strategic altitude and horizon to specific team responsibilities.

Why do newly promoted Product Directors feel misaligned with their new leadership responsibilities?

Newly promoted Product Directors feel misaligned because they struggle with organizational dynamics and changing scope. The transition shifts focus from direct product management to leadership, often causing friction when previous PM-level execution habits conflict with new strategic altitude requirements.

Can this altitude and horizon framework be used for product leadership coaching?

Yes, the altitude and horizon framework is explicitly useful for career development and leadership coaching in product organizations. It provides a structured model to diagnose transition zones and failure modes, helping coaches guide Product Managers into Director roles effectively.