---
name: executive-onboarding-playbook
description: Use when entering a new VP or CPO role — to structure the first 90 days as a diagnostic process that builds the evidence base before making structural, strategic, or people decisions.
role: product-manager
intent: |
  Structures a VP or CPO transition as three distinct phases — Diagnose,
  Validate, Act with Evidence — each with defined inputs, outputs, and
  decision gates. The cardinal error in senior product leadership transitions
  is compressing the diagnostic phase under social pressure to appear decisive;
  this playbook names that pressure explicitly and provides the methodology
  for resisting it without appearing passive.
type: workflow
theme: career-leadership
best_for:
  - A newly-appointed VP of Product or CPO planning their first 90 days
  - A product leader evaluating an executive offer and needing a pre-acceptance interview framework
  - A PM manager coaching a newly-landed director or VP through an onboarding that has gone off-track
scenarios:
  - "I just accepted a VP of Product role starting in three weeks — help me plan my first 90 days"
  - "I'm evaluating a CPO offer and want to know what questions I should be asking the CEO before I sign"
  - "I'm 6 weeks into a new VP role and I'm feeling pressure to announce a strategy — is that the right call?"
estimated_time: "Initial planning: 60-90 min. Execution spans 90 days; phase checkpoints add ~2h each."
---

# Executive onboarding playbook

> v0 draft. Framework grounded in Michael Watkins (*The First 90 Days*, 2003/2013). People-assessment concepts draw on Marty Cagan (*Empowered*, 2020) and Melissa Perri (*Escaping the Build Trap*, 2018). Executive-team-dysfunction framing references Patrick Lencioni (*Five Dysfunctions of a Team*, 2002). Cross-references: [`altitude-horizon-framework`](../altitude-horizon-framework/SKILL.md), [`director-readiness-advisor`](../director-readiness-advisor/SKILL.md), [`strategy-kernel`](../strategy-kernel/SKILL.md), [`cross-functional-orchestration`](../cross-functional-orchestration/SKILL.md), [`okrs`](../okrs/SKILL.md).

## Purpose

Run the first 90 days of a VP or CPO transition as a structured diagnostic — not an execution sprint. The playbook operates in three sequential phases: **Diagnose** (Month 1), **Validate** (Month 2), **Act with Evidence** (Month 3). Phases cannot be compressed without invalidating the evidence base; Month 3 decisions are defensible only if Month 1 and Month 2 were completed with discipline.

This is a diagnostic protocol, not an impression-management calendar. It does not optimize for looking decisive on Day 30. It optimizes for making durable decisions on Day 90.

## Key Concepts

### The diagnostic posture (Watkins)

Watkins (*The First 90 Days*, ch. 1-3) frames leadership transitions as a race between learning and the organizational expectation of action. The failure mode is acting before the learning is complete — not because action is bad, but because premature action builds on false premises and produces reversals that cost more credibility than patience would have.

In practice: enter the role with the orientation of an external consultant hired to assess the organization before changing it. Ask before declaring. Observe before diagnosing. Resist the instinct to fix what looks obviously broken — you don't yet know why it exists or what it's connected to.

Negotiate this posture explicitly with your manager before Day 1. "Month 1 is diagnostic" is a confident statement when made clearly, not a hedge. A hiring executive who responds badly to that statement is a signal worth noting before you accept.

### Unwritten strategy

At VP and CPO level, substantial strategic context lives outside written documents. It lives in the CEO's implicit priorities, in board dynamics, in the history of decisions that shaped current constraints, and in tribal knowledge that senior leaders treat as obvious. Written strategy is always incomplete.

Surfacing the unwritten layer is active work. The diagnostic questions that reach it are indirect: "What did we try before this that didn't work?" / "How did we end up with this approach?" / "What's the history here?" Direct questions about strategy often produce the official version; indirect questions about history surface the real one.

By the end of Month 2 you should be able to describe the gap between stated organizational priorities and observed organizational behavior. That gap is load-bearing diagnostic material.

### The evidence body

