borghei/Claude-Skills / project-management/career/pm-onboarding
pm-onboarding
VerifiedBuilds 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 7.8 KB |
| assets/30_60_90_plan.md | markdown | 4.3 KB |
| assets/first_prd_template.md | markdown | 4.0 KB |
| assets/onboarding_1on1_questions.md | markdown | 5.2 KB |
| assets/stakeholder_map.md | markdown | 3.6 KB |
| examples/fintech-series-b-new-pm-30-60-90.md | markdown | 14.3 KB |
| references/30-60-90-plan-and-tactics.md | markdown | 9.8 KB |
| references/first-90-days-playbook.md | markdown | 8.3 KB |
| references/red-flags.md | markdown | 12.9 KB |
references/first-90-days-playbook.md
View on GitHub# First 90 Days Playbook for PMs
A Watkins-grounded deep dive on the principles that drive successful PM transitions.
---
## 1. The transition trap
Most PMs are evaluated on their first quarter even though they have the least context in their first quarter. The trap: feeling you must "produce" before you have the evidence to know what to produce.
Watkins' core principle is that **the first 90 days are about achieving the breakeven point** -- the point at which the value you've added equals the cost of bringing you in. Acting before reaching breakeven (declaring strategy, reorging, killing things) burns trust faster than it builds.
The structured 30-60-90 plan exists to compress the time-to-breakeven while protecting against premature action.
---
## 2. STARS in depth
STARS is not academic. Each type has distinct rules for what early actions are appropriate.
### Start-up
**Looks like:** New product, new team, no existing customers (or very few). Things you build from scratch.
**Pitfalls:** Hesitating to make decisions because "we don't have data yet". At start-up, you must form a point of view from limited data and iterate fast.
**90-day priorities:**
- Set direction (vision, customer hypothesis)
- Hire the right initial team
- Build the smallest thing that proves the idea
- Establish operating cadence early
### Turnaround
**Looks like:** A failing product or team. Metrics declining, morale low, leadership has lost confidence.
**Pitfalls:** "Listening tour" too long. At turnaround, the team needs visible decisive action within 30 days or trust erodes further.
**90-day priorities:**
- Diagnose quickly (intense first 2 weeks)
- Cut what is not working (projects, possibly people)
- Set a new direction
- Pick a high-symbolism early win
### Accelerated Growth
**Looks like:** Working product, breaking under scale. Hiring fast, processes lag, quality slips.
**Pitfalls:** Trying to "fix everything" in the first 90 days. At accelerated growth, the work is operating-system design, not heroics.
**90-day priorities:**
- Strengthen operating cadence
- Hire the right roles for scale
- Identify the 2-3 metrics that matter most
- Resist the urge to introduce too much process at once
### Realignment
**Looks like:** Apparently successful, but losing share or relevance. Most insidious -- the team believes things are fine.
**Pitfalls:** Aggressive moves alienate the team that built the current success. At realignment, the work is changing minds before changing actions.
**90-day priorities:**
- Confront the denial (data-driven evidence the team can see)
- Build alignment around the gap
- Make incremental, evidence-driven changes
- Identify the small set of allies for the longer transformation
### Sustaining Success
**Looks like:** Working well, market-leading. Your job is to not break it.
**Pitfalls:** "Make your mark" pressure leads to changing things that didn't need changing. At sustaining success, the most experienced employees are the ones whose trust matters most.
**90-day priorities:**
- Listen long (60+ days)
- Identify the 2-3 levers for marginal improvement
- Preserve what works
- Build trust with long-tenured staff
---
## 3. Securing early wins
A correctly chosen early win:
1. **Is visible to your manager and skip-level** -- They can name it 90 days from now.
2. **Is achievable inside 90 days** -- Or has visible meaningful progress by day 90.
3. **Aligns with existing priorities** -- Don't pick a contrarian early win.
4. **Has clear authorship** -- Your fingerprints are unambiguous.
5. **Builds long-term capability** -- Bonus if the win sets up later wins (e.g., a customer research cadence, a metric dashboard, a documentation hub).
### Pattern-library of strong early wins for PMs
- Ship a previously-stalled feature with renewed engineering buy-in
- Kill a zombie project and free engineering capacity
- Run a customer research project whose findings appear in an exec readout
- Publish a sharp competitive memo that becomes the team's reference
- Author a re-prioritized backlog with explicit rationale that earns engineering trust
- Introduce a regular metrics review that surfaces an issue the team didn't know about
- Resolve a long-standing cross-functional tension (e.g., handoff between PM and Marketing)
### Pattern-library of weak early wins
- Reorging the team in week 6 (no earned trust)
- A strategy doc that never leaves a wiki
- "Cleaning up the backlog" (invisible)
- A new framework / template proliferation (process for process's sake)
- A win owned 50/50 with a peer (no clear authorship)
---
## 4. Negotiating success with your manager
Watkins emphasizes the **five-conversations framework** -- five distinct conversations with your manager in the first 90 days:
| Conversation | Timing | What to discuss |
|--------------|--------|-----------------|
| 1. Situational diagnosis | Week 1-2 | What kind of STARS situation am I in? Do we agree? |
| 2. Expectations | Week 2-4 | What does success at 6 months look like? At 12 months? |
| 3. Style | Week 3-4 | How does my manager prefer to work? Frequency, format, escalation thresholds? |
| 4. Resources | Week 4-8 | What do I need to succeed? People, budget, decision rights? |
| 5. Personal development | Week 6-8 | What does my manager see as my development priorities? |
These do not have to be 5 separate meetings. They should all happen by week 8.
---
## 5. Achieving alignment in the team
By day 90, the new PM should have:
- A shared point of view with the team about *what we're trying to accomplish*
- A shared point of view with the team about *how we operate* (rituals, decision rights, communication)
- A shared point of view with the team about *what's broken and what we're fixing first*
Alignment is built through repeated conversation, not declared in a kickoff. The week-by-week 1:1s, the early-win project, and the 90-day retro memo are the artifacts that build alignment over time.
---
## 6. Common new-PM failure modes
| Failure mode | Why it happens | How to avoid |
|--------------|----------------|---------------|
| Spend 90 days in listen mode, never acts | Imposter syndrome; "I need more data" | Commit to an early win by day 60; ship by day 90 |
| Declare strategy in week 4 | "Make your mark" pressure | Watkins' rule: wait for breakeven before strategic moves |
| Inherits and accepts the existing roadmap unchanged | Conflict avoidance | Use weeks 5-8 to build a point of view and propose adjustments with evidence |
| Builds a 12-page PRD as the first deliverable | Demonstrating "thoroughness" | First PRD: 2-4 pages, customer-evidenced, scoped to ship in 90 days |
| Avoids difficult conversations with cross-functional partners | Wants to be liked | Address tensions in the first 60 days; tensions in months 1-2 are easier than month 6 |
| Doesn't meet skip-level until month 4 | Calendar friction; deference | Request the skip-level 1:1 in week 2 |
| Sends no written updates to manager | "My manager knows what I'm doing" | Weekly written status in first 90 days; even a 5-line note |
| Skips the 90-day retro | "Self-evaluation feels weird" | Send it anyway; it's the most important artifact of the cycle |
---
## 7. Onboarding when remote or hybrid
The 90-day playbook applies, with adjustments:
- **More 1:1s, shorter:** 30 min beats 60 min when virtual; you can do more per week
- **Written communication weighs more:** Async updates, public docs, recorded meeting summaries
- **Be in the office for "high-bandwidth" moments:** Quarterly planning, executive reviews, customer visits
- **Proactively schedule informal time:** 15-min coffee chats with peers; remote work eliminates accidental face time
---
## 8. The 90-day retro memo
Structure for the end-of-cycle memo to your manager:
1. **What I learned about the STARS situation** -- has your diagnosis changed?
2. **Top 3 things going well** that I want to preserve
3. **Top 3 risks** that need attention
4. **My point of view on the area** -- 1-2 paragraphs of original synthesis
5. **What I shipped / impacted** -- the early win and any other tangible outcomes
6. **What I'd do differently** -- self-aware reflection on missteps
7. **What I need from you** -- specific manager support for the next quarter
8. **Next 90 days** -- top priorities going into the second cycle
This memo is the artifact that locks in the credibility built over the first quarter. Send it. Don't skip it.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |
| 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: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| 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: 194k | Updated | Claude CodeCodex | Verified | Install |