// 30-60-90 day plan for a new PM joining a company or team, grounded in Michael Watkins' First 90 Days framework and the STARS situational diagnosis. Includes week-by-week plan, stakeholder map, 1:1 question bank, and first-PRD template.
Expert agile coaching for team transformation, framework selection, maturity assessment, and organizational change management. Use when selecting an agile framework for a team, coaching through Tuckman development stages, facilitating retrospectives, assessing organizational agile maturity, or designing a transformation roadmap.
Atlassian Administrator for managing and organizing Atlassian products, users, customization of the Atlassian suite, permissions, security, integrations, system configuration, and all administrative features. Use for user provisioning, global settings, security policies, system optimization, and org-wide Atlassian governance.
Atlassian Template and Files Creator/Modifier expert for creating, modifying, and managing Jira and Confluence templates, blueprints, custom layouts, reusable components, and standardized content structures. Use for building org-wide templates, custom blueprints, page layouts, and automated content generation.
Structured PM 1:1 templates by partner type — with manager, engineering manager partner, designer, IC reports — grounded in Radical Candor, the GROW coaching model, and the Manager Tools 1:1 framework.
PM career ladder rubrics from APM through VP/CPO across product sense, execution, leadership, strategy, and communication. Includes gap analysis, growth planning, and promotion packet templates.
Structured PM interview preparation across product sense, execution, strategy, behavioral, and technical rounds, using CIRCLES, AARM, STAR, and the estimation framework. Calibrated to APM, PM, Senior PM, and Group PM rubrics.
| name | pm-onboarding |
| description | 30-60-90 day plan for a new PM joining a company or team, grounded in Michael Watkins' First 90 Days framework and the STARS situational diagnosis. Includes week-by-week plan, stakeholder map, 1:1 question bank, and first-PRD template. |
| license | MIT + Commons Clause |
| metadata | {"version":"1.0.0","author":"borghei","category":"project-management","domain":"pm-career","updated":"2026-05-21T00:00:00.000Z","tech-stack":"pm-onboarding, 30-60-90, first-90-days, stars-framework"} |
A new PM's first 90 days are disproportionately important. Trust earned in the first quarter compounds; missteps in the first quarter haunt for the next year. This skill is a structured 30-60-90 day plan that helps a new PM diagnose the situation, build relationships, identify early wins, and arrive at the end of the quarter with credibility and a clear point of view.
The skill draws on Michael Watkins' The First 90 Days, the STARS situational diagnosis (Start-up / Turnaround / Accelerated growth / Realignment / Sustaining success), and the public PM onboarding patterns popularized by Lenny Rachitsky and other senior product leaders.
Watkins' STARS framework forces you to ask: what kind of situation am I entering? The answer determines what early actions are appropriate.
| Type | What it means | First-90-day priorities |
|---|---|---|
| Start-up | Building from scratch (new product, new team) | Move fast, hire, set direction, prove the idea |
| Turnaround | Failing product / team that needs rescue | Diagnose, cut, set a new direction, change personnel if needed |
| Accelerated growth | Working, growing fast, breaking under scale | Build operating muscle, hire, design org for growth |
| Realignment | Apparently successful but losing ground | Confront denial, align on the gap, make incremental change |
| Sustaining success | Working well, must be preserved and refined | Listen long before acting, do no harm, preserve trust |
Why this matters: A new PM walking into a Sustaining-success area should listen for at least 60 days. The same PM in a Turnaround should act within 30. Misreading the situation is the most common new-PM mistake.
In your first two weeks, ask every stakeholder:
Patterns across 8-12 conversations reveal the STARS type.
Goal: Build context. No major decisions. No big PRDs. Listen, observe, ask.
| Week | Focus | Outputs |
|---|---|---|
| Week 1 | Logistics, manager 1:1, team intros | Calendar set up, stakeholder shortlist, manager-aligned 90-day plan draft |
| Week 2 | Customer immersion: read research, listen to sales/support calls | Customer-segment map, top-5 customer pain hypotheses |
| Week 3 | Product immersion: use the product daily, read PRDs, walk the metrics tree | Product-area map, baseline metrics dashboard |
| Week 4 | Team immersion: 1:1 with every engineer and designer in the immediate team | Team strength/gap map, draft of STARS diagnosis |
End-of-30 deliverable: A 1-page "What I'm learning" memo to your manager. Includes your STARS diagnosis, top-3 things going well, top-3 risks, and questions you still need to answer.
Goal: Build a point of view. Identify the early-win candidates. Start to align stakeholders on direction.
| Week | Focus | Outputs |
|---|---|---|
| Week 5 | Deepen customer evidence: interview 3-5 customers yourself | Customer insight memo |
| Week 6 | Competitive scan + market context | Competitive 2x2 or summary |
| Week 7 | Identify 1-2 early wins (visible, achievable in <90 days) | Early-win proposal with cost/effort |
| Week 8 | Align manager + key stakeholders on early wins and 6-month direction | Aligned roadmap proposal |
End-of-60 deliverable: A first PRD or strategy memo for the early win, plus a draft 6-month roadmap. Share with manager and 2-3 key stakeholders for feedback before going wider.
Goal: Deliver the early win. Set the operating cadence. Establish credibility.
| Week | Focus | Outputs |
|---|---|---|
| Week 9-10 | Ship the early win (or be in delivery with visible progress) | First shipped artifact under your name |
| Week 11 | Establish operating cadence: standups, planning, review, metrics | Cadence calendar published |
| Week 12 | Write the 90-day retro: what worked, what changed, what's next | 90-day retro memo |
End-of-90 deliverable: A retrospective memo. What you learned, what changed in your thinking from days 1-30, what your point of view is now, what the next 90 days look like.
In Watkins' framework, early wins are how new leaders build credibility. A good early win is:
Bad early wins:
Good early wins:
Identify candidates by week 6. Commit to one or two by week 8. Ship by week 12.
New-PM stakeholder mapping is different from steady-state mapping. The new PM is mapping who knows what and whose trust matters, not just who has decision rights.
Three-tier model:
| Tier | Description | Action |
|---|---|---|
| Tier 1 | Direct manager, your team's eng/design lead, your 1-2 most-engaged cross-functional partners | Weekly 1:1 for first 90 days |
| Tier 2 | Skip-level, adjacent PM peers, key cross-functional stakeholders (sales, support, legal, marketing) | One 1:1 within first 30 days, monthly afterward |
| Tier 3 | Anyone else useful for context (former PM of the area, customer success leads, exec sponsors) | One 1:1 within first 60 days |
Aim for 25-35 distinct conversations in the first 60 days. Less is too little context; more is performance.
See assets/stakeholder_map.md for the full template.
New PMs often want to author a big PRD in week 4 to "make their mark". Don't. A first PRD has unique requirements:
See assets/first_prd_template.md.
| Symptom | Likely Cause | Resolution |
|---|---|---|
| You feel pressure to "make a mark" in week 2 | Manager or skip-level signaled urgency early | Renegotiate the timeline; share Watkins' early-win principle; commit to a 90-day visible outcome rather than week-2 declarations |
| You inherit a roadmap you don't agree with | Predecessor committed to work before you arrived | Honor existing commitments through your learning period; propose adjustments in week 8 with evidence, not in week 2 with opinion |
| Stakeholders give you conflicting accounts of "what's broken" | Normal in months 1-2; reveals organizational tensions | Triangulate across 8-12 conversations before forming a view; the truth is usually the intersection |
| You haven't met your skip-level by week 4 | Calendar friction; new PM hesitant to ask | Ask your manager to introduce or directly request 30 minutes; skip-level visibility in the first 60 days is essential |
| You spend all your time in meetings and can't think | Over-scheduled in the learning phase | Block 2-hour daily focus windows; reduce 1:1 cadence to 30 min where possible; protect a "no meetings" half-day per week |
| Your STARS diagnosis is wrong (e.g., you thought Turnaround but it's Sustaining success) | Misread early signals; missed long-tenured staff voices | Re-interview 3-5 senior people in week 6; explicitly ask "what should I not change in my first year?"; revise diagnosis |
| The early win you committed to is at risk of slipping | Over-scoped or hit unexpected dependencies | Cut scope ruthlessly; ship a smaller version on time rather than a bigger version late; the timeline is the win, not the size |
| You haven't sent the 90-day retro because it feels self-indulgent | Imposter syndrome around "what did I actually do" | Send it anyway; it forces clarity, signals to your manager that you self-reflect, and creates the artifact you'll need for year-end review |
In Scope:
Out of Scope:
personal-productivity/ and other career skillspm-career-ladder/Important Caveats:
| Integration | Direction | What Flows |
|---|---|---|
pm-1on1s/ | Feeds into | The 1:1 question banks here are designed for first-90-day conversations; ongoing 1:1s use the broader skill |
pm-career-ladder/ | Feeds into | End-of-90-day retro becomes the baseline self-score on the ladder |
pm-interview-prep/ | Receives from | Pre-offer "Can you do the job?" stories often map to early wins delivered in past 90-day windows |
senior-pm/stakeholder-mapper/ | Reuses | The stakeholder mapping technique scales beyond onboarding into steady-state |
execution/create-prd/ | Feeds into | First-PRD template is a tighter version of the full PRD skill |
discovery/interview-synthesis/ | Reuses | Customer interviews in week 5 use the same synthesis discipline as steady-state discovery |
references/first-90-days-playbook.md -- Watkins-grounded deep dive on STARS, early wins, securing winsassets/30_60_90_plan.md -- Editable 30-60-90 plan templateassets/stakeholder_map.md -- Onboarding stakeholder map templateassets/onboarding_1on1_questions.md -- Question bank for the first 30 days of 1:1sassets/first_prd_template.md -- Tighter PRD template for new-PM constraintsExternal: