borghei/Claude-Skills / project-management/career/pm-career-ladder
pm-career-ladder
VerifiedScores a PM against level rubrics from APM to VP/CPO, then builds a gap analysis, 6-month growth plan or promotion packet. Use when preparing for promotion, calibrating your level, or turning manager feedback into a plan.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 7.8 KB |
| assets/gap_analysis.md | markdown | 3.0 KB |
| assets/growth_plan.md | markdown | 4.8 KB |
| assets/promo_packet.md | markdown | 5.0 KB |
| examples/maria-chen-apm-to-pm-promo-packet.md | markdown | 12.5 KB |
| references/ladder-playbook.md | markdown | 11.4 KB |
| references/ladder-rubric-detail.md | markdown | 9.2 KB |
| references/red-flags.md | markdown | 12.9 KB |
references/ladder-playbook.md
View on GitHub# PM Ladder, Rubric Detail & Growth Playbook
Read this when you need the full level-by-level ladder, the per-level rubric behaviors, the gap-analysis process, the 6-month growth plan, the promo packet structure, the operating workflow, troubleshooting, or success criteria.
## The Ladder
Five dimensions x seven levels. APM through GPM are IC tracks; Director and above are management tracks.
| Dimension | APM | PM | Sr PM | Group PM | Director | VP / CPO |
|-----------|-----|-----|-------|----------|----------|----------|
| Product Sense | Solves well-defined feature problems | Frames problems independently for a single product area | Identifies high-leverage opportunities across the area | Sets product strategy across multiple areas | Drives portfolio bets across teams | Sets product vision for the company |
| Execution | Ships features against a defined plan | Owns end-to-end delivery of a product area; runs the rituals | Designs the operating system for the team; unblocks systematically | Aligns multiple teams to coherent outcomes; manages dependencies at scale | Drives delivery across a portfolio with predictable cadence | Builds the org-wide execution operating model |
| Leadership | Influences peers in the trio | Earns trust as the product lead for the area | Mentors junior PMs; influences across functions | Leads a small group of PMs (formally or informally); develops them | Manages PM managers; develops the next layer | Builds and develops the PM org; succession planning |
| Strategy | Understands the area's strategy and translates it to features | Owns the area's roadmap with rationale | Connects area strategy to company strategy; defends trade-offs | Sets multi-quarter strategy for the product line; aligns the org | Owns the product line P&L or equivalent business metric | Owns company product strategy; board-facing |
| Communication | Clear written and verbal updates to the team | Crisp PRDs, status updates, and stakeholder presentations | Effective exec readouts; persuasive writing for cross-functional alignment | Sets the narrative for the product line; aligns multi-team stakeholders | Sets exec-level narrative; speaks for the product org externally | Speaks for the company on product; analyst- and customer-facing |
A level is reached when a PM is operating at that bar **consistently across all five dimensions for >=2 quarters**, not the high-water mark of a single quarter.
## Rubric Detail per Level
### APM (Associate Product Manager)
**Scope:** A single feature or sub-area inside a larger product area. Manager-supervised on most decisions.
**Looks like:**
- Writes clear PRDs for well-defined feature problems
- Runs the rituals (standups, planning, demos) for their feature
- Synthesizes user feedback into actionable changes
- Builds trust with engineers and designers as a thought partner
- Ships features on a known timeline
**Promotion to PM signal:** Has run end-to-end delivery of >=2 features with measurable impact; manager no longer needs to review every PRD; able to handle ambiguous user feedback without escalation.
### PM (Product Manager)
**Scope:** A defined product area (e.g., onboarding, search, billing) with 4-8 engineers and 1-2 designers.
**Looks like:**
- Owns the roadmap for the area with clear rationale tied to business outcomes
- Runs discovery proactively (interviews, experiments) rather than waiting for tickets
- Authors PRDs that pass a 10-second exec scan
- Resolves cross-functional disagreements without escalating to manager
- Sets weekly cadence and metrics review for the area
- Reports on the area's health to leadership monthly
**Promotion to Sr PM signal:** Has identified and led 1-2 high-leverage initiatives that were not on the roadmap when they joined; mentors APMs informally; has a track record of saying no with reasoning.
### Senior PM
**Scope:** A meaningful product area or a complex single-team product. Often the most senior PM in the room with engineering and design leads of equal or higher seniority.
**Looks like:**
- Sets 6-12 month strategy for the area, defended with data and customer evidence
- Identifies systemic problems and proposes operating-model fixes (not just feature fixes)
- Mentors >=1 junior PM with measurable growth
- Influences other product areas without authority
- Designs the metrics tree for the area and uses it for prioritization
- Authoritative on the area's customer, market, and competitive context
**Promotion to Group PM signal:** Has led a multi-team or platform initiative successfully; has been informally consulted on strategy for adjacent areas; manager-track candidates begin to mentor a small group of PMs.
### Group PM
**Scope:** A product line covering multiple sub-areas, often with 2-5 PMs reporting in (formally or dotted-line) and 20-50 engineers across teams.
**Looks like:**
- Sets multi-quarter strategy for the product line
- Aligns multiple teams to a coherent set of outcomes
- Develops PMs -- promotion track records matter at this level
- Represents the product line to executives and external stakeholders
- Designs cross-team operating rhythms (e.g., portfolio review, dependency forums)
- Authoritative on org-design trade-offs (team boundaries, decision rights)
**Promotion to Director signal:** Has demonstrated repeated success across multiple PM teams; has built a bench of promotable PMs; comfortable in P&L-style conversations.
### Director of Product
**Scope:** A product portfolio with multiple PMs (typically 5-15) and PM managers. Owns P&L or equivalent business metric.
**Looks like:**
- Owns portfolio strategy and capital allocation across the area
- Develops PM managers (the next layer of leadership)
- Sets the operating cadence for the product organization (portfolio review, planning, hiring bar)
- Represents product externally to customers, partners, analysts
- Influences company-level strategy
### VP / CPO
**Scope:** The product organization, company-wide product strategy, executive-team membership.
**Looks like:**
- Owns the company product vision and roadmap
- Builds and develops the product org
- Partners with the CEO and other functional leaders on company strategy
- Board-facing on product topics
- Sets the bar for craft, hiring, and operating excellence across product
## Gap Analysis Process
1. **Self-score across the rubric.** For each dimension at your current level and the next, rate yourself: *Below bar / At bar / Above bar*.
2. **Manager-score independently.** Ask your manager to score you using the same rubric without seeing your scores.
3. **Compare.** Differences indicate calibration gaps that themselves need addressing.
4. **Pick 2-3 dimensions to develop.** Trying to grow on all five at once dilutes effort.
5. **Translate to behaviors.** For each prioritized dimension, identify 2-3 specific behaviors at the next level you do not yet exhibit.
6. **Find experiments.** Each behavior gap becomes an experiment over the next 1-2 quarters.
See `assets/gap_analysis.md` for the full worksheet.
## 6-Month Growth Plan
A growth plan turns the gap analysis into concrete action. Each plan has three to five focus areas, each with:
- **Bar at next level:** What does "at bar" look like?
- **Current state:** What do you do today?
- **Target state:** What would "at bar" look like for you specifically?
- **Experiments:** 1-3 concrete actions in the next 90 days
- **Evidence:** What artifact or observable outcome proves you reached the target?
- **Manager support:** What does your manager need to do to make this possible?
- **Check-in cadence:** When do you review progress?
See `assets/growth_plan.md` for the full template.
## Promo Packet
When you and your manager align that you're ready for promotion, build a promo packet. A strong packet includes:
1. **Scope statement** -- One paragraph: what you own and at what scale.
2. **Impact summary** -- 3-5 bullets, each with a quantified outcome and your specific contribution.
3. **Rubric mapping** -- For each of the five dimensions, 1-2 examples of you operating at the next level's bar.
4. **Peer and partner quotes** -- 3-5 quotes from engineers, designers, cross-functional partners, and direct reports (if any).
5. **Growth narrative** -- How you've grown over the cycle; what feedback you've absorbed.
6. **What's next** -- What you would tackle at the new level.
See `assets/promo_packet.md` for the full template.
## Workflow
1. **Calibrate quarterly.** Self-score against the rubric every quarter; have your manager score independently every 6 months.
2. **Identify the gap.** Pick 2-3 dimensions where you are below bar for the next level.
3. **Write a 6-month growth plan.** Translate gaps into experiments.
4. **Review monthly with manager.** In a recurring 1:1, walk the plan, update evidence, adjust experiments.
5. **Build the packet at the 3-month mark of the cycle.** Do not start the packet two weeks before the deadline.
6. **Manage your own narrative.** Quarterly written summaries of impact, sent to your manager, become the raw material for the eventual packet.
## Troubleshooting
| Symptom | Likely Cause | Resolution |
|---------|-------------|------------|
| You believe you're at the next level but you keep getting passed over | Calibration gap between you and your manager / leveling committee | Run the gap analysis with your manager independently; if you're 1 level apart on >=2 dimensions, the gap is calibration, not performance -- ask for specific examples of "at bar" peers |
| Your manager says "you need more scope" with no path to get it | Scope is gated by org design, not your performance | Identify a stretch project across an adjacent team; volunteer to backfill a Sr PM on leave; propose a new initiative with explicit success criteria |
| Your impact is real but invisible | Communication dimension is below bar | Send a monthly written impact summary to your manager and skip-level; present at a broader forum quarterly; turn one project into a public blog or talk |
| You score "above bar" on execution but "below bar" on strategy | You are a strong tactician but have not invested in strategy | Volunteer to author the area's quarterly strategy doc; reduce time spent in delivery rituals by 30% and reinvest in customer research and competitive analysis |
| Promotion was denied with vague feedback | Manager is uncomfortable with the feedback or doesn't have specifics | Ask for the 2 most-cited "below bar" examples from the calibration discussion; if they cannot provide them, escalate to a skip-level conversation |
| You promote on technical execution but stall as Sr PM | You haven't shifted from "ship the roadmap" to "design what should be on it" | Block calendar time for discovery and strategy; reduce time spent in delivery rituals; develop one junior PM to demonstrate leadership behaviors |
| You skip levels (PM to Sr PM in <12 months) and burn out | Promotion happened on potential, not consistent demonstration | Slow down; build the operating muscles of the new level before reaching for the next; protect 2 quarters of operating-at-level before chasing the next promo |
## Success Criteria
- You have a current self-score on the 5x6 rubric, updated quarterly
- Your manager has scored you independently within the last 6 months
- You have a written 6-month growth plan with 2-3 focus dimensions
- You have a monthly written impact summary stream going to your manager
- When promo cycle comes, you have a half-built packet by the 3-month mark
- Your peers and partners can articulate why you operate at the level you claim
- Your growth is sustainable: you operate at level for >=2 quarters before chasing the next
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 |