Product Ops Onboarding Checklist (30/60/90)
30/60/90-day onboarding plan for a new product ops hire, from listening tour to first deliverable.
What this template covers
A new PO hire without a structured onboarding wastes 60 days figuring out who owns what. This 30/60/90 plan sequences the listening tour (weeks 1-3), diagnostic (weeks 4-6), prioritization (weeks 7-9), and first deliverable (weeks 10-13). Includes a list of 22 people to meet, 12 documents to read, and 6 rituals to observe before proposing any changes.
The template
# Product Ops 30/60/90 Onboarding Plan **New hire:** ___________ **Manager:** ___________ **Start date:** YYYY-MM-DD **90-day review:** YYYY-MM-DD > The first 90 days are for **listening, diagnosing, and earning trust**. Resist the urge to ship anything substantive before day 60. --- ## Days 1-30 — Listening tour ### People to meet (22 conversations) - [ ] CEO — strategic context (45 min) - [ ] CPO — what does success look like for this hire (60 min) - [ ] VP Engineering — current product-engineering operating model (45 min) - [ ] VP Design — design's pain points with the operating system (45 min) - [ ] VP Sales — what does sales need from product to win (45 min) - [ ] VP Marketing — current product marketing handoff (45 min) - [ ] VP Customer Success — top 5 customer themes (45 min) - [ ] VP Support — what's eating support's bandwidth (30 min) - [ ] Head of Data — instrumentation maturity (30 min) - [ ] Head of Finance — budget and headcount realities (30 min) - [ ] Each PM (1:1) — what's working, what's broken (30 min each) - [ ] Two engineering managers — view from delivery (30 min each) - [ ] Two designers — view from craft (30 min each) - [ ] One customer (intro from CSM) — the user's voice (30 min) ### Documents to read (12 documents) - [ ] Last two quarterly planning decks - [ ] Most recent board update (product section) - [ ] Last two post-launch retros - [ ] Last 30 days of customer interview notes - [ ] Top 5 inbound complaints from support tickets - [ ] Current roadmap document - [ ] Current OKR document - [ ] Last engagement survey results - [ ] Career ladder for product and PO - [ ] Tool stack inventory + cost - [ ] Existing PO playbook (if any) - [ ] Org chart, current and prior ### Rituals to observe (6 rituals) - [ ] Weekly product team standup - [ ] Sprint review or demo - [ ] Sprint retro - [ ] Quarterly planning kickoff (if it lands in the window) - [ ] Customer call (sit in, do not speak) - [ ] Exec staff meeting (if invited) **Day 30 deliverable:** A written "what I heard" memo, 1-2 pages, shared with manager only. --- ## Days 31-60 — Diagnostic - [ ] Synthesize findings from listening tour into 5-7 themes - [ ] Write a diagnostic memo (3-5 pages) covering: - The product operating system as it exists today - The top 3 friction points and their impact - The top 2 opportunities (low-effort, high-leverage) - What you propose to focus on for the next 60 days - [ ] Review the diagnostic with manager - [ ] Review with CPO - [ ] Pressure-test with two PMs and two functional VPs - [ ] Revise based on feedback - [ ] Publish to a small audience (manager, CPO, peers) **Day 60 deliverable:** A revised, approved 60-day work plan with one named first deliverable. --- ## Days 61-90 — First deliverable Pick **one** thing. Ship it cleanly. The goal is credibility, not scope. Examples of good first deliverables: - Stand up the weekly feedback triage ritual - Publish a single product health dashboard - Run a clean quarterly planning offsite - Replace the old roadmap format with a Three-Horizon view - [ ] Scope the deliverable in writing (one-pager) - [ ] Get sign-off from your manager and the affected team - [ ] Ship it - [ ] Run a retro on it with the affected team - [ ] Document the work in a permanent location - [ ] Present learnings + next 90 days at the day-90 review **Day 90 deliverable:** Shipped artifact + a written 90-day retro. --- ## Manager check-ins | Day | Format | Topic | | --- | --- | --- | | 7 | 30 min | First-week impressions, immediate blockers | | 14 | 30 min | Listening tour progress, calibration | | 30 | 60 min | Day-30 memo review | | 45 | 30 min | Diagnostic shaping | | 60 | 60 min | Day-60 work plan sign-off | | 75 | 30 min | First-deliverable check-in | | 90 | 90 min | Day-90 review, plan for the next quarter |
When to use it
- First 90 days for a new PO hire
- Manager onboarding plan
- Self-directed ramp for a lateral move
- Reboot after a failed ramp
How to adapt it
Copy the template above into Google Docs, Sheets, Notion, Airtable, or Confluence. Keep the section order intact, later sections often reference data entered earlier. Replace the example values with your own, then review quarterly and re-circulate to stakeholders.
Related templates
Templates are drafted from public Product Operations research and reviewed by practicing PO leaders. Free to copy and modify for internal company use.
Frequently Asked Questions
A new PO hire without a structured onboarding wastes 60 days figuring out who owns what. This 30/60/90 plan sequences the listening tour (weeks 1-3), diagnostic (weeks 4-6), prioritization (weeks 7-9), and first deliverable (weeks 10-13). Includes a list of 22 people to meet, 12 documents to read, and 6 rituals to observe before proposing any changes.
This template is written for Product Operations teams at software companies sized 50-500 employees. Common use cases include: First 90 days for a new PO hire; Manager onboarding plan; Self-directed ramp for a lateral move.
The template is designed as a Checklist. Copy the structure directly into your own Google Docs, Sheets, Notion, or Airtable workspace. No attribution is required for internal company use.
Start with the section structure exactly as published, then modify field names to match your organization's vocabulary. Most teams complete a first pass in 30 minutes and a polished version within one working week.