---
name: director-readiness-advisor
description: Use when a PM is preparing for, actively interviewing for, newly settled into, or struggling to recalibrate within a Director of Product role — to surface the specific failure modes and highest-leverage moves for that exact situation.
role: product-manager
intent: |
  Diagnoses which of four distinct phases of the PM-to-Director transition
  you are in, then delivers coaching calibrated to that phase rather than
  generic leadership advice. Surfaces the two or three behavioral changes
  that matter most right now, not a comprehensive development catalogue.
type: interactive
theme: career-leadership
best_for:
  - A senior PM with 3–12 months before a Director interview or promotion conversation
  - A newly promoted or hired Director in the first six months of the role
  - A Director 12+ months in who recognises a persistent pattern that isn't resolving
scenarios:
  - "I'm being considered for Director internally and don't know what to change about how I work"
  - "I just landed the Director role and I keep pulling my team's tickets into my own queue"
  - "I've been a Director for two years and my executive relationships still feel transactional"
estimated_time: "10–15 min"
---

# Director readiness advisor

> v0 draft. Anchored in the altitude-horizon mental model from *The Product Porch* (Todd Blaquiere, Ryan Cantwell, Joe Ghali, Ep. 42, January 2026); supplemented by Watkins (*The First 90 Days*), Zhuo (*The Making of a Manager*), and Cagan (*Empowered*). Editorial review recommended before production use.

## Purpose

The PM-to-Director transition is not a promotion — it is a role change. The work is different, the failure modes are different, and the feedback loops are longer and more ambiguous. Most advice about it is either too abstract ("think more strategically") or context-free (the same coaching for someone six months out as for someone eighteen months in).

This skill runs a diagnostic first. It establishes where you are in the journey — preparing, interviewing, newly landed, or recalibrating — and then delivers the two or three moves that are actually load-bearing for that situation. Coaching without diagnosis is noise.

## Key Concepts

### The four transition situations

The transition looks completely different depending on your position in it. Each situation has distinct coaching priorities, and the biggest mistake is applying advice from the wrong one.

#### Preparing to make the leap

You are still operating as a PM. The work here is behavioural: identifying which instincts to stop reinforcing and which new muscles to start building — *before* they are tested in a new role. The preparation error is treating this as a checklist of things to demonstrate rather than habits to genuinely change. The altitude shift (from solving customer problems directly to designing the conditions in which others solve them) does not happen automatically at promotion; it has to be practised.

Key concept: **altitude versus horizon.** Altitude is the scope of thinking — PM-altitude is product and feature; Director-altitude is portfolio and organisation. Horizon is the time window — PM-horizon is sprint and quarter; Director-horizon is annual and multi-year. Watkins (*The First 90 Days*) frames this as the core cognitive shift: the leader who continues to operate at the altitude of their previous role builds a glass ceiling made of their own habits.

#### Interviewing for Director roles

The interview is not a knowledge test. Interviewers are probing for evidence that the altitude and horizon shift has already begun — not that you have memorised a framework. The interview failure mode is performing the vocabulary without demonstrating the lived experience: saying "I think about portfolio-level trade-offs" without a concrete story in which you actually made one.

Interview prep is story work, not concept work. For each of the transition zones (see [altitude-horizon-framework](../altitude-horizon-framework/SKILL.md)), you need at least one specific first-person story. Stories reveal calibration; frameworks reveal study.

#### Newly landed

The first six months are the highest-stakes window. Watkins identifies this as the period when patterns get established that are very hard to break later. The two most common failure modes in this phase:

**Hero syndrome** (Blaquiere et al., Ep. 42): the Director who keeps jumping in to solve problems directly — picking up slack, rewriting specs, inserting themselves into decisions that a PM should own. Hero syndrome feels like helpfulness; it registers to the team as a signal that they aren't trusted. It also robs the Director of the thinking time that the role requires.

**Direction vacuum**: the opposite failure — a Director who waits for strategy clarity from above before giving their team context. Direction rarely arrives top-down in a clean form. The Director's job is to translate whatever signal exists into actionable orientation for the team, and to revise that translation as more signal arrives.

Zhuo (*The Making of a Manager*) names the core shift: your personal output matters less than the output of the people you lead. A Director who produces excellent work while their team is adrift is failing the role.

#### Recalibrating

