# Pm Exec Onboarding > A 30-60-90 day diagnostic playbook for VP and CPO leaders entering a new role. Use when the user asks about "starting a new VP or CPO role", "first 90 days as a product leader", "evaluating a CPO offer", or "diagnosing an organisation I've just joined". - Skill: `jiplet/pm-exec-onboarding` (Agent Skill) - Install (CLI): `npx skillmds@latest add jiplet/pm-exec-onboarding` - Raw SKILL.md: https://api.skillmd.com/api/skills/jiplet/pm-exec-onboarding/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: Jiplet (https://skillmd.com/u/jiplet) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/jiplet/pm-exec-onboarding --- ## 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. Three phases: **Diagnose** (Month 1) → **Validate** (Month 2) → **Act with Evidence** (Month 3). This is not a 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 organisation — before you're the person responsible for changing it. - Observe before diagnosing - Ask questions before making declarations - Understand how the steering connects to the rudder - Don't throw the big red switch — understand what it controls first Negotiate this upfront: tell your boss Month 1 is explicitly a learning phase. ### Unwritten Strategy At VP/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 - Tribal knowledge that long-tenured leaders treat as obvious Surface the unwritten layer through indirect questions: "What's the history here?" / "What did we try before that didn't work?" ### The Body of Evidence Every significant decision in Month 3+ should rest on evidence from Months 1-2: - Detailed notes from every diagnostic conversation - Patterns across multiple independent sources (not one vocal person) - Reality-checks with your manager and key peers ### People Assessment: Two Categories - **Diamonds in the rough** — Capable, undervalued people who haven't had a champion. Find them, give them scope. - **Strong people in wrong roles** — Strengths mismatched to current scope. Coach up, find another role, or part ways — all three better than leaving the mismatch. --- ## Application ### Phase 0: Before Day 1 (Evaluating the Role) Five questions to ask the hiring CEO: 1. "What are you expecting from the product organisation in the first 90 days? The first year?" 2. "Who are the all-stars on your product team, and why?" 3. "Who has gaps, and why?" 4. "What constraints are we working with that I should understand upfront?" 5. "What does success look like for this role at one year?" **Red flags:** - "You can't change the existing roadmap" — loss of authority before you start - "We need you to transform in six months" — sets you up to fail - Misalignment between CEO's talent assessment and what you hear elsewhere --- ### Phase 1: Diagnose (Month 1) **Objective:** Build the body of evidence. Understand reality, not the official version. **Step 1: Interview everyone** 30-min conversations with direct reports, cross-functional peers (CRO, CFO, CMO, Engineering), and a sample of PMs. Use these questions: - "What's working well that I should protect?" - "What's not working that you've hoped someone would fix?" - "What do I need to know that I won't hear in official briefings?" - "Who else should I talk to?" **Step 2: Let people find you** Some of the most valuable information comes from people who proactively seek out the new leader. Note what they say *and* that they came to you. **Step 3: Take detailed notes** Every conversation. Note content, context, who said it, their potential incentive, and whether you heard it from multiple independent sources. **Step 4: Resist action** When you see something obviously broken, resist fixing it. You don't yet know why it's broken or what it's connected to. Note it in your evidence log instead. **Deliverable:** A detailed notebook of organisational reality, not yet interpreted. --- ### Phase 2: Validate (Month 2) **Objective:** Surface patterns, challenge conclusions, identify people situations. **Step 1: Reality-check with your boss** "I'm hearing [X] from multiple people. This differs from what I understood coming in. Help me understand the history." **Step 2: Map the unwritten strategy** "What does the organisation actually optimise for when things get hard?" The answer is usually different from the mission statement. **Step 3: Complete people assessment** By end of Month 2, have a preliminary read on: - Diamonds in the rough (how to give them more scope) - Strong people in wrong roles (what the right conversation looks like) - People genuinely not coachable to the required level **Step 4: Identify 3-5 highest-leverage changes** Not a full transformation plan — three to five specific changes that would most improve effectiveness. **Deliverable:** An interpreted organisational assessment with people map and initial priorities. --- ### Phase 3: Act with Evidence (Month 3) **Objective:** Begin making decisions grounded in evidence. Introduce structure and direction, not transformation. **Step 1: Share your organisational assessment** Bring key findings to your boss and direct reports. Don't keep it private — transparency builds trust and surfaces disagreements before you act on them. **Step 2: Give your team context** Your team has been waiting for direction. Give them your best current translation of strategy, even if things above you are still ambiguous. Commit to refining it. **Step 3: Start the people conversations** - Diamonds in the rough: stretch assignment or expanded scope - People in wrong roles: direct, honest conversation about the mismatch and options - Exits: begin with honesty and care, not avoidance **Step 4: Build your executive alliance deliberately** Regular touchpoints with CRO, CFO, CMO. Ensure they understand product's priorities and the trade-offs being made. Don't let them be surprised. **Deliverable:** Shared organisational assessment, initial strategic direction, 3-5 active changes with clear rationale. --- ## Examples ### Good: Consultant Mindset Preventing a Costly Mistake New CPO notices a long-tenured PM who is resistant and unpopular with engineering. Impulsive response: performance plan in Month 1. Consultant response: investigates and discovers she's the only person who understands the legacy platform's architecture — and a previous CPO already tried to push her out, creating the defensive behaviour. Outcome: moved to technical product owner role by Month 3; delivery velocity improves. ### Bad: Acting Before Understanding New VP standardises three PMs' different roadmap formats in Week 3. Doesn't know each format exists because of specific stakeholder group requirements. Outcome: three stakeholder groups lose their views; Month 2 spent rebuilding goodwill. ### Good: Surfacing Unwritten Strategy VP hears "enterprise expansion" as stated priority. After 30 diagnostic conversations, realises the CEO has one specific enterprise customer in mind — a reference customer for the Series B — never mentioned in any written document. Surfaces it in Month 2 reality-check. Outcome: two product teams realigned around what actually matters. --- ## Common Pitfalls - **Performing action instead of building evidence:** Making structural changes in Month 1 to signal decisive leadership → reversals in Month 3 damage credibility more - **Staying in consultant mode too long:** Still gathering in Month 3, no visible decisions → organisational confidence erodes - **Trusting the loudest voice:** Only act on themes heard from 3+ unrelated independent sources - **Skipping the CEO interview:** The Phase 0 questions are not optional - **Ignoring executive dysfunction:** Map the alliances in Month 1 as carefully as you map the product portfolio ## References - Michael Watkins, *The First 90 Days* — Foundational reference for structured leadership transitions - Patrick Lencioni, *Five Dysfunctions of a Team* — Diagnostic for executive team dysfunction - Marty Cagan, *Empowered* — Organisational dynamics and product leadership at scale