What Changes at Each Level
If the competencies don't change as you climb The Product Career Ladder, and I argue in the hub that they don't, then something has to. This note names that something. There are exactly four dials, and every promotion is a turn of some combination of them.
Scope · Autonomy · Ambiguity · Influence. Master these and you can read any ladder, at any company, regardless of how the titles are spelled. They're the machinery under The Six Stages of Mastery.
#The four dials
| Axis | The question it answers | Low → High |
|---|---|---|
| Scope | How big is what you own? | One feature → a product area → a portfolio → a business → the company |
| Autonomy | How much do you decide alone? | Execute a defined task → set your own plan → set the team's strategy → set company direction |
| Ambiguity | How undefined is the problem when it reaches you? | Problem fully framed → ill-defined → you define the problem |
| Influence | How far does your impact reach? | Your own work → your team → the org → the market/field |
#The dials, rung by rung
| Level | Scope | Autonomy | Ambiguity | Influence |
|---|---|---|---|---|
| APM | A feature | Works under supervision | Problem handed over framed | Self |
| PM | A product area | Sets own priorities | Frames the work themselves | Begins to reach the team |
| Senior | Complex / interrelated areas | Fully independent; role model | Brings clarity to ill-defined work | Across the team |
| Staff/Principal | Cross-team initiatives | Defines context for others | Tackles the most ambiguous problems | Org-wide (no headcount) |
| GPM | A group, through PMs | Owns the team's plan | Absorbs ambiguity for the team | The team's output |
| Director/VP | A domain / business line, through managers | Sets functional strategy | Defines which problems matter | The function / org culture |
| CPO | The company | Co-sets company strategy | Defines the problem space itself | The company / the market |
#The fork, read through the dials
This is the cleanest way to see why the two tracks are peers, not a ranking:
After Senior PM, both tracks keep climbing, but on different axes. The IC track (Staff and Principal Product Manager) scales ambiguity and influence to their ceiling without adding headcount. A Principal's reach is enormous, yet they manage nobody. The manager track (Group Product Manager → up) scales scope and influence through people, by managing, then managing managers. Neither is "higher." They turn different dials. Choosing which is The IC vs Manager Decision.
#Why this is the most useful note in the domain
Two payoffs I lean on constantly:
- It diagnoses promotion-readiness. When someone wants the next level, I don't ask "are they good?" I ask which dial they need to turn and whether they've shown it. Most "ready for Senior" PMs are great at their current scope but haven't yet proven they can operate in higher ambiguity. That's the gap, named precisely. This is the substance behind Calibration and Promotion and Score-Gated Leveling.
- It explains why people fail after promotion. Almost always, they turned one dial (usually scope) but not another (usually autonomy or ambiguity). The new GPM who still does the work didn't turn the influence-through-people dial. The new VP who still executes didn't turn autonomy/strategy. (Identifying Growth Areas.)
A promotion is rarely all four dials at once. Senior→Staff cranks ambiguity and influence hard while scope barely moves. Senior→GPM cranks influence-through-people while the craft dials hold. Mistaking "more scope" for "promoted" is how companies over-level builders into the wrong jobs.
#Continue Reading
- The Six Stages of Mastery for the progression these dials drive.
- The IC vs Manager Decision for which dials each track maxes out.
- The Product Career Ladder for the map these axes describe.
- Calibration and Promotion for using the dials to judge readiness.
- Score-Gated Leveling for the gate the dials feed.
- Identifying Growth Areas for finding the dial you haven't turned.