Being in the role for 12+ months and still experiencing a persistent problem is a different diagnostic than early-stage friction. By this point, transition-period explanations don't hold. The pattern is now structural — the result of settled habits, established relationships, or a mismatch between the role as defined and how you are operating in it.

The Cagan (*Empowered*) framing is useful here: a Director who is still acting as an individual contributor is not filling the leadership vacuum — they are creating it. The PMs underneath them do not grow; the portfolio lacks coherent direction; and the Director becomes the bottleneck for every decision that should be distributed.

Recalibration requires naming the specific pattern, understanding its root cause, and making a deliberate structural change — not harder effort in the same direction.

### The altitude-horizon mental model

This skill coaches on the application of a framework described fully in [altitude-horizon-framework](../altitude-horizon-framework/SKILL.md). The concepts used here:

- **Altitude shift**: from direct problem-solving to environment design
- **Horizon extension**: from quarterly to annual thinking
- **Waiter-to-restaurant-operator**: the core persona shift — from executing tasks well to designing a system that consistently produces good outcomes without your constant involvement
- **Four transition zones**: Thinking Altitude, Persona Shift, Hero Syndrome Recovery, Direction Creation

Understanding the framework deeply is prerequisite to coaching on it fluently in interviews or 1-on-1s.

## Application

This advisor runs a diagnostic question, one adaptive follow-up, and then delivers three to five numbered recommendations specific to your situation.

### Step 0: Entry mode

Before the first question, offer three paths:

1. **Guided** — questions one at a time, recommendations built from your answers. Recommended for most situations.
2. **Context dump** — describe your situation in full; skip to coaching.
3. **Best guess** — no intake; deliver the highest-value advice for the most common situation (newly landed Director, first 90 days, hero-syndrome pattern).

---

### Question 1: Where are you? (Q1/3)

"Which of these describes your situation right now?"

1. **Preparing** — Still in a PM role; actively working toward Director over the next 3–12 months.
2. **Interviewing** — In an active process — internal promotion or external search.
3. **Newly landed** — Promoted or hired as Director in roughly the last six months.
4. **Recalibrating** — Been in the Director role for a while; something persistent isn't working.

Or describe your situation directly.

---

### Branch 1: Preparing

**Question 1B (Q2/3):** "What's the gap you most want to close?"

1. **Altitude** — I still default to solving problems directly rather than coaching others to solve them.
2. **Stakeholder navigation** — I struggle with executive dynamics, organisational politics, or cross-functional influence at the right level.
3. **Strategic narrative** — I can't yet connect my team's work to company strategy convincingly.
4. **Direction creation** — I wait for clarity from above rather than generating it for my team.

**Question 1C (Q3/3):** "What's your runway?"

1. **6+ months** — Building deliberately; no immediate pressure.
2. **3–6 months** — Starting to signal readiness; preparing to have the conversation.
3. **Actively moving** — In motion now or imminent.

**Recommendation delivery (example: gap = strategic narrative, runway = 3–6 months):**

"Here are the three highest-leverage moves for your situation:

1. **Reframe your 1-on-1s as strategic conversations** — Shift from reporting progress to asking how your team's work connects to this year's company priorities. This builds the muscle and signals readiness to your manager simultaneously.
2. **Write a one-page context cascade** — Take the most recent company priority you heard in an all-hands or QBR and translate it for your team: what does it mean for their portfolio? Share it informally with your manager. You don't need permission to practise this.
3. **Audit your hero ratio** — Track two weeks: how often do you solve a problem that a PM on your team could solve with coaching? The ratio of rescuing to developing is a leading indicator of readiness. If it's above 50%, that's the gap to close before the timeline you named.

Choose a number to go deeper, or tell me what you want to work on."

---

### Branch 2: Interviewing

**Question 2B (Q2/3):** "What's your interview context?"

1. **Internal** — Promotion process within my current company.
2. **External** — Interviewing at new organisations.
3. **Both** — Running internal and external processes in parallel.

**Question 2C (Q3/3):** "Where do you want to focus prep?"

1. **Internalising the model** — I want to understand the altitude-horizon framework deeply enough to reason from it, not just recite it.
2. **Building stories** — I understand the concepts; I struggle to map them to my own experience.
3. **Practising responses** — I want to rehearse answers to likely Director interview questions.
4. **Diagnosing gaps** — I want to know which transition zones I haven't demonstrated and how to address that honestly.

**Recommendation delivery (example: context = external, focus = building stories):**

"The highest-leverage interview prep is story mining, not concept review. Here's the sequence:

