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/red-flags.md
View on GitHub# Red Flags: PM Career Ladder
> 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 self-assessment, gap analysis, growth plan, or promo packet, scan the red flags below before sharing with your manager or promo committee. Each red flag shows a *bad* and *good* version.
---
## Red Flag 1: Rubric Gaming (Filling the Checkboxes, Not the Spirit)
**Symptom.** Promo packet lists activities that nominally match each rubric dimension but produce no meaningful impact — "ran 3 workshops" without naming what changed because of them.
**Why it's bad.** The rubric is meant to *describe* the kind of impact a person at that level produces, not to be a checklist. Rubric gaming gets people promoted on optics, then fails them within a quarter when the new level's actual demands appear.
**Bad example:**
> "Strategy (Senior PM): I wrote a strategy document. I ran a strategy workshop. I created a strategy slide for our QBR."
**Good example:**
> "Strategy (Senior PM): Authored the Q3 strategy memo that re-prioritized the team from feature-X to onboarding (3 workshops, 14 stakeholder interviews). Strategy adopted; resulted in onboarding completion rising from 41% to 64% in two quarters."
**How to catch it.** For every claim, ask: "what changed in the business because of this?" If you cannot answer, you are gaming the rubric.
---
## Red Flag 2: Growth Plan That Does Not Change Behavior
**Symptom.** 6-month growth plan lists generic activities ("read more product books", "improve communication") with no measurable behavior change.
**Why it's bad.** Vague growth plans are aspirations, not plans. They allow the PM and their manager to feel productive without producing learning. The next 6-month review will be a copy-paste of this one.
**Bad example:**
> "Growth area: Strategy. Plan: read 2 strategy books, attend a strategy course, sync with my manager more."
**Good example:**
> "Growth area: Strategy. Plan: (a) Draft a 2-page strategy memo for the team by Week 4 and present it; success = manager + EM rate it 4/5 on clarity. (b) Lead the Q3 prioritization debate; success = decision documented and team aligned. (c) Run one 6-month forward look in QBR. Manager reviews monthly."
**How to catch it.** Each growth area should have a behavior that an observer could *see* changing — a meeting you would not previously have run, a document you would not previously have written.
---
## Red Flag 3: Self-Assessment Inflation
**Symptom.** PM scores themselves above their actual level on every dimension. Manager scores them below. Conversation becomes a calibration debate, not a growth conversation.
**Why it's bad.** Self-assessment inflation wastes the entire calibration loop. The point of the rubric is to enable a *concrete* discussion, not a score-comparison contest. Inflation also makes the PM look unaware of the bar at the next level.
**Bad example:**
> "Self-rating Product Sense: Senior PM. Evidence: I have product opinions." Manager rating: PM.
**Good example:**
> "Self-rating Product Sense: PM, trending toward Senior. Evidence: I lead feature-level product decisions (PM bar). I have not yet driven a 0-to-1 product bet or framed a multi-quarter portfolio choice (Senior bar). Plan to do so this quarter via the onboarding revamp."
**How to catch it.** For every dimension where self and manager differ by more than half a level, examine the *evidence*, not the score.
---
## Red Flag 4: Promo Packet Without Scope Evidence
**Symptom.** Promo packet lists outputs ("launched feature X") but does not show the scope expansion that justifies the next level.
**Why it's bad.** Promotion is about a sustained shift in *scope and impact*, not a one-time deliverable. A packet of features without scope evidence reads as "this PM did their current job, please promote them."
**Bad example:**
> "This year I launched: feature A, feature B, feature C. Recommend promotion to Senior PM."
**Good example:**
> "This year I expanded from owning feature-team scope to owning the onboarding domain. Evidence: (a) led the cross-team activation initiative (3 teams, 4 quarters), (b) authored the activation strategy memo that became the team's Q3-Q4 north star, (c) mentored 2 PMs (now on track for PM-level). I am operating at Senior PM scope; the packet asks for the title to match."
**How to catch it.** Scope shift should be visible in the *first paragraph* of the packet, before any feature list.
---
## Red Flag 5: Confusing IC Track with Manager Track
**Symptom.** Senior PM packet emphasizes managing people, or Director packet emphasizes individual product wins.
**Why it's bad.** The ladder has separate IC and manager tracks for a reason. Senior PMs and Group PMs deliver through *scope*; Directors and VPs deliver through *people and systems*. Submitting evidence from the wrong track signals confusion about the role.
**Bad example:**
> Senior PM packet: "I have coached 3 junior PMs, run team retros, and improved hiring."
**Good example:**
> Senior PM packet: "I led the activation domain (Senior IC). Coaching of junior PMs is a positive sign; I would highlight in a Director packet, not here. Headline impact this year: activation rate +23pp via 4 cross-team initiatives I owned end-to-end."
**How to catch it.** Map every piece of evidence to the rubric dimension. If your evidence is mostly about leading other people rather than product/strategy work, you are on the wrong track or applying for the wrong level.
---
## Red Flag 6: Frameworks Memorized but Not Applied
**Symptom.** PM can name RICE, JTBD, OKRs, opportunity solution trees, but their actual work artifacts show no evidence of any of them.
**Why it's bad.** Vocabulary without practice is rubric theater. Promo committees see through it. The PM who *uses* one framework well will out-perform the PM who can list ten.
**Bad example:**
> "I use OKRs, RICE, JTBD, and opportunity solution trees." [Actual roadmap doc is a feature list with arbitrary priority labels.]
**Good example:**
> "I use RICE for quarterly prioritization. Last quarter's RICE scoring produced 3 changes from gut-feel ranking, including deferring feature-X and accelerating feature-Y. Artifact: link to scored backlog."
**How to catch it.** For every framework named, attach a concrete artifact showing it applied.
---
## Red Flag 7: "Influence" Claimed Without Decision Evidence
**Symptom.** Packet repeatedly uses words like "influenced", "drove alignment", "championed", but cannot point to a decision that turned on the PM's input.
**Why it's bad.** Influence is the most over-claimed PM capability. A promo committee that cannot trace a specific decision back to the PM's reasoning will discount the claim.
**Bad example:**
> "Drove alignment on Q3 priorities. Influenced engineering staffing."
**Good example:**
> "Q3 priorities: I authored the trade-off memo arguing for onboarding over checkout work. Decision meeting on March 14; my memo was the basis for the recommendation. Outcome: 2 engineers reallocated, onboarding hit activation goal."
**How to catch it.** Replace every "influenced" with "decision made on [date] in [forum] based on [my artifact]". If you cannot, the influence is imagined.
---
## Red Flag 8: Sandbagging the Self-Assessment
**Symptom.** PM under-rates themselves on every dimension. Manager and PM agree the work is at the higher level but PM hesitates to claim it.
**Why it's bad.** Sandbagging delays promotion (managers cannot promote someone who does not claim the bar) and creates an opening for less-capable PMs who self-promote loudly. It also signals to leadership that the PM is not ready to operate at the next level, even if they are.
**Bad example:**
> "Product Sense: APM. I just do my job, nothing special."
**Good example:**
> "Product Sense: PM. Evidence: I own feature decisions in my area, I push back on stakeholder requests with data, I have shipped 2 features this year that customers and the team agreed were thoughtfully designed. I would not yet claim Senior PM (no 0-to-1, no portfolio bets)."
**How to catch it.** Have a peer rate you using the same rubric. If their score is consistently higher than yours, you are sandbagging.
---
## Red Flag 9: Career Ladder as a Carrot Without a Calendar
**Symptom.** The PM and manager discuss the rubric, agree on gaps, and never set a follow-up date or promo target.
**Why it's bad.** Career conversations without a calendar are aspirations. Promotion is a process; without a target cycle, the PM drifts and the manager forgets. Most calibration committees want 6-12 months of evidence, so the calendar matters.
**Bad example:**
> "We agreed I'd work on strategy. Let's check in eventually."
**Good example:**
> "Target promo cycle: Q4 (8 months out). Pre-read draft to manager by month 5. Monthly checkpoint on growth plan. Skip-level shadow opportunity arranged for month 3."
**How to catch it.** A career conversation without a date is a daydream.
---
## Red Flag 10: Skip-Level Signal Ignored
**Symptom.** PM only discusses career with their direct manager. Skip-level (manager's manager) has never seen the PM in action and has no opinion on promo.
**Why it's bad.** Calibration committees include skip-levels. A skip-level who does not know the PM cannot advocate; promo gets stuck at "needs more visibility." A career strategy that excludes skip-levels is incomplete.
**Bad example:**
> "I talk to my manager monthly about my career. My skip-level has never seen my work."
**Good example:**
> "Quarterly skip-level 1:1 on my plate (manager arranged). I sent the strategy memo to my skip-level. I will present at a director-level forum in Q3 — manager will sponsor."
**How to catch it.** When did your skip-level last see your work directly? If never in the last 90 days, your visibility is too narrow.
---
## Red Flag 11: Ignoring Communication and Storytelling Dimensions
**Symptom.** PM has strong product sense and execution, but their written artifacts are dense, their presentations are tactical, and stakeholders are not aligned.
**Why it's bad.** The ladder explicitly includes communication. A Senior PM who cannot make their work legible to leadership does not get to Senior. Many PMs treat this dimension as soft skills; promo committees treat it as load-bearing.
**Bad example:**
> "Communication: I write good PRDs."
**Good example:**
> "Communication evidence: (a) Q3 strategy memo cited by CEO in all-hands, (b) post-mortem write-up adopted as company template, (c) 4 cross-functional teams use my onboarding spec as the canonical reference, (d) executive 1-pager I wrote replaced a 12-slide deck for the board."
**How to catch it.** Look at the artifacts in your packet. Are they readable by an executive who lacks context? If they need translation, your communication dimension is weak.
---
## Red Flag 12: Treating Promo as a Reward for Tenure
**Symptom.** Packet leans on "I have been here 2 years" rather than evidence of operating at the next level.
**Why it's bad.** Tenure is necessary but not sufficient. The bar is *demonstrated impact at the next level*. PMs who treat promo as a tenure reward are surprised when they get a "not yet" with no explanation — the explanation is that there is no evidence of next-level work.
**Bad example:**
> "I have been a PM for 2 years and want to be promoted to Senior PM."
**Good example:**
> "I am operating at Senior PM scope and impact (evidence in this packet). Tenure (2 years as PM) is within the normal range for the company; the case is impact-based."
**How to catch it.** Cut every tenure reference from the packet. Does the case still stand? If not, you are leaning on time-in-seat.
---
## Red Flag Quick Reference
| # | Anti-pattern | One-line check |
|---|---|---|
| 1 | Rubric Gaming | "What changed in the business because of this?" |
| 2 | Growth Plan with No Behavior Change | Each goal has an observable behavior shift? |
| 3 | Self-Assessment Inflation | Evidence justifies the score? |
| 4 | No Scope Evidence | Scope shift visible in first paragraph? |
| 5 | IC/Manager Track Confusion | Evidence matches the track you are on? |
| 6 | Frameworks Memorized, Not Applied | Concrete artifact per framework named? |
| 7 | "Influence" Without Decision | Decision date + forum + artifact named? |
| 8 | Sandbagging | Peer rating roughly matches yours? |
| 9 | No Promo Calendar | Target cycle + monthly checkpoint? |
| 10 | Skip-Level Invisible | Skip-level has seen your work in 90 days? |
| 11 | Communication Weakness Ignored | Artifacts readable by exec without context? |
| 12 | Promo as Tenure Reward | Case stands without any tenure reference? |
## Related Reading
- SKILL.md Troubleshooting section (for symptom -> root cause -> resolution)
- references/rubric.md (for the level-by-level definitions, if present)
- pm-1on1s/references/red-flags.md (for growth-conversation patterns)
- pm-interview-prep/references/red-flags.md (for adjacent calibration signals)
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 |