The IC and Manager Tracks
For the first three rungs of The Product Career Ladder, there's only one path. Everyone does the same job at rising altitude. Then, after Senior PM, the ladder forks, and a lot of careers get confused right here. So let me lay the two tracks out plainly.
#The fork, and where it opens
Up to and including Senior PM, you're a pure individual contributor and there's nothing to choose. The fork opens because a strong Senior PM has more value to give than one product area can absorb. You can scale that value two ways: wider influence as an IC, or leverage through a team as a manager. That's the decision in The IC vs Manager Decision.
┌─► Staff / Principal PM ─► (Distinguished) [IC: scale influence]
APM ─► PM ─► Senior PM ──►┤
└─► Group PM ─► Director ─► VP ─► CPO [Mgr: scale through people]#The two tracks, side by side
| IC track | Manager track | |
|---|---|---|
| Rungs above Senior | Staff → Principal → Distinguished | GPM → Director → VP → CPO/SVP |
| What you scale | Depth and breadth of influence | Output through other people |
| Output is | Your own work + the bar you raise | Your team's work |
| Core competency that lights up | Strategic Impact, Product Vision and Roadmapping | Team Leadership |
| Headcount? | No direct reports | Direct (then indirect) reports |
| Mastery stage (see The Six Stages of Mastery) | SME → Master → Thought Leader, applied to the craft | SME → Master → Thought Leader, applied to people and org |
#They are peers, not a ranking
This is the point I hammer hardest. A Staff PM and a GPM sit at the same level: same compensation band, same influence expectation, with a different shape of contribution. The senior IC track is not where you go when you "can't" manage. Some of the highest-leverage product people I've worked with never managed a soul. They shaped strategy across an entire portfolio and made every team around them better. Treating the IC ceiling as lower than the manager ceiling is how companies lose their best builders.
On the IC track, the twelve competencies keep escalating but Team Leadership expresses as influence and coaching without authority (Leading Without Authority) rather than formal people management. On the manager track, Team Leadership becomes the dominant competency, and your evaluation increasingly rests on whether your team succeeds, not whether you ship. See The Manager as Coach.
Myth 1: "Management is the promotion." It isn't. It's a lateral move into a different job, detailed in The IC vs Manager Decision. Myth 2: "You can't go back." You can, and I've watched great PMs flip both ways more than once. The tracks are a fork in the road, not a one-way door.
#How leveling works across the fork
Both tracks are scored against the same twelve competencies. What changes is the altitude and which competencies dominate. The full grid lives in The Master Competency Matrix, and the per-rung cheat sheet is Competency Quick Reference by Level. Promotions on either track are gated the same way, through Score-Gated Leveling and Calibration and Promotion.
#Continue Reading
- The IC vs Manager Decision for how to actually choose your fork.
- Staff and Principal Product Manager for where the IC track goes.
- Group Product Manager for the first rung of the manager track.
- What Changes at Each Level for the four dials that escalate on both tracks.
- Team Leadership for the competency that diverges at the fork.
- The Manager as Coach for what the manager track is really made of.
- Competency Quick Reference by Level for both tracks, rung by rung.