Every consequential decision in Month 3 and beyond must be traceable to a body of evidence — patterns observed across multiple independent sources in Months 1 and 2, not strong opinions from single informants. This is the mechanism that separates decisions from guesses, and that makes hard calls defensible to your team, your peers, and the board.

The evidence body has two quality tests:
1. **Independence** — does the pattern appear across sources with different incentives? A concern you hear from one vocal person is a data point. A concern you hear from five people who don't talk to each other is a finding.
2. **Triangulation** — have you reality-checked your emerging conclusions with your manager? Conclusions that survive triangulation with the person who hired you are more reliable than conclusions you've only tested internally.

### People assessment: two categories (Cagan, Perri)

Cagan (*Empowered*, ch. 4-5) distinguishes two distinct people situations that senior product leaders inherit and must resolve differently.

**Diamonds in the rough** — capable contributors who have been underutilized, overlooked, or placed in a scope that doesn't match their ceiling. They appear in the diagnostic phase as the people who give you the most unvarnished information, or who are named by peers as talented but underdeployed. These become early allies and leverage points; their elevation signals organizational intelligence to the rest of the team.

**Strength-role mismatch** — not weak performers, but people whose genuine strengths are mismatched to their current scope. Perri (*Escaping the Build Trap*, ch. 8) identifies this as endemic in organizations that grew fast or promoted on tenure rather than fit: the PM who excels at technical depth in an IC role, now managing a team that needs a coach. The right response is honest conversation about the mismatch and the options — not avoidance, and not a performance plan that treats a fit problem as a capability problem.

### Phase 0: Pre-acceptance diagnostic

Watkins (*The First 90 Days*, ch. 2) argues that the evaluation phase before accepting an executive role is itself diagnostic work — the organization is interviewing you, but you should be interviewing the organization. The quality of the answers you receive to five specific questions will tell you whether the role is winnable before you accept it.

**Five questions for the hiring CEO:**

1. "What does success look like for this role at 12 months — specifically?" — Vague answers ("transform the product culture") are a red flag. Specific answers ("two new enterprise logos, rebuilt discovery practice, measurable reduction in time-to-ship") are workable.
2. "Who are the strongest people on the product team, and what makes them strong?" — Surfaces the CEO's mental model and biases. Worth triangulating against your own observations.
3. "Who has gaps, and what do you think they are?" — A CEO who can name this clearly has thought about the team; one who can't is either conflict-avoidant or out of touch.
4. "What constraints will I be working with that aren't visible from the outside?" — Financial constraints, locked commitments, org politics, technical debt. Degrees of freedom matter more than scope on paper.
5. "What would need to be true at 90 days for you to feel confident I'm going to succeed in this role?" — Forces specificity and surfaces the CEO's real expectations vs. the job description's.

**Red flags that change the calculus:**
- "We need you to transform the organization in six months" — sets you up to fail by construction.
- "The existing roadmap is not changeable" — removes basic authority before Day 1.
- Meaningful dissonance between the CEO's talent assessment and what you hear in other conversations — tells you how much of reality filters up to the top.

## Application

### Phase 1: Diagnose (Month 1)

**Objective:** Build the evidence body. Understand organizational reality, not the official version.

**Step 1 — Schedule the diagnostic interview series.**
In your first week, book 30-minute conversations with: each direct report, cross-functional peers (CRO, CFO, CMO, engineering leadership), and a stratified sample of PMs in your organization. Run these throughout Month 1, not all in the first two weeks — later conversations benefit from context you've built in earlier ones.

Use a consistent question set:
- "What's working well here that I should understand and protect?"
- "What's been broken that you've hoped someone would address?"
- "What do you think I need to know that I probably won't hear in official briefings?"
- "Who else should I make sure to talk to?"

**Step 2 — Let information come to you.**
Some of the highest-signal input arrives unsolicited. People who seek out the new leader have an agenda — which is fine and expected. Surface the agenda, evaluate its validity, and note both what they're saying and the fact that they came. The pattern of who sought you out is itself diagnostic.

