altitude-horizon-framework

Diagnose PM-to-Director transitions using altitude and horizon mapping.

1|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/tabooes/pm_skills --skill altitude-horizon-framework-tabooes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: altitude-horizon-framework
Source: https://github.com/tabooes/pm_skills/tree/main/skills/altitude-horizon-framework
Command: npx skills add https://github.com/tabooes/pm_skills --skill altitude-horizon-framework-tabooes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This framework helps product leaders move from PM to Director by providing a clear mental model to reason about scope (Altitude) and time horizon (Horizon), enabling better role clarity and strategic alignment.

Core Features & Use Cases

  • Altitude & Horizon mapping: distinguish when to think about a product portfolio vs. individual features.
  • Cascading Context Map: translate vague company priorities into concrete team accountabilities.
  • Transition-zone diagnosis: identify which zone (Thinking Altitude, Persona Shift, Hero Syndrome, or Direction Creation) is creating friction, and how to intervene.
  • Use Case: a newly promoted Director uses the framework to align teams to a quarterly plan; a senior PM prepares for Director-level responsibilities with a mapped context cascade.

Quick Start

Identify your current transition zone, and draft a Cascading Context Map to translate strategy into team priorities.

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 PM to product director successfully?

To transition from PM to product director successfully, you must shift your thinking altitude from individual features to portfolio scope and extend your time horizon. Diagnosing transition zones like Hero Syndrome helps navigate role clarity and strategic alignment.

What is a Cascading Context Map for product management?

A Cascading Context Map for product management translates vague company priorities into concrete team accountabilities. It guides newly promoted directors in mapping organizational strategy to cross-functional team priorities during quarterly planning.

How do I translate company strategy into team priorities?

You translate company strategy into team priorities by drafting a Cascading Context Map. This structured practice aligns teams to a quarterly plan by shifting your perspective across different altitudes and time horizons to ensure strategic alignment.

Why do newly promoted product directors struggle with role clarity?

Newly promoted product directors struggle with role clarity due to friction in transition zones like Thinking Altitude, Persona Shift, Hero Syndrome, or Direction Creation. Identifying these zones helps intervene and establish better strategic alignment.

When should I use altitude and horizon mapping in product management?

You should use altitude and horizon mapping in product management during role transitions, organizational strategy translation, and cross-functional planning. It distinguishes when to reason about a product portfolio versus individual features to ensure proper scope.

Can I use this framework to prepare for director-level responsibilities as a senior PM?

Yes, you can use this framework to prepare for director-level responsibilities as a senior PM. It provides a mental model to map context cascades, identify transition zones creating friction, and practice structured cross-functional planning for role transitions.