Altitude-Horizon Framework Examples

This file shows how to apply the framework in a realistic PM-to-Director transition scenario.

Example 1: Good Use of the Cascading Context Map

Scenario

Company priority from CEO: "Win larger enterprise deals this year."

A newly promoted Director has three PMs asking: "What does that mean for our roadmaps this quarter?"

Completed Context Cascade

## Context Cascade

**Company Priority:** Win larger enterprise deals this year.

**Business Unit Translation:** Increase average contract value and reduce time-to-security-approval for enterprise prospects.

**Product Portfolio Translation:**
- Product A: strengthen admin controls and role permissions
- Product B: improve API documentation and integration reliability
- Product C: close SOC 2 and SSO adoption gaps

**Team Accountabilities:**
- Team A owns admin controls and audit logs
- Team B owns API docs, SDK quality, and integration examples
- Team C owns security certifications and SSO implementation quality

**Why this matters:**
Enterprise growth does not mean "build random enterprise features."
It means removing blockers that stall enterprise deals and procurement.

Why This Is Strong

Translates vague strategy into concrete team ownership.
Preserves altitude: portfolio and outcomes first, backlog details second.
Makes trade-offs visible: what changes now vs. later.

Example 2: Anti-Pattern (Hero Syndrome)

Scenario

A PM escalates a conflict with Sales about roadmap commitments.

Director Response (Weak)

"I will jump into the account call and handle this for you."

Director Response (Strong)

"Walk me through your current framing. I will coach your next move, then you lead the conversation."

Why the First Response Fails

Solves immediate pain but reinforces dependency.
Keeps the Director in PM-level conflict resolution.
Prevents PM growth on stakeholder leadership.

Better Follow-Through

Debrief the PM's framing.
Align on one clear message and one fallback position.
Let PM lead with Director in support.
Post-call: identify one behavior to improve next time.

Example 3: Altitude Calibration Check

Use this quick self-audit before major decisions:

Am I deciding at team/backlog altitude or portfolio altitude?
Who should own this decision at my current role level?
If I step in, am I building system clarity or rescuing execution?
What context translation is missing for the team right now?

If most answers point to execution rescue, you are likely slipping into Hero Syndrome.

Third-party checks

No alerts17d5 checks · Risk SAFE

Gen Agent Trust Hub17d
The skill provides a conceptual leadership framework for product managers transitioning to director roles. It is generally safe but presents a minor surface for indirect prompt injection because it processes user-provided context to generate diagnostic advice without explicit boundary markers.
Socket17d
No alerts
Snyk17d
Risk: LOW · No issues
Runlayer6mo
1/2 files flagged
ZeroLeaks5mo
Score: 93/100 · 2 sections analyzed

Capability

type: component
theme: career-leadership
estimated_time: 10-15 min

Other metadata

intent: Defines the two-axis mental model that distinguishes Director-level thinking from PM thinking: **Altitude** (how wide you zoom out) and **Horizon** (how far ahead you look). Use this to understand what actually changes in the transition, diagnose which transition zone is creating friction, and apply the Cascading Context Map when organizational direction is vague or absent.
best_for: [ "Understanding what actually changes when you move from PM to Director", "Diagnosing which transition zone is creating friction in your role", "Applying the Cascading Context Map when organizational direction is vague" ]
scenarios: [ "I'm a senior PM trying to understand what changes when I become a Director", "I'm newly promoted to Director and something isn't clicking — help me diagnose it", "My team has no clear direction and I need to create context from a vague company strategy" ]

/altitude-horizon-framework

examplessample.md