**Step 3 — Take structured notes; don't interpret yet.**
Every conversation: log the content, the source, that source's apparent incentives, and any cross-references to things you heard elsewhere. Month 1 note-taking is pattern-collection, not pattern-interpretation. Resist the urge to conclude.

A note-taking discipline that works: for each conversation, record three categories separately — (a) facts stated, (b) the source's apparent stake in how you receive those facts, (c) cross-references to other conversations. The third column is where patterns emerge; you cannot see it without the first two.

**Step 4 — Hold the action instinct.**
You will observe things in Month 1 that look obviously fixable. Note them and wait. You don't yet have the context to know why they exist, whether previous attempts to fix them failed, or what they're load-bearing for. Acting on incomplete diagnosis produces reversals.

Watkins' heuristic: imagine you've just entered a complex system you've never operated before. Before you touch anything, you want to understand what each component controls. The same logic applies to org structures, team compositions, reporting lines, and process rituals you've inherited. Understand what they're controlling first.

**Deliverable:** A structured diagnostic notebook — organizational observations recorded without yet being interpreted into decisions. Suggested format per conversation entry:

```
Date / Interviewee / Role:
Facts stated:
Source's apparent stake:
Cross-references to other conversations:
Items to probe further:
```

---

### Phase 2: Validate (Month 2)

**Objective:** Surface patterns, challenge emerging conclusions, complete the people assessment.

**Step 1 — Reality-check with your manager.**
Bring your emerging picture back to the person who hired you: "I'm hearing X from multiple people — this is different from what I understood coming in. Help me understand the history." This is not confrontational. It is how you separate signal from noise and build a shared baseline. If your manager is defensive about the reality you've observed, that's a signal too.

**Step 2 — Map the gap between stated and actual priorities.**
By mid-Month 2 you have enough observations to ask directly: "What does this organization actually optimize for when things get hard?" The answer is almost always different from the stated strategy, the mission statement, or the roadmap. Name the gap explicitly in your diagnostic notes. It is the material you'll work with in Phase 3.

Two reliable elicitation questions for the gap: "When two priorities are in conflict at this company, how does the decision actually get made?" and "What has been consistently deprioritized over the past year, even when it was nominally on the roadmap?" Answers to these reveal the real priority stack.

**Step 3 — Complete the people assessment.**
By end of Month 2, produce a preliminary read on:
- Who your diamonds in the rough are and what elevated scope would look like for each.
- Who is strong but in the wrong role, and what the honest conversation about that looks like.
- Who is genuinely not coachable to the level the organization needs — and what timeline and process is appropriate.

The people assessment is not punitive. It is the PM leader's version of Cagan's four-risk diagnosis applied to the team: where is the binding constraint on organizational capability?

**Step 4 — Identify three to five highest-leverage changes.**
Not a transformation plan. Three to five specific, bounded changes that would most improve the organization's ability to do its actual job. These become the Month 3 action set.

**Deliverable:** An interpreted organizational assessment. Suggested shape:

```
Organizational strengths (what to protect):
Organizational gaps (what needs to change):
Unwritten strategy vs. stated strategy — the gap:
People map:
  - Diamonds in the rough: [name / current role / proposed elevated scope]
  - Strength-role mismatches: [name / current role / mismatch / options]
  - Exits: [name / timeline / process]
Three to five highest-leverage changes (ranked):
```

---

### Phase 3: Act with Evidence (Month 3)

**Objective:** Begin making decisions. Not a transformation announcement — grounded actions with visible rationale.

**Step 1 — Share the assessment.**
Present your key findings to your manager and your direct reports: "Here's what I've learned about how this organization works, where it's strong, and where it needs to develop. Here's my initial plan for the next quarter." Transparency here serves two purposes: it builds trust by showing you did the work, and it surfaces disagreements before you act on them rather than after.

