VP/CPO Executive Onboarding Playbook (30-60-90)

# Executive Onboarding Playbook (VP/CPO 30-60-90)

Structure the first 90 days of a VP or CPO transition as a **diagnostic process**, not an execution sprint. The single most common failure in senior product leadership transitions is acting before understanding — changing structures, replacing people, or announcing strategy before building the evidence base that makes those decisions defensible.

Three phases: **Diagnose** (Month 1), **Validate** (Month 2), **Act with Evidence** (Month 3). Skipping phases doesn't accelerate results — it guarantees expensive reversals.

This is not a 100-day plan for impressing your new boss. It's a diagnostic protocol for making durable decisions.

## Key Concepts

### The Consultant Mindset

Enter every new VP/CPO role as if you're an external consultant hired to assess the organization — before you're the person responsible for changing it.

- **Observe before diagnosing.** Don't form opinions in the first week based on first impressions.
- **Ask questions before making declarations.** "Help me understand how this works" > "here's what we're going to do differently."
- **Understand how the steering connects to the rudder.** Systems and relationships look one way on paper and work completely differently in practice.
- **Don't throw the big red switch.** Understand what inherited structures control before you touch them.

Negotiate this upfront: tell your boss and peers Month 1 is explicitly a learning phase. Executives who want action in Week 1 are a signal worth noting.

### Unwritten Strategy

At VP/CPO level, significant strategy is never fully written down. It lives in:
- The CEO's head
- Board meeting dynamics and investor preferences
- Last night's executive dinner
- Off-the-record conversations between founders
- Tribal knowledge long-tenured leaders treat as obvious

Surface it by asking indirect questions ("What's the history here?"), letting information find you, and reality-checking with your boss ("Here's what I'm hearing; help me understand").

### The Body of Evidence

Every significant Month 3+ decision should rest on a body of evidence collected in Months 1-2:
- Detailed notes from every diagnostic conversation
- Patterns noted across multiple independent sources
- Reality-checks completed with manager and key peers
- Clear picture of what's working, what's broken, and why

The body of evidence is what separates confident decisions from guesses — and makes hard decisions defensible.

### People Assessment: Two Categories

**Diamonds in the rough** — Capable, undervalued people who haven't had a champion. Find them in Months 1-2 by listening for "She's really talented but nobody gives her the hard problems." These become critical early allies.

**Strong people in wrong roles** — Strengths mismatched to current scope. A former sales rep who became a PM because they knew the product. A brilliant IC managing a team that needs a coach. Requires honest, compassionate conversations — coach up, find another role, or part ways. All three are better than leaving the mismatch.

---

## Phase 0: Before Day 1 (Evaluating the Offer)

**Five questions to probe with the hiring CEO:**

1. "What are you expecting from product in the first 90 days? The first year?" — Red flag: "roadmap fully overhauled by Q2"
2. "Who are the all-stars on your product team, and why?" — Reveals CEO's perceptions and biases
3. "Who has gaps, and why?" — What does the CEO believe the org's weakness is? Is it accurate?
4. "What constraints should I understand upfront?" — Financial, organizational, market — know your degrees of freedom
5. "What does success look like at one year?" — Force specificity. Vague = red flag. Specific = workable.

**Red flags that change the calculus:**
- "You can't change the existing product roadmap" — loss of basic authority before you start
- "Transform the organization in six months" — sets you up to fail
- Misalignment between CEO's talent assessment and what you learn elsewhere

---

## Phase 1: Diagnose (Month 1)

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

### Activities

1. **Interview everyone** — 30-minute conversations with direct reports, cross-functional peers (CRO, CFO, CMO, Engineering leadership), sample of PMs
   - "What's working well that I should protect?"
   - "What's not working that you've been hoping someone would fix?"
   - "What do I need to know that I probably won't hear in official briefings?"
   - "Who should I make sure to talk to?"

2. **Let people find you** — Valuable info comes from people who proactively schedule time. They have an agenda — surface it, evaluate it, note the signal.

3. **Take detailed notes** — Every conversation. Note content, context, incentives, and whether you heard it from multiple independent sources.