1. **Work through [altitude-horizon-framework](../altitude-horizon-framework/SKILL.md) as a diagnostic** — After each section, ask: where have I actually operated at this altitude or horizon? What is my concrete story? If you can't generate one, that's your gap — and naming it honestly in an interview is stronger than avoiding it.
2. **Build one story per transition zone** — Four zones; four stories minimum. Use the zone name as the structure: 'here's when I had to shift my thinking altitude; here's what triggered the persona shift.' Interviewers notice this self-awareness quickly.
3. **Reframe your wins in Director language** — Don't open with 'I shipped X.' Open with: 'The strategic question my team was facing was Y. Here's how I thought about the portfolio trade-off.' The outcome is your evidence, not your headline.
4. **Prepare for the gap question** — If you haven't managed direct reports or operated at portfolio level, don't avoid it. The strongest answer is: 'Here's the gap; here's how I've been developing toward it; here's what I'd prioritise learning in the first 90 days.' A plan lands better than avoidance.

Choose a number to go deeper, or describe what you want to practise."

---

### Branch 3: Newly landed

**Question 3B (Q2/3):** "What's your most pressing challenge right now?"

1. **Still thinking like a PM** — I default to solving problems directly rather than directing others to solve them.
2. **Hero syndrome** — I know I should let the team own things; I can't stop pulling work into my queue.
3. **Direction vacuum** — I'm waiting for strategy clarity from above that isn't coming, and the team is adrift.
4. **Wrong stakeholder relationships** — I'm spending time with the people I knew before; I haven't built the peer and exec relationships the role requires.

**Question 3C (Q3/3):** "What's your team situation?"

1. **Inherited team** — Established PMs with existing processes and relationships.
2. **New team** — Hiring into a newly formed or restructured group.
3. **Mixed** — Some experienced, some new, some in transition.

**Recommendation delivery (example: challenge = direction vacuum, team = inherited):**

"An inherited team without directional context from you is the most common first-90-days failure mode. Here's what to do:

1. **Write a context cascade this week — don't wait for perfect clarity** — Take the most recent company priority you heard and translate it down: what does it mean for your portfolio? One page. Share it. Make it explicit that it's provisional and you'll revise it as you learn more. The team needs some orientation, not perfect orientation.
2. **Redirect 1-on-1s immediately** — Most PMs will try to brief you on feature status. Redirect: 'I want to understand how each of your products connects to the business goals I'm accountable for. Walk me through the through-line.' This sets altitude expectations from day one.
3. **Name the ambiguity explicitly** — Teams handle honest partial context better than silence. 'I'm still building my picture of where leadership wants us to focus. Here's my current best translation. I'll update it in two weeks.' Silence reads as incompetence; named uncertainty reads as leadership.
4. **Don't reorganise before you understand** — The inherited structure has history. Give yourself 60–90 days before changing processes or reporting lines. The processes you find frustrating may be doing important work you haven't yet seen.

Choose a number to go deeper, or tell me what's most blocking you."

---

### Branch 4: Recalibrating

**Question 4B (Q2/3):** "Where does the role feel most broken?"

1. **Still acting like a PM** — I'm doing IC work alongside my team; I haven't made the altitude shift stick.
2. **Team isn't growing** — The PMs under me aren't developing; quality and delivery are inconsistent.
3. **Executive relationships aren't working** — I'm not getting the visibility, trust, or buy-in I need at that level.
4. **Portfolio lacks coherence** — I'm managing a collection of roadmaps, not a system with a shared direction.

**Question 4C (Q3/3):** "How long have you been in this role?"

1. **Under a year** — Still within the typical transition window.
2. **1–2 years** — Past the transition period; this feels like a settled pattern.
3. **2+ years** — Established in the role; this is structural.

**Recommendation delivery (example: friction = still acting like PM, tenure = 1–2 years):**

"At 12+ months, this is no longer a transition problem — it's a settled operating mode. Diagnosis before prescription:

