executive-onboarding-playbook
Plan a VP or CPO 30-60-90 day diagnostic onboarding path. Use when entering a new executive product role and avoiding premature change.
Executive Onboarding Diagnostic Playbook: A 30-60-90-Day Plan for VPs/CPOs (executive-onboarding-playbook)
Skill Overview
The Executive Onboarding Diagnostic Playbook (executive-onboarding-playbook) helps a newly appointed VP of Product or CPO structure their first 90 days into three phases—“diagnose → validate → act on evidence.” It prioritizes building an evidence base before making decisions, helping avoid “acting before understanding,” the most common failure in senior product leadership transitions.
Applicable Scenarios
- You have just accepted a VP of Product/CPO offer and have a few weeks before starting: use it to plan your complete 30-60-90-day path, and to conduct a five-question assessment of the hiring CEO before accepting the offer.
- You are in your first or second month in the new role: use it to conduct organizational diagnostic interviews, reality-check with your manager, map the unwritten strategy, and complete a talent assessment.
- You have been in the role for about two months and are preparing to take action: use it to identify the 3–5 highest-leverage changes from the evidence and smoothly begin the first round of talent conversations.
Core Functions
- Three-Phase Diagnostic Process: Breaks the first 90 days into “diagnose (Month 1) → validate (Month 2) → act on evidence (Month 3).” Each phase includes concrete steps, interview question checklists, and clearly defined deliverables, systematically preventing premature change. The playbook emphasizes that skipping phases will not accelerate results; it will only guarantee expensive rework.
- Phase 0 Offer Assessment: For users still evaluating an offer, provides five probing questions to ask the hiring CEO—covering expectations for the first 90 days and the first year, the CEO’s assessment of the team’s talent, hidden constraints, and the definition of success—along with a list of red flags, such as “the existing roadmap cannot be changed” or “complete the organizational transformation within six months.” These help determine whether the role is worth accepting.
- Two-Category Talent Assessment: Classifies people in the organization into two groups for separate treatment: “undiscovered high-potential talent” (capable people who have not received sufficient recognition and may be ready for greater responsibility) and “misaligned high performers” (capable people whose roles are a poor fit and who may need coaching, reassignment, or a dignified exit). This helps avoid eliminating critical talent based on first impressions.
Frequently Asked Questions
How is this different from a traditional 100-day “impress-the-boss” plan?
The goal of a traditional 100-day plan is to demonstrate results quickly. This playbook defines the first 90 days as a diagnostic process, with the core deliverable being an “evidence system for organizational reality.” Every important decision in Month 3 is grounded in interview notes, patterns cross-validated across multiple sources in Months 1 and 2, and shared understanding established with the manager. The playbook is positioned as “a diagnostic protocol for making durable decisions,” rather than a performance staged for the new boss.
I haven’t started yet. Can I still use it?
Yes. Phase 0 is designed specifically for the offer-evaluation stage. It provides five questions to ask the hiring CEO—about expectations for the product organization in the first 90 days and first year, the team’s stars and weak links, constraints you should understand in advance, and what success should look like after one year—along with red flags that should change your decision. The playbook explicitly recommends walking away from the offer when the answers reveal fundamental misalignment.
What if I see an obvious problem in the first month? Am I still not supposed to fix it immediately?
The playbook recommends documenting rather than immediately fixing it. Until you understand why the problem exists, who has previously tried to fix it, and which systems it is connected to, you should not act—just as you would not enter an unfamiliar power plant and immediately pull the largest red switch. All “obviously broken things” should first go into an evidence log. Only after validating them through multiple independent sources in Month 2 and conducting a reality-check with your manager should you act on the evidence in Month 3. At the same time, the playbook draws a clear boundary: you cannot remain in consultant mode forever; Month 3 is the action phase.