4. **Resist action** — When you see something obviously broken in Month 1, your instinct will be to fix it. Resist. Note it in your evidence log instead.

**Deliverable:** Detailed notebook of organizational reality, not yet interpreted.

---

## Phase 2: Validate (Month 2)

**Objective:** Surface patterns, challenge emerging conclusions, identify people situations.

### Activities

1. **Reality-check with your boss** — "I'm hearing [X] from multiple people. This is different from what I understood. Help me understand the history."

2. **Map the unwritten strategy** — Ask directly: "What does the organization actually optimize for when things get hard?" Usually different from the mission statement.

3. **Complete people assessment**:
   - Diamonds in the rough → give them more scope
   - Strong but wrong role → right conversation + options
   - Genuinely not coachable → appropriate timeline

4. **Identify 3-5 highest-leverage changes** — Not a full transformation plan. Three to five specific changes for Month 3.

**Deliverable:** Interpreted organizational assessment with people map and initial strategic priorities.

---

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

**Objective:** Begin making decisions grounded in evidence. Introduce structure and direction, not transformation.

### Activities

1. **Share your organizational assessment** — "Here's what I've learned. Here's my initial plan for next quarter." Transparency builds trust and surfaces disagreements before you act.

2. **Run your first Cascading Context Map** — Give your team your best current translation of strategy, even if company strategy above is still ambiguous. (See `altitude-horizon-framework`.)

3. **Start the people conversations** — Diamonds get stretch assignments. Wrong-role people get honest conversations and options. Exits begin with honesty and care.

4. **Build your executive alliance deliberately** — Weekly touchpoints with CRO, CFO, CMO so they understand product's priorities and trade-offs. Don't wait for them to be surprised.

**Deliverable:** Shared organizational assessment, initial strategic direction, 3-5 active changes underway with clear rationale.

---

## Common Pitfalls

1. **Performing action instead of building evidence** — Announcements in Month 1 to signal decisive leadership → Month 3 reversals damage credibility more than Month 1 patience would have.
2. **Staying in consultant mode too long** — Still gathering info in Month 3 → org confidence erodes. Act on best current evidence and commit to learning.
3. **Trusting the loudest voice** — Early opinions based on most vocal Month 1 conversations → single-source narratives collapse. Pattern-match across 3+ independent sources.
4. **Skipping the CEO interview before accepting** — Locked roadmap, impossible timeline, wrong talent model → first 6 months managing misperceptions. The Phase 0 questions are not optional.
5. **Ignoring executive dysfunction** — Assuming staff meetings are mature and politics-free → blindsided by alliances and agendas. Expect dysfunction; integrity gets tested more at higher levels.

## Good / Bad Examples

**Good — Consultant mindset prevents costly mistake:** New CPO notices longest-tenured PM is resistant/slow. Impulse: PIP in Month 1. Consultant response: discovers in Month 2 she's the only one who understands the legacy platform's architecture; strong but in wrong role. Moves her to technical product owner. Engineering velocity improves.

**Bad — Acting before understanding:** New VP hears in Week 2 that three PMs use different roadmap formats. Standardizes them in Week 3. Didn't know each format existed for specific stakeholder requirements. Spends Month 2 rebuilding goodwill.

**Good — Surfacing unwritten strategy:** VP joins company whose stated priority is "enterprise expansion." After 30 diagnostic conversations, realizes the CEO has a specific reference customer in mind (unlocks Series B) never mentioned in any written doc. Surfaces in Month 2 reality-check. Realigns two teams around that customer's capabilities.

## References

- `vp-cpo-readiness-advisor` — Interactive advisor for all four VP/CPO transition situations
- `altitude-horizon-framework` — The Cascading Context Map technique referenced in Phase 3
- Michael Watkins, *The First 90 Days*
- Patrick Lencioni, *Five Dysfunctions of a Team*
- Marty Cagan, *Empowered*
- *The Product Porch*, Episode 43 — "Becoming a VP & CPO: Leading Product at the Executive Level (Part 2)"