**Step 2 — Establish strategic direction.**
Use the organizational clarity from Phase 2 to provide directional context to your team, even if company-level strategy above you is still being formed. The [`altitude-horizon-framework`](../altitude-horizon-framework/SKILL.md) Cascading Context Map technique is the right instrument here — translating whatever strategic signal exists at the company level into something your team can act on at the product level. Your team has been context-starved during the diagnostic phase; give them your best current read and commit to refining it. See also [`strategy-kernel`](../strategy-kernel/SKILL.md) if the diagnostic has surfaced a named crux that needs a formal strategy artifact.

**Step 3 — Have the people conversations.**
Now that the evidence base is complete, act on the people assessment:
- Diamonds in the rough: stretch assignment, expanded scope, or explicit endorsement to the team.
- Strength-role mismatches: a direct, specific conversation about what you've observed, the options, and the timeline.
- Exits: begin with clarity and care. Avoidance at this stage turns a difficult conversation into a months-long drag on team performance.

**Step 4 — Build the executive alliance deliberately.**
By Month 3 you understand the cross-functional dynamics well enough to establish a deliberate operating rhythm with the functions product depends on most — engineering, sales/CRO, marketing/CMO, finance/CFO. The alliance is not about rapport; it is about ensuring those functions understand product's priorities and the trade-offs being made, before they are surprised by them. See [`cross-functional-orchestration`](../cross-functional-orchestration/SKILL.md) for the PM-as-integrator operating model.

Pair this with a first-pass OKR commitment for the quarter using your highest-leverage changes as the key results. See [`okrs`](../okrs/SKILL.md).

**Deliverable:** A shared organizational assessment; an initial strategic direction artifact; three to five active, evidence-grounded changes underway with explicit rationale. Each active change should have a named owner, a success signal, and a revisit date — the same structure [`cross-functional-orchestration`](../cross-functional-orchestration/SKILL.md) uses for decision-shaped recommendations.

---

## Examples

### Example 1 — Consultant posture preventing a costly people decision

**Context.** A new CPO inherits a team whose longest-tenured PM is visibly resistant, slow to ship, and unpopular with engineering. The obvious Month 1 response: performance management.

**What diagnostic patience reveals.** In Month 2, through cross-referencing multiple independent sources, the CPO learns: this PM is the only person on the team with deep knowledge of the legacy platform's data model. A previous CPO already attempted to push her out, creating the defensive posture. Her resistance is not unwillingness — it is self-protection after a previous leadership failure. Her actual strength is technical product depth, not stakeholder-facing PM work.

**Month 3 outcome.** She moves into a technical product owner role scoped to her actual strength. Engineering delivery improves because the platform knowledge is now formally positioned as a resource rather than an informal tax. The CPO avoids destroying an irreplaceable organizational capability by acting on 6-week observations rather than 6-day ones.

**What would have broken this.** Acting in Month 1 based on surface signals (resistance, unpopularity) rather than completing the diagnostic to understand root causes. The evidence of "diamond in the wrong role" only becomes visible through the full interview series and the people-assessment step in Phase 2.

---

### Example 2 — Surfacing unwritten strategy through indirect questioning

**Context.** A VP of Product joins a company whose stated priority is "enterprise expansion." The written strategy, the roadmap, and the Q1 OKRs all orient around enterprise acquisition. At 30 days, the VP cannot explain which specific enterprise segment, which specific capabilities, or what "success" means in enterprise terms.

**The diagnostic move.** In the Month 2 reality-check with the CEO, the VP asks: "When you picture what this business looks like at the end of this year — what does the portfolio look like specifically?" The CEO mentions one target customer by name. It is a reference customer that would unlock a Series B. It has never appeared in any written strategy document.

**What changes.** Two product teams' priorities shift toward the specific capabilities that matter to that customer. The "enterprise expansion" strategy becomes executable because the VP now has the actual target — not the category-level aspiration.

**The lesson.** The written strategy was real but incomplete. The unwritten layer — the specific reference-customer bet driving the CEO's mental model — was the load-bearing piece. It only surfaced through the indirect question about the future picture, not through a direct question about strategy.

---

### Example 3 — Premature standardization destroying goodwill

**Context.** A VP of Product notices in her second week that three PMs each use different formats for roadmap documentation. This looks like inconsistency. She standardizes them in Week 3.

