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/red-flags.md
View on GitHub# Red Flags: PM Onboarding
> Common ways this skill's output goes wrong — concrete examples, why they're bad, and how to fix them. Pair with the SKILL.md and Troubleshooting table.
## How to use this document
When you have just produced a 30-60-90 day plan, stakeholder map, or onboarding artifact, scan the red flags below. Each red flag shows a *bad* and *good* version of an early-tenure decision.
---
## Red Flag 1: Jumping to Delivery Before Earning the Right to Lead
**Symptom.** Day 12 of the new role, the PM is already proposing a roadmap change, a re-org, or a "fix" for what they perceive as a broken process.
**Why it's bad.** Watkins' first 90 days exist for diagnosis. A PM who proposes changes before listening will be ignored by stakeholders who do not yet trust them, and will probably be wrong because they have not yet seen the iceberg under the surface.
**Bad example:**
> Week 2 in role: "I've put together a new roadmap that drops three of the active initiatives. Can we discuss in tomorrow's product trio?"
**Good example:**
> Week 2 in role: "I've shadowed 4 customer calls, read the last 6 months of PRDs, and had 1:1s with 7 stakeholders. Themes so far: [...]. I'd like to spend the next two weeks deepening before proposing changes. First strawman thoughts by end of Day 30."
**How to catch it.** Before any change proposal in the first 30 days, ask: "have I done at least 10 hours of listening on this topic?" If not, hold the proposal.
---
## Red Flag 2: STARS Misdiagnosis
**Symptom.** PM treats a Turnaround as Sustaining Success (low urgency, light touch), or treats a Sustaining Success as a Turnaround (sweeping changes, frame as broken).
**Why it's bad.** STARS (Watkins) prescribes very different actions per situation. A turnaround needs decisive early moves; a sustaining-success role needs deference and care. Misdiagnosing the situation produces actions that backfire — fast changes in a healthy team alienate it, slow listening in a turnaround team prolongs the bleeding.
**Bad example:**
> Team is in Turnaround (key engineer left, two missed launches, declining metrics). PM enters with "let me listen for 90 days before changing anything."
**Good example:**
> Team is in Turnaround. PM's first 30 days: (a) confirm diagnosis with skip-level + 5 stakeholders, (b) pick *one* visible early win to deliver by Day 45 (stabilize releases, hit a near-term commitment), (c) protect the team from new asks for 30 days while triage happens.
**How to catch it.** Have you written down your STARS classification with evidence? If not, you cannot have calibrated your action pace.
---
## Red Flag 3: Stakeholder Map Missing Power Dynamics
**Symptom.** Stakeholder map lists names and titles. Does not show influence, interests, current opinion of the team, or relationship to other stakeholders.
**Why it's bad.** A map without power dynamics is an org chart. The point of the stakeholder map is to inform sequencing — who to meet first, who to align before whom, where political risks live. A flat list will get the sequencing wrong.
**Bad example:**
> Stakeholder map: "Sales VP — Jane. Eng VP — Raj. Marketing VP — Sam. Design Director — Liz."
**Good example:**
> Stakeholder map: "Sales VP Jane (high influence, frustrated with last quarter's slip; meet first, listen, get 1 win). Eng VP Raj (high influence, supportive of incoming PM, allies with Sam). Marketing VP Sam (medium influence, neutral). Design Director Liz (medium influence, key product partner; meet by Day 10)."
**How to catch it.** For each stakeholder, can you state their *interest* (what they want from your team), *influence*, and *current sentiment*? If not, the map is incomplete.
---
## Red Flag 4: 30-60-90 Plan with Identical Activities Each Phase
**Symptom.** The plan says "do customer interviews" in all three phases. "Build stakeholder relationships" appears at Day 30, 60, and 90.
**Why it's bad.** The 30-60-90 structure exists because the phases serve different purposes: 30 = listen and diagnose, 60 = test hypotheses and early wins, 90 = commit to direction. A plan that repeats activities loses the phase logic and produces a 90-day plateau instead of a 90-day climb.
**Bad example:**
> "Day 1-30: meet stakeholders, learn product. Day 31-60: meet stakeholders, learn product. Day 61-90: meet stakeholders, learn product."
**Good example:**
> "Day 1-30 (Listen): 1:1s with all stakeholders, 5 customer interviews, read PRDs/postmortems, shadow support. Day 31-60 (Test): write strawman point-of-view memo, propose 1 hypothesis-testing experiment, deliver 1 small early win. Day 61-90 (Commit): publish 90-day POV memo, propose Q+1 priorities, build buy-in."
**How to catch it.** Each phase should have distinct output artifacts. If the artifacts repeat, the phases blur.
---
## Red Flag 5: No Early Win Identified
**Symptom.** The 90-day plan has no concrete "deliverable by Day 45" — just learning activities.
**Why it's bad.** Trust is built by delivery, not by listening. A new PM who completes 90 days of learning with no visible win is judged "still ramping" indefinitely. The early win does not need to be large — it needs to be visible to the team and stakeholders.
**Bad example:**
> "First 90 days will be focused on learning and listening."
**Good example:**
> "Early win target by Day 45: ship the bug-triage process the team has wanted for 3 months. Small in scope, big in signal — shows I listen, deliver, and reduce friction."
**How to catch it.** What is your Day-45 visible deliverable? If you cannot name it, the plan lacks an early win.
---
## Red Flag 6: Calendar Filled with Internal Meetings, No Customer Contact
**Symptom.** Week 4. PM has had 22 internal meetings and 0 customer conversations.
**Why it's bad.** Internal meetings are a comfort zone — same vocabulary, friendly faces, easy debriefs. Customer conversations are uncomfortable but produce the only outside-in data. A PM who has not heard 5 customers in 30 days will absorb the internal narrative and lose product judgment.
**Bad example:**
> Week 4: 22 internal 1:1s, 0 customer calls, 0 support tickets read.
**Good example:**
> Week 4: 12 internal 1:1s, 6 customer calls (3 won, 3 churned), shadowed 4 support tickets, watched 10 session replays. Patterns emerging: [...]"
**How to catch it.** Track ratio of internal-to-external time. If below 5:1 in the first 30 days, you are absorbing the internal bubble.
---
## Red Flag 7: First-PRD Used to Make a Statement
**Symptom.** New PM's first PRD is a major scope, intended to "establish credibility." It is over-engineered, takes a month to write, and signals overreach.
**Why it's bad.** The first PRD's job is to show *how you work*, not to land a marquee win. A first PRD that tries to be the most important PRD of the year almost always lands wrong — too big, too soon, too dependent on relationships that have not been built.
**Bad example:**
> First PRD: 18-page rewrite of the team's entire activation strategy, submitted Week 6.
**Good example:**
> First PRD: a small but well-formed feature in the current sprint, written in the team's template. Shows clear thinking, calibrated scope, partnership with EM and designer. Lands by Week 4.
**How to catch it.** Is your first PRD small enough to ship in the current cycle? If it is multi-quarter, you are over-reaching.
---
## Red Flag 8: Skip-Level Relationship Neglected
**Symptom.** PM has had multiple 1:1s with their manager but never met their skip-level past introductions.
**Why it's bad.** The skip-level (your manager's manager) is the person who will sponsor your promotion, sign off on your strategy memo, and decide whether you are a "rising star" or "still ramping." Skip-level relationships compound; starting at Day 90 is too late.
**Bad example:**
> Day 60. Skip-level introduction was Day 1, no contact since.
**Good example:**
> Day 60. Two skip-level touchpoints: (a) Day 20, manager-arranged 30-min coffee with explicit "what do you want from me" framing, (b) Day 55, sent strawman POV memo for input ahead of formal Day-90 publication."
**How to catch it.** When did your skip-level last hear from you, and what did they hear? If never substantively, the relationship is shallow.
---
## Red Flag 9: Diagnosis Sealed in Private (No Strawman Shared)
**Symptom.** PM has formed strong opinions by Day 30 but keeps them private until the "big reveal" Day-90 memo.
**Why it's bad.** A 90-day surprise memo is high risk. Stakeholders feel they were not consulted; the memo is critiqued for what it missed (which they would have flagged earlier). The fix is to share a *strawman* version at Day 45-60 and invite input.
**Bad example:**
> Day 30-89: PM gathers data silently. Day 90: publishes 8-page POV memo with major recommendations.
**Good example:**
> Day 45: PM shares 1-page strawman POV with manager + skip-level + 3 key stakeholders. Day 60: revised strawman shared with broader team for input. Day 90: published POV is the *third draft*, with broad buy-in earned along the way."
**How to catch it.** Has your POV been pressure-tested by 3+ stakeholders before publication? If not, you are betting the launch on private analysis.
---
## Red Flag 10: Overcommitting in the First Sprint
**Symptom.** New PM, eager to look productive, takes on 8 deliverables in the first sprint, misses 5 of them.
**Why it's bad.** First-quarter signal is loud. A new PM who misses commitments early loses credibility for the rest of the year. The right move is to under-promise and over-deliver in the first 60 days — your future reputation depends on this calibration.
**Bad example:**
> Week 2 commitments: deliver onboarding revamp PRD, run 10 customer interviews, propose new prioritization framework, lead next QBR. Result: 2 of 4 delivered.
**Good example:**
> Week 2 commitments: 5 customer interviews, sit in on 2 sprint planning sessions, deliver a 1-page summary of findings by Week 4. Result: all 3 delivered + early win opportunity surfaced."
**How to catch it.** What is your delivery rate on commitments in the first 30 days? Aim for 100%. Under 80% damages reputation.
---
## Red Flag 11: Treating the Predecessor's Work as Wrong by Default
**Symptom.** New PM frames previous decisions as mistakes, plans, or roadmaps to undo. Visible to the team.
**Why it's bad.** Even if previous decisions were wrong, framing them as such alienates the team that made them and signals the new PM is more interested in differentiation than continuity. Watkins' Sustaining-Success scenarios specifically warn against this pattern.
**Bad example:**
> Week 4: "The previous PM's roadmap missed the most important opportunity. Here's a new direction."
**Good example:**
> Week 4: "The previous roadmap delivered [X] which gave us [Y]. Based on what I'm hearing, the next move I'd consider building on that is [Z]. Curious what the team thinks."
**How to catch it.** Have you publicly criticized any decision made before you arrived? If yes, walk it back; the team made those decisions and you damaged trust.
---
## Red Flag 12: No Personal Pace / Burnout in First Quarter
**Symptom.** New PM works 11-hour days, weekends, eats lunch at desk, skips exercise. Burns out by Day 60.
**Why it's bad.** First 90 days are a marathon. Burning out at Day 60 means the most important quarter ends in apology, not impact. Stamina is a deliverable.
**Bad example:**
> Week 6: PM working 70+ hour weeks, has missed family commitments, irritable on Slack, no longer sleeping well.
**Good example:**
> Week 6: PM works hard but maintains sleep, exercise, and at least 1 family/personal evening per week. Has said no to 2 nice-to-have asks. Stamina is intact through Day 90 and beyond."
**How to catch it.** At Week 6, do you have the energy reserve for the next 6 weeks? If not, scale back commitments now, not at Week 12.
---
## Red Flag Quick Reference
| # | Anti-pattern | One-line check |
|---|---|---|
| 1 | Jumping to Delivery | 10+ listening hours before any change proposal? |
| 2 | STARS Misdiagnosis | Written classification with evidence? |
| 3 | Stakeholder Map Flat | Interest + influence + sentiment per stakeholder? |
| 4 | 30-60-90 Same Each Phase | Distinct artifacts per phase? |
| 5 | No Early Win | Day-45 visible deliverable named? |
| 6 | No Customer Contact | Internal-to-external ratio below 5:1? |
| 7 | First PRD as Statement | First PRD ships within current cycle? |
| 8 | Skip-Level Neglected | Substantive skip-level contact within 30 days? |
| 9 | Private Diagnosis | POV pressure-tested by 3+ stakeholders before publication? |
| 10 | Overcommitting Early | 100% delivery rate on first-30-day commitments? |
| 11 | Predecessor Criticism | No public criticism of pre-tenure decisions? |
| 12 | Burnout in First Quarter | Energy reserve intact at Week 6? |
## Related Reading
- SKILL.md Troubleshooting section (for symptom -> root cause -> resolution)
- references/30-60-90-template.md (if present)
- references/stakeholder-map-template.md (if present)
- pm-1on1s/references/red-flags.md (for new-relationship 1:1 patterns)
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 |