All skills
deanpeters avatar

/executive-onboarding-playbook

@6a4fbf2

Plan a VP or CPO 30-60-90 day diagnostic onboarding path. Use when entering a new executive product role and avoiding premature change.

Use this Skill: https://skilld.dev/gh/deanpeters/product-manager-skills/executive-onboarding-playbook

This session only. Nothing lands on disk.

examplessample.md

≈822 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Executive Onboarding Playbook Example (30-60-90)

This example shows how a newly hired VP Product applies the playbook across the first 90 days.


Context

  • Company: B2B SaaS, Series B
  • Role: VP Product (first product executive hire)
  • Situation: Fast growth, noisy roadmap, unclear ownership between Product and Sales

Phase 0 (Before Day 1): Pre-Entry Checks

Inputs gathered before accepting

  • CEO expectations for first 90 days
  • Existing roadmap constraints and non-negotiables
  • Initial read on leadership team dynamics
  • Why the previous product leader left

Risk signals identified

  • CEO asks for "quick transformation" in first 30 days
  • CRO expects immediate roadmap commitments to close deals

Decision

Accept role with explicit alignment:

  • First 30 days are diagnostic.
  • Major org or process changes come after evidence review.

Phase 1 (Month 1): Diagnose

Actions

  1. 30 interviews across executives, PMs, engineering leads, and GTM partners.
  2. Document recurring themes and contradictions.
  3. Observe decision-making rituals (staff meetings, roadmap reviews, deal escalations).

Pattern signals

  • Stated strategy: "Move upmarket."
  • Unwritten strategy: close one reference enterprise logo in Q2.
  • People reality:
    • one PM is under-leveraged but strong in discovery
    • one PM is in a role mismatch (execution-heavy role, poor stakeholder management)

Month 1 output artifact

Organizational Assessment Memo:

  • top 5 strengths
  • top 5 failure risks
  • assumptions requiring validation in Month 2

Phase 2 (Month 2): Validate

Actions

  1. Reality-check findings with CEO, CRO, CFO, CTO.
  2. Test whether themes hold across independent data sources.
  3. Pressure-test people assessments with observed outcomes, not hearsay.

Validation outcomes

  • Enterprise reference-customer strategy confirmed by CEO and CRO.
  • Current roadmap over-invests in low-impact requests from loud internal stakeholders.
  • PM role mismatch confirmed by repeated cross-functional friction patterns.

Month 2 output artifact

Validated Hypotheses Deck:

  • what is true
  • what remains uncertain
  • what decisions can now be made with confidence

Phase 3 (Month 3): Act with Evidence

Actions

  1. Publish first Cascading Context Map for product org.
  2. Rebalance roadmap to support enterprise reference-customer motion.
  3. Start people decisions:
  • promote under-leveraged PM into a strategic initiative
  • move mismatch PM into a role better aligned to strengths
  1. Establish weekly executive alignment cadence with CRO, CFO, CMO.

Results by Day 90

  • Product org has clear priorities tied to business outcomes.
  • Executive peers understand product trade-offs earlier, with fewer late surprises.
  • People changes underway with clear rationale and lower political friction.

Anti-Pattern Contrast

What would have failed

  • Announcing org redesign in Week 2.
  • Standardizing all team artifacts before understanding why variation exists.
  • Taking executive narratives at face value without cross-checking.

Why the playbook prevented this

  • Diagnose first, validate second, act third.
  • Evidence precedes visible change.
  • Leadership credibility built through clarity and consistency.

Source: SKILL.md on GitHub

No alerts17d5 checks · Risk SAFE
  • Gen Agent Trust Hub17d

    This skill is a pure documentation and methodology framework for executive onboarding. It contains no executable code, no dangerous system commands, and no sensitive data access. It is entirely safe for use.

  • Socket17d

    No alerts

  • Snyk17d

    Risk: LOW · No issues

  • Runlayer6mo

    1/2 files flagged

  • ZeroLeaks5mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at 6a4fbf2. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last month.

Activeupdated 3 months ago
argument-hint
[role and company context]
type
workflow
theme
career-leadership
Other metadata
intent
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.
best_for
[
  "Starting a new VP or CPO role in the first 90 days",
  "Evaluating a CPO offer — what to ask before you accept",
  "Diagnosing an organization you've just inherited"
]
scenarios
[
  "I just accepted a VP of Product role starting next month — help me plan my first 90 days",
  "I'm evaluating a CPO offer and want to know what questions to ask the hiring CEO",
  "I'm two months into a new role and want to validate what I've learned before I start acting"
]
estimated_time
20-30 min

README badge

README badge for deanpeters/product-manager-skills/executive-onboarding-playbook