**What she did not know.** Each format exists because of specific stakeholder requirements from three distinct internal audiences — each with different information needs and different levels of technical fluency. The "inconsistency" was intentional differentiation, not dysfunction.

**Outcome.** Three sets of stakeholders lose the views they relied on. The VP spends Month 2 rebuilding goodwill she spent three weeks burning. The standardization is reversed.

**The diagnostic question she should have asked first.** "Why does each team use a different format? What would break if they were unified?" That question, asked in Month 1, would have revealed the stakeholder differentiation and deferred the standardization to Month 3 — or avoided it entirely.

---

## Common Pitfalls

### Pitfall 1 — Performing action to signal leadership

**Symptom.** Making structural announcements, process changes, or strategy declarations in Month 1 to demonstrate decisive leadership. The announcement often feels necessary because the organization is visibly waiting for direction.

**Consequence.** Decisions built on 3-week observations rather than a 60-day evidence body produce reversals. Each reversal costs more credibility than the patience that would have prevented it. Watkins (*The First 90 Days*, ch. 4) identifies this as the single most common failure pattern in senior transitions.

**Fix.** Name the posture explicitly before Day 1: "I'm in diagnostic mode for the first 30 days. My first substantive recommendations will come in Month 2." Said with confidence to your manager and team, this reads as methodical, not passive. An executive who responds badly to it is a signal about the role's winnability.

---

### Pitfall 2 — Anchoring on the loudest voice

**Symptom.** Forming early organizational conclusions based on the most vocal, most accessible, or most persuasive person encountered in Month 1. The first strong personality you meet fills in the blanks your evidence body hasn't yet answered.

**Consequence.** You adopt a single source's organizational narrative as ground truth. When the rest of the organization provides contradictory context in Month 2, the early conclusions collapse — often loudly, because you've already repeated them.

**Fix.** Pattern-match across independent sources. A theme you've heard from three or more people with different incentives is a finding. A theme you've heard from one person, however compellingly argued, is a hypothesis pending validation. Do not act on single-source organizational claims.

---

### Pitfall 3 — Staying in diagnostic mode through Month 3

**Symptom.** Continued information-gathering in Month 3; no visible decisions, structural changes, or direction-setting. The organization is still waiting.

**Consequence.** Organizational confidence in the new leader erodes. Cagan (*Empowered*, ch. 3) observes that product teams are acutely sensitive to whether leadership has an opinion — extended ambiguity is demoralizing in ways that show up in attrition and disengagement. Your manager starts to wonder whether you can commit.

**Fix.** Month 3 is the action phase. You will not have complete information — no one ever does. Act on your best current evidence, name the evidence it rests on, and commit to learning from what follows. A provisional decision made transparently is a stronger signal than continued deference to uncertainty.

---

### Pitfall 4 — Skipping Phase 0 before accepting

**Symptom.** Taking the VP or CPO role without running the five-question pre-acceptance diagnostic with the hiring CEO.

**Consequence.** Walking into a locked roadmap, an impossible timeline, or a CEO whose mental model of the team is so far from reality that Month 1 is consumed managing their misperceptions. No role is worth accepting on hope alone at the VP level.

**Fix.** The Phase 0 questions are not optional and are not impolite. A hiring CEO who responds defensively to "what would success look like at 12 months, specifically?" is answering the question. Red flags uncovered before accepting are survivable; red flags discovered on Day 30 are not.

---

### Pitfall 5 — Treating executive team dynamics as mature by default

**Symptom.** Assuming the executive staff operates with transparency, shared goals, and good-faith information-sharing. Treating the org chart as a model of how power and information actually flow.

**Consequence.** Being blindsided by alliances, information hoarding, and personal agendas that were operating long before you arrived. Lencioni (*Five Dysfunctions of a Team*, ch. 1-2) observes that leadership teams are often the most dysfunctional teams in the building — higher stakes produce more politics, not less.

