executive-onboarding-playbook

Purpose

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.

This playbook runs in three phases: Diagnose (Month 1), Validate (Month 2), Act with Evidence (Month 3). Each phase builds on the last. 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.

What this means in practice:

• 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" is more powerful than "here's what we're going to do differently."
• Understand how the steering connects to the rudder. In any organization, there are systems and relationships that look one way on paper and work completely differently in practice. Map that reality before you touch anything.
• Don't throw the big red switch. If you walked into a power plant you'd never operated before and saw a large red switch, you probably wouldn't throw it. The same logic applies to org structures, processes, reporting lines, and team compositions you've inherited. Understand what they control first.

Negotiate this upfront: tell your boss and peers that Month 1 is explicitly a learning phase. Set the expectation that your first major recommendations will come in Month 2. Executives who've been through transitions will respect this; executives who want action in Week 1 are a signal worth noting.

Unwritten Strategy

At VP and CPO level, significant strategy is never fully written down. It lives in:

• The CEO's head, shaped by conversations you weren't in
• Board meeting dynamics and investor preferences
• Last night's executive dinner
• Off-the-record conversations between founders
• Tribal knowledge that long-tenured leaders treat as obvious

This isn't dysfunction — it's how every organization works at the executive level. Treating written strategy as complete strategy will get you into trouble fast.

Your job in the first 90 days is to surface the unwritten layer. How:

• Ask indirect questions: "What's the history here?" / "How did we end up with this approach?" / "What did we try before that didn't work?"
• Let information find you. People who want to shape the new leader's perspective will seek you out. Take those meetings. Take notes.
• Reality-check with your boss: "Here's what I'm hearing from the organization. This is different from what you told me. Help me understand." This is not confrontational — it's how you triangulate toward the truth.

The Body of Evidence

Every significant decision you make in Month 3 and beyond should rest on a body of evidence collected in Months 1 and 2. This means:

• Detailed notes from every diagnostic conversation
• Patterns noted across multiple independent sources (not just one vocal person)
• Reality-checks completed with your manager and key peers
• A clear picture of what's working, what's broken, and why

The body of evidence is what separates confident decisions from guesses. It's also what makes hard decisions defensible — to your team, to your peers, and to the board.

People Assessment: Two Categories

Two distinct people situations require different responses:

Diamonds in the rough — Capable, undervalued people who haven't had a champion. They exist in almost every organization. You'll find them in Months 1-2 by listening for: "She's really talented but nobody gives her the hard problems" or noticing who gives you the most useful, unvarnished information in your diagnostic interviews. These people become critical early allies.

Strong people in wrong roles — Not weak performers; people whose strengths are mismatched to their current scope. This is more common in organizations that grew fast, went through acquisitions, or promoted based on tenure. A former sales rep who became a PM because they knew the product. A brilliant individual contributor managing a team that needs a coach. These situations require honest, compassionate conversations — coach up if they're coachable, find them another role, or part ways. All three outcomes are better than leaving the mismatch in place.

Phase 0: Before Day 1

If you're evaluating whether to take the role, use this phase to interview the organization before it interviews you.

Five questions to probe with the hiring CEO:

1. "What are you expecting from the product organization in the first 90 days? The first year?" — Surfaces unrealistic transformation timelines early. Red flag: "I expect the roadmap to be fully overhauled by Q2."

2. "Who are the all-stars on your product team, and why?" — Reveals the CEO's perceptions and biases. They're often wrong, but knowing their mental model matters.

3. "Who has gaps, and why?" — What does the CEO believe the org's weakness is? Is it accurate?

4. "What constraints are we working with that I should understand upfront?" — Financial, organizational, market. Understand your actual degrees of freedom before you accept.

5. "What does success look like for this role at one year?" — Force specificity. Vague answers ("transformed the product culture") are red flags. Specific answers ("85% on-time delivery, two new enterprise accounts, one rebuilt team") are workable.

Red flags that change the calculus:

• "You can't change the existing product roadmap" — loss of basic authority before you start
• "We need you to transform the organization in six months" — sets you up to fail
• Misalignment between CEO's talent assessment and what you learn elsewhere in conversations

Application

Phase 1: Diagnose (Month 1)

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

Step 1: Interview everyone Schedule 30-minute conversations with your direct reports, key cross-functional peers (CRO, CFO, CMO, Engineering leadership), and a sample of the PMs in your organization. The question set is simple:

• "What's working well that I should understand and protect?"
• "What's not working that you've been hoping someone would fix?"
• "What do you think I need to know that I probably won't hear in official briefings?"
• "Who are the people in this organization I should make sure to talk to?"

Step 2: Let people find you Don't do all the seeking. Some of the most valuable information comes from people who proactively schedule time with the new leader. They have an agenda — surface it, evaluate it, and note the signal (both in what they say and in that they came to you at all).

Step 3: Take detailed notes Every conversation. Note not just content but context: who said it, what their incentive might be, whether you heard the same thing from multiple independent sources. Patterns that appear across multiple conversations are much more reliable than strong opinions from single sources.

Step 4: Resist action When you see something obviously broken in Month 1, your instinct will be to fix it. Resist. You don't yet have the context to know why it's broken, whether previous attempts to fix it failed, or what it's connected to. Note it in your evidence log instead.

Deliverable: A detailed notebook of organizational reality, not yet interpreted.

Phase 2: Validate (Month 2)

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

Step 1: Reality-check with your boss Take your emerging pict