Rewrite a PM career ladder so leveling stops being subjective

Career Ladders Either Make Leveling Defensible or They Make It a Politics Problem

A PM career ladder that lists abstract attributes like "demonstrates strategic thinking" or "shows leadership" cannot resolve a calibration debate. Every PM in the org meets those bars on a generous reading and fails them on a strict reading. The result is leveling by tenure, by likability, or by who has the loudest manager. Rewriting the ladder around four observable axes with one-line rubrics per level converts leveling from politics into evidence.

Reforge's writing on PM career ladders makes the central case: ladders fail when they describe attributes instead of behaviors. The fix is to describe what a PM at level N does in observable terms.

Why four axes, not seven

Most ladders bloat to six or seven axes (impact, complexity, communication, leadership, technical depth, strategic thinking, customer focus). The bloat hides the core question: what does this PM actually do that another PM does not?

Four axes carry 90 percent of the leveling discussion:

• Problem complexity. The hardest problem the PM owns. A PM I owns well-scoped features; a Principal owns ambiguous strategic problems with many right answers.
• Scope of impact. Team, area, business unit, company. The number of people whose work depends on the PM's decisions.
• Autonomy. How much guidance the PM needs to operate. The lower the level, the more they need product strategy handed to them; the higher, the more they shape the strategy.
• Leadership. How much they grow others. PM II might mentor an APM; Principal sets the bar across an org.

SVPG's writing on the PM job and the empowered teams essay provide the deeper context for why the four axes capture leveling: the PM job is to drive outcomes through influence, and outcomes scale with problem complexity, scope, autonomy, and leadership.

How the Rewrite a PM career ladder prompt works

Step 1 picks the four axes. The prompt resists adding a fifth axis. Most extra axes are confounded with the first four; "communication" usually shows up inside scope and leadership.

Step 2 writes the one-line rubric per cell. Twenty-four cells (4 axes by 6 levels). Each cell describes observable behavior in a single sentence. Verbs like "owns," "decides," "ships," "mentors," "defines," not "demonstrates" or "shows." A reader should be able to identify the level from the cell content alone.

Step 3 anchors each level with two real projects. Abstract definitions slide; real projects do not. The team picks recent work and explains why each project sits where it does on each axis. New hires use the anchors to calibrate.

Step 4 calibrates against current PMs. Place each PM on the rubric blind, then compare to current level. Expect 10-20 percent disagreement. That is the size of the leveling debt the ladder pays down. Disagreements get a written case and go through the new calibration ritual.

Step 5 writes promotion criteria. Specific observable outcomes per level transition: problems led end to end, decisions made independently, people grown, the single signal that means readiness. SVPG's writing on the PM vs PO debate is useful as a sanity check; promotion criteria that look like PO criteria (managing the backlog) are likely capturing the wrong work.

Step 6 installs the calibration ritual. Quarterly, borderline PMs only, written cases, cross-team panel, blind reads, documented outcomes. The ritual matters more than the rubric. A great rubric without a calibration ritual decays in two cycles.

What changes in the team after the rewrite

Three predictable shifts:

• Calibration meetings get shorter. A written case against a one-line rubric resolves in 30 minutes; the same debate against attribute language took three hours.
• Promotion debt becomes visible. PMs who have been ready for months are now identifiable. Some of them will be promoted; some will be told what is missing.
• Hiring bar becomes consistent. Interview rubrics align with the ladder, so a Senior hire from outside has the same expectations as a Senior promoted from within.

First Round Review collects writing on calibration practices that align with this approach: the document carries the meeting, not the meeting carries the document.

When to use it

• Calibration debates last hours and rarely produce confident outcomes.
• The same kind of work is leveled differently across teams in the same org.
• A new VP of product is joining and wants a defensible ladder before the first calibration cycle.
• High-performing PMs are leaving because the path to promotion is unclear.
• A reorg is creating new manager-of-managers roles and the ladder needs to scale to a larger org.

Common pitfalls

• Attribute language. "Demonstrates strategic thinking" cannot be calibrated. Use verbs and outcomes.
• More than four axes. Extra axes confuse calibration without adding signal.
• Rubric without ritual. A great rubric without quarterly written calibration decays in two cycles.

Sources

• Career ladders for product management - Reforge
• The product manager job - Silicon Valley Product Group
• The product manager vs product owner revisited - Silicon Valley Product Group
• Empowered product teams - Silicon Valley Product Group
• First Round Review - First Round