
Executive Onboarding Playbook
Plan a VP or CPO first 90 days as diagnosis—relationships, evidence, and boundaries—before structural or strategy changes.
Overview
executive-onboarding-playbook is an agent skill most often used in Validate (also Build, Operate) that plans a VP or CPO 30-60-90 diagnostic onboarding before major org or strategy moves.
Install
npx skills add https://github.com/deanpeters/product-manager-skills --skill executive-onboarding-playbookWhat is this skill?
- Three-phase path: Diagnose, then Learn, then Act—explicitly anti premature change
- Use when starting VP/CPO, evaluating a CPO offer, or validating learnings at ~60 days
- Estimated 20–30 minutes to structure the playbook conversation
- Focus on evidence base before replacing people, restructuring teams, or announcing strategy
- Workflow type with career-leadership theme for executive transitions
- Estimated time 20–30 min
- Three phases: Diagnose, Learn, Act
Adoption & trust: 1.1k installs on skills.sh; 5k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You just landed—or are considering—a senior product executive role and feel pressure to change the team or roadmap before you understand how the business really works.
Who is it for?
New VP/CPOs, founders hiring their first product executive, or leaders at ~60 days who want to validate assumptions before acting.
Skip if: IC engineers fixing lint, pure roadmap prioritization without a leadership transition, or roles with zero people or stakeholder scope.
When should I use this skill?
Entering a new VP or CPO product role, evaluating a CPO offer, or validating executive learnings before acting.
What do I get? / Deliverables
You leave with a phased 90-day diagnostic plan, CEO interview questions, and explicit gates before structural or strategy commitments.
- 30-60-90 diagnostic onboarding plan
- Stakeholder and evidence-gathering checklist
- Decision gates before org or strategy changes
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Entering a senior product role is a commitment decision; Validate scope is where you define what you will learn before you rebuild the roadmap. Scope covers role boundaries, stakeholder map, and what 'success' means in 90 days without premature reorgs.
Where it fits
Draft CEO questions and success metrics before signing a CPO offer letter.
Map Diagnose-phase listening tours before changing squad structure in month one.
At day 60, validate learnings against the playbook before announcing a new portfolio strategy.
How it compares
Executive transition playbook—not a sprint planning or user-story writing skill.
Common Questions / FAQ
Who is executive-onboarding-playbook for?
Product executives and founder-operators entering or evaluating VP/CPO roles who need a structured 90-day diagnostic instead of day-one reorgs.
When should I use executive-onboarding-playbook?
In Validate scope when negotiating or accepting a CPO offer; in Build pm when inheriting a product org; in Operate iterate when stabilizing leadership after a messy transition.
Is executive-onboarding-playbook safe to install?
It is advisory planning content with no infra access—review the Security Audits panel on this page like any third-party skill.
SKILL.md
READMESKILL.md - 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