**Fix.** Map the executive dynamics in Month 1 with the same rigor you apply to the product portfolio. Who has informal authority that the org chart doesn't reflect? Who controls information flow to the CEO? What are the standing tensions between functions? None of this is unusual; all of it matters for your Month 3 decisions.

---

### Pitfall 6 — Conflating people assessment with performance management

**Symptom.** Framing the Month 2 people assessment as a performance-management exercise — producing ratings, putting people on notice, or treating the assessment as a precursor to exits by default.

**Consequence.** The people assessment is a tool for matching capability to scope and identifying leverage. Used as a performance-management frame in Month 2, it signals threat before you have the evidence base to make credible calls, and it drives away the diamonds in the rough who have the most options and will leave first.

**Fix.** The people assessment has two productive outputs: elevated scope for the under-deployed, and honest conversations about fit for the mismatched. Exits are one possible outcome of the second category, not the purpose of the exercise. Cagan's four-risk model applied to the team: diagnose the binding constraint on organizational capability before deciding what to do about it.

---

## References

- **Michael Watkins** — *The First 90 Days: Proven Strategies for Getting Up to Speed Faster and Smarter* (2003, updated 2013, Harvard Business Review Press). The foundational reference for structured leadership transitions. The three-phase structure (Diagnose / Validate / Act) is Hornero's synthesis of Watkins' STARS model and his accelerate-learning / early-wins framing. The pre-acceptance diagnostic in Phase 0 is derived from Watkins' negotiate-success principle. See ch. 1-4 for the core methodology and ch. 9-10 for the executive-team dynamics framing.
- **Marty Cagan** — *Empowered: Ordinary People, Extraordinary Products* (2020, with Chris Jones, Wiley). The people-assessment categories (diamonds in the rough; strength-role mismatch) trace to Cagan's treatment of product leadership and team composition in ch. 3-5. The four-risk diagnostic model (*Inspired*, 2017) is used in Phase 2's people-assessment step as a structured frame for identifying where organizational capability is constrained.
- **Melissa Perri** — *Escaping the Build Trap: How Effective Product Management Creates Real Value* (2018, O'Reilly). The strength-role-mismatch pattern — specifically fast-growth promotion dynamics producing PMs mismatched to scope — is a direct application of Perri's build-trap diagnosis to organizational structure. See ch. 8 on team structure and the product leader's role in resolving inherited mismatches.
- **Patrick Lencioni** — *The Five Dysfunctions of a Team: A Leadership Fable* (2002, Jossey-Bass). Pitfall 5 (executive team dysfunction) draws on Lencioni's model: trust, conflict, commitment, accountability, and results as cascading organizational deficits. Applied specifically here to executive-team dynamics in Month 1 mapping.
- **Related Hornero skills:**
  - [`altitude-horizon-framework`](../altitude-horizon-framework/SKILL.md) — The Cascading Context Map technique referenced in Phase 3 Step 2. Use when translating ambiguous company-level strategy into actionable team-level direction. The altitude/horizon framing is the VP/CPO's primary instrument for Phase 3 direction-setting.
  - [`director-readiness-advisor`](../director-readiness-advisor/SKILL.md) — The director-level transition equivalent. Use when coaching a newly-landed director through their own onboarding, or when a VP is diagnosing a direct report's transition.
  - [`strategy-kernel`](../strategy-kernel/SKILL.md) — When Phase 2 diagnostics surface a named crux, the strategy kernel is the artifact that formalizes the diagnosis → guiding policy → coherent actions chain. Phase 3 direction-setting should produce a kernel if the VP/CPO has identified a clear binding constraint on organizational strategy.
  - [`cross-functional-orchestration`](../cross-functional-orchestration/SKILL.md) — The PM-as-integrator operating model for Phase 3 executive alliance-building. The orchestration skill provides the step-by-step framework for the CRO/CFO/CMO coordination cadence referenced in Phase 3 Step 4.
  - [`okrs`](../okrs/SKILL.md) — The quarterly outcome-commitment layer. Phase 3 deliverables should culminate in a first-pass OKR set grounded in the three-to-five highest-leverage changes identified in Phase 2.

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