Skip to content

borghei/Claude-Skills / project-management/career/pm-onboarding

pm-onboarding

Verified

Builds a new PM's 30-60-90 day plan from a situation diagnosis: stakeholder map, 1:1 questions, early wins and a first PRD. Use when starting a PM job, moving to a new team, or taking on new scope.

assets/30_60_90_plan.md

View on GitHub
# 30-60-90 Day Plan

**Your name:** ___________
**Role:** ___________
**Manager:** ___________
**Start date:** ___________
**Day 90 target date:** ___________

---

## Pre-start (week before day 1)

- [ ] Read company about page, recent blog posts, last 2 quarterly earnings (if public)
- [ ] Read product docs, public release notes, support center
- [ ] Use the product as a customer for at least 2 hours
- [ ] 30-minute call with manager to confirm day-1 logistics
- [ ] Identify your day-1 buddy (often arranged by HR)

---

## Days 1-30: Learn

**Goal:** Build context. No major decisions.

### Week 1: Logistics + manager alignment

- [ ] Day 1: Get laptop, access, calendar set up
- [ ] Day 2: 1:1 with manager — discuss expectations, communication style, first-30-day plan
- [ ] Day 3-5: Intro 1:1s with immediate team (engineers, designers)
- [ ] End of week: Send "what to expect from me" note to the team
- [ ] **Output:** 90-day plan draft shared with manager

### Week 2: Customer immersion

- [ ] Read all existing customer research
- [ ] Listen to 5-10 sales / support / customer success calls
- [ ] Read top 50 support tickets in your area
- [ ] **Output:** Top-5 customer pain hypotheses

### Week 3: Product immersion

- [ ] Use the product daily as a customer
- [ ] Read existing PRDs, design docs, RFCs
- [ ] Map the metrics tree for your area
- [ ] **Output:** Product-area map + baseline metrics dashboard

### Week 4: Team immersion + STARS diagnosis

- [ ] Complete 1:1s with every engineer and designer in immediate team
- [ ] Tier-2 stakeholder 1:1s started (sales, support, marketing leads)
- [ ] Skip-level 1:1 booked or held
- [ ] **Output:** "What I'm learning" memo to manager (1 page)
- [ ] **Output:** STARS diagnosis draft

---

## Days 31-60: Plan

**Goal:** Build a point of view. Identify early wins.

### Week 5: Deepen customer evidence

- [ ] Interview 3-5 customers yourself
- [ ] Synthesize using the interview-synthesis discipline
- [ ] **Output:** Customer insight memo

### Week 6: Competitive + market scan

- [ ] Map 3-5 competitors with feature / positioning
- [ ] Identify your area's competitive moat or gap
- [ ] **Output:** Competitive memo or 2x2

### Week 7: Identify early wins

- [ ] Generate 3-5 early-win candidates
- [ ] Filter against criteria: visible, aligned, achievable, yours
- [ ] **Output:** Top 1-2 early-win proposals with cost/effort

### Week 8: Align stakeholders on direction

- [ ] Review early-win proposals with manager
- [ ] Review with Tier-1 stakeholders
- [ ] Adjust based on feedback
- [ ] **Output:** Committed early win(s) + draft 6-month roadmap

---

## Days 61-90: Deliver

**Goal:** Ship the early win. Set the cadence.

### Week 9: Kick off early win

- [ ] Write first PRD (use the new-PM PRD template, kept tight)
- [ ] Align engineering and design on scope
- [ ] Set up the cadence for the project

### Week 10: Drive delivery

- [ ] Daily presence with the team
- [ ] Cut scope if the timeline is at risk
- [ ] Update manager weekly on progress

### Week 11: Establish operating cadence

- [ ] Publish team rituals (standups, planning, review, retro)
- [ ] Set up monthly metrics review
- [ ] Codify decision rights with engineering and design leads

### Week 12: Ship + reflect

- [ ] Ship the early win (or land at "visible meaningful progress")
- [ ] Write the 90-day retro memo
- [ ] Schedule cycle-2 planning with manager
- [ ] **Output:** Retrospective memo + 6-month plan refined

---

## Cumulative tracker

| Category | Target | Current count |
|----------|--------|----------------|
| 1:1s with team members | 100% in first 30 days | |
| Customer conversations / interviews | >=5 in first 30 days; >=10 by day 60 | |
| Sales / support call shadows | >=10 by day 60 | |
| PRDs / strategy docs authored | 1-2 by day 90 | |
| Early wins shipped / in delivery | 1-2 by day 90 | |
| Written memos to manager | >=3 by day 90 | |
| Stakeholder map | Complete by end of week 2 | |

---

## Manager check-in cadence

| Cadence | Format | Purpose |
|---------|--------|---------|
| Daily (week 1-2) | 15 min | Logistics + early questions |
| Weekly (week 3-12) | 30-45 min | Progress, blockers, calibration |
| End of week 4 | 60 min | "What I'm learning" memo review |
| End of week 8 | 60 min | Early-win commit + 6-month direction |
| End of week 12 | 60 min | 90-day retro + cycle-2 plan |
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 194kUpdated Claude CodeCodexVerifiedInstall