1. **Measure the ratio first** — Track two weeks: what percentage of your time is spent solving problems versus developing people who solve problems? Most Directors in this pattern are at 60–70% IC. The target is closer to 20%. You can't change what you haven't quantified.
2. **Identify the root cause** — There are three typical drivers: (a) you trust your judgment more than the team's current capability, (b) the team hasn't been developed enough to own things without rescue, (c) you're getting reward signals (praise, urgency, visibility) that reinforce IC behaviour. Which one is it? The fix differs for each.
3. **Create deliberate handoffs for your top three IC activities** — List the three things you do most often that a PM should own. For each: write down what 'done well' looks like, have an explicit conversation about ownership, then don't rescue when they struggle. Coaching through failure is the Director's actual work.
4. **Redesign the reward loop** — The feedback signals that reinforced great PM work (praise, launches, visible impact) come less often and less directly as a Director. Find the new signal: a PM who navigates a hard stakeholder conversation without you, a team that creates its own context cascade, a portfolio decision you made that held up under pressure. Start noticing those.
5. **If the pattern is entrenched at 1–2 years, consider whether the role is the right fit** — The senior IC or Principal PM path is legitimate and valuable. Misalignment between the role you hold and the work you want to do is not failure — it is information. Better to name it than to keep optimising the wrong variable.

Choose a number to go deeper, or tell me what you want to focus on."

---

## Examples

### Example A: Newly landed — direction vacuum, inherited team

**User input flow:**

- Q1: "3 — Newly landed"
- Q2: "3 — Direction vacuum"
- Q3: "1 — Inherited an established team"

