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/stakeholder_map.md

View on GitHub
# Onboarding Stakeholder Map

**Your name:** ___________  **Start date:** ___________
**Target completion:** End of week 2 for Tier 1; end of week 4 for Tier 2; end of week 8 for Tier 3.

---

## Tier 1: Weekly 1:1 for first 90 days

Direct manager, your team's lead engineers and designers, your most-engaged cross-functional partners (1-2). These are the people whose trust matters most in your first quarter.

| Name | Role | Why critical | First 1:1 booked? | Notes |
|------|------|--------------|-------------------|-------|
| | Manager | Your boss; sets the bar | | |
| | Eng Lead | Co-leads delivery | | |
| | Design Lead | Co-leads product quality | | |
| | | Engineer | Senior IC | | |
| | | Designer | Senior IC | | |

---

## Tier 2: First 1:1 in 30 days, monthly afterward

Skip-level, adjacent PM peers, key cross-functional stakeholders.

| Name | Role | Why important | First 1:1 booked? | Notes |
|------|------|---------------|-------------------|-------|
| | Skip-level (VP/Director) | Strategic visibility | | |
| | Adjacent PM 1 | Coordination, mutual context | | |
| | Adjacent PM 2 | Coordination, mutual context | | |
| | Sales / GTM Lead | Customer & pipeline | | |
| | Customer Success Lead | Retention & adoption | | |
| | Support Lead | Pain & ticket trends | | |
| | Marketing Lead | Positioning & launch | | |
| | Data / Analytics Lead | Metrics, A/B test pipeline | | |
| | Legal / Privacy | Compliance gating | | |

---

## Tier 3: First 1:1 in 60 days

Helpful for context but not weekly.

| Name | Role | Why useful | First 1:1 booked? | Notes |
|------|------|------------|-------------------|-------|
| | Former PM for the area | Historical context | | |
| | Exec sponsor (if any) | Strategic visibility | | |
| | Engineering Manager partner | Cross-team coordination | | |
| | Adjacent customer success | Customer empathy | | |
| | HR / People Partner | Career conversations | | |

---

## Conversation goals

For each Tier 1 and Tier 2 1:1, aim to learn:

- **What you do** -- their role and accountabilities
- **Top 3 priorities** for the quarter
- **What's going well** they want to preserve
- **What's broken** or hard to do today
- **How they want to work with me** -- communication frequency, decision involvement
- **Who else should I be talking to**

For Tier 1 specifically, also discuss:

- Working style preferences (sync vs. async, written vs. verbal, etc.)
- Escalation thresholds
- What success looks like for the partnership in 6 months

---

## STARS signal tracker

Use these conversations to triangulate the STARS situation. After each 1:1, jot down which signals you heard:

| Person | Heard signals of... | STARS leaning |
|--------|---------------------|---------------|
| | "We need to rescue X" | Turnaround |
| | "Don't change Y" | Sustaining |
| | "We're breaking under growth" | Accelerated growth |
| | "We're losing share" | Realignment |
| | "We're starting Z from scratch" | Start-up |

**Diagnosis by week 4:** ______________________________________

---

## Stakeholder calibration

By end of week 8, you should be able to answer:

- Who are my 3 strongest cross-functional allies? ____________
- Who are 1-2 stakeholders likely to be skeptical of changes? ____________
- Who controls a critical resource (eng capacity, budget, data access)? ____________
- Who has the most operational knowledge of the current state? ____________
- Who am I most likely to have a tension with in months 2-3? ____________

---

## Stakeholder engagement plan (post day-30)

| Stakeholder | Cadence | Format | Owner of next action |
|-------------|---------|--------|----------------------|
| | | | |
| | | | |
| | | | |
| | | | |
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