**Advisor output summary:** Four recommendations covering the provisional context cascade (write it now, don't wait), redirecting 1-on-1 topics to strategic through-lines, naming ambiguity explicitly rather than projecting false confidence, and resisting premature reorganisation of inherited structure. Recommended follow-on: read [altitude-horizon-framework](../altitude-horizon-framework/SKILL.md) section on Direction Creation and the Cascading Context Map template.

---

### Example B: Preparing — strategic narrative gap, 3–6 months out

**User input flow:**

- Q1: "1 — Preparing"
- Q2: "3 — Strategic narrative"
- Q3: "2 — 3–6 months"

**Advisor output summary:** Three recommendations — reframe 1-on-1s as strategic conversations, build a one-page context cascade, audit the hero ratio. Warning against over-investing in Director-altitude thinking while still in a PM role: the most common preparation error is performing above your current level at the expense of serving it well.

---

### Example C: Recalibrating — executive relationships, 2+ years

**User input flow:**

- Q1: "4 — Recalibrating"
- Q2: "3 — Executive relationships aren't working"
- Q3: "3 — 2+ years"

**Advisor output summary:** The executive-relationship problem at 2+ years is almost always a positioning problem, not a rapport problem. Diagnosis questions: Are you meeting executives where they need information (portfolio health, risk, strategic trade-offs) or where you need to report (features shipped, team velocity)? Are you a peer in their planning conversations or a supplier of status updates? Recommendations focus on repositioning the interaction — leading with strategic questions rather than operational updates, asking for their constraints rather than presenting your plans, and making your portfolio decision-making visible at the right altitude.

---

## Common Pitfalls

### Pitfall 1: Treating the transition as a checklist

**Symptom.** Asking "what do I need to do to get promoted?" and working through development items like a task list — demonstrating altitude thinking in one-on-one conversations while continuing to operate as a PM everywhere else.

**Consequence.** You optimise for the appearance of readiness rather than the actual behavioural change. Interviewers and managers can distinguish between performed vocabulary and lived altitude shift.

**Fix.** Use this advisor to identify one or two specific behavioural changes — not a comprehensive development programme. The question is not "what skills do Directors need?" but "what is the one habit I most need to break or build right now?"

---

### Pitfall 2: Misidentifying your phase

**Symptom.** Selecting "preparing" when you are already in an active interview process, or selecting "newly landed" when you have been in the role for 18 months. The phase selection answers how you feel, not where you objectively are.

**Consequence.** Coaching calibrated to the wrong phase. A recalibrating Director who uses newly-landed framing gives themselves too much transitional latitude for a pattern that is now structural.

**Fix.** Be honest about your actual timeline. The coaching in Branch 4 is harder to hear than Branch 3 — that discomfort is diagnostic information about which branch applies.

---

### Pitfall 3: Seeking a readiness verdict

**Symptom.** Using this advisor to find out whether you are "ready" for the Director role, expecting a pass/fail answer.

**Consequence.** There is no readiness threshold that makes the transition safe. The transition involves ambiguity by design. A verdict-seeking framing produces either false confidence or unnecessary hesitation, both of which are more harmful than named uncertainty.

**Fix.** Use this skill to identify what will be hardest for you specifically — and to work on that. Readiness is not a state you reach; it is a direction you orient toward.

---

### Pitfall 4: Hero syndrome as conscientiousness

**Symptom.** The newly landed Director frames their IC intervention as "helping the team," "maintaining quality," or "covering while someone ramps." The behaviour looks like commitment. It is praised in the short term.

**Consequence.** The team does not develop the ownership it needs. The Director becomes a bottleneck. Cagan (*Empowered*): a leader who holds all the judgment centralises all the risk.

**Fix.** The diagnostic question is not "is this intervention helpful right now?" but "does this intervention increase or decrease the team's ability to own this class of problem in the future?" If the answer is decrease, it is hero syndrome regardless of the short-term quality benefit.

---

### Pitfall 5: Waiting for top-down direction before acting

**Symptom.** The Director says "I don't have enough clarity from leadership to give my team direction" and waits. The team drifts. The Director feels blocked.

**Consequence.** Watkins (*The First 90 Days*): leaders who wait for permission to act rarely get it. The direction vacuum gets filled — by the loudest stakeholder, by default inertia, or by individual PMs optimising locally. None of those outcomes is better than an explicit provisional direction that gets revised.

**Fix.** Provisional direction is better than no direction. State clearly that it is provisional. Revise it publicly when you have more signal. The act of translating ambiguous context into actionable orientation is the job. If that feels uncomfortable, you are in the right discomfort.

---

### Pitfall 6: Diagnosing recalibration as a relationship problem

**Symptom.** The Director whose executive relationships aren't working focuses on rapport-building — more lunches, more face time, more small-talk — rather than on the substance of what they bring to those interactions.

**Consequence.** The relationship remains transactional because the executive's actual need (a Director who surfaces strategic trade-offs, manages portfolio risk, and thinks at the right altitude) is not being met. More contact at the wrong level does not produce better relationships.

**Fix.** Diagnose the interaction before investing in the relationship. Are you showing up as a strategic partner or a status reporter? The fix is usually content and altitude, not frequency and warmth.

---

## References

- **Todd Blaquiere, Ryan Cantwell, Joe Ghali** — *The Product Porch*, Episode 42: "From Product Manager to Director: How to Make the Shift (Part 1)" (January 2026, Simplecast). Primary source for the four transition situations and the failure modes named in Branches 3 and 4, including hero syndrome, direction vacuum, and the waiter-to-operator framing.

- **Michael Watkins** — *The First 90 Days: Proven Strategies for Getting Up to Speed Faster and Smarter* (2003, rev. 2013, Harvard Business Review Press). The 90-day diagnostic framework and the core observation that leadership patterns established in the transition window are difficult to break. Used throughout Branch 3 and Pitfall 5.

- **Julie Zhuo** — *The Making of a Manager: What to Do When Everyone Looks to You* (2019, Portfolio/Penguin). The IC-to-manager cognitive shift: your personal output matters less than the output of the people you lead. Anchors the altitude-shift framing in Branches 1 and 3, and the hero-syndrome consequence chain in Pitfall 4.

- **Marty Cagan** — *Empowered: Ordinary People, Extraordinary Products* (2020, Wiley). Organisational dynamics, leadership clarity as a precondition for team empowerment, and the centralised-risk consequence of hero syndrome in product organisations. Used in Branch 4 and Pitfall 4.

- **Related Hornero skills:**
  - [`altitude-horizon-framework`](../altitude-horizon-framework/SKILL.md) — The full mental model this skill coaches on: altitude/horizon axes, four transition zones, the Cascading Context Map template, and named failure modes. Read this before a Director interview; run this advisor after.
  - [`cross-functional-orchestration`](../cross-functional-orchestration/SKILL.md) — The Director's primary tool for decision-making across functions. As the role matures, orchestration skill becomes the mechanism through which strategic direction is operationalised.
  - [`okrs`](../okrs/SKILL.md) — OKRs are the Director's primary instrument for translating portfolio direction into team-level orientation. A Director who sets clear OKRs reduces the direction-vacuum failure mode structurally.
  - [`strategy-kernel`](../strategy-kernel/SKILL.md) — Producing a coherent portfolio-level strategy kernel is the primary Director deliverable that distinguishes the role from senior PM work. If executive relationships feel transactional, the missing ingredient is often a clear kernel.

*Synthesis cue: adapted from Dean Peters' [Product-Manager-Skills](https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/director-readiness-advisor) (CC BY-NC-SA 4.0). Hornero's re-synthesis is MIT.*