The Product Manager’s Atlas
The Career Ladder

The IC vs Manager Decision

4 min readΒ·771 words
career-ladderic-trackmanager-trackdecisionleveling

The single hardest career question in The Product Career Ladder, and the one PMs most often get wrong, usually by not treating it as a decision at all, but as a default. After Senior PM the ladder forks: stay a senior IC (Staff and Principal Product Manager) or become a manager (Group Product Manager). This note is how I coach people through that fork.

β–²The myth that ruins this decision

Management is not a promotion. It is a change of profession. Going from Senior PM to GPM is a lateral move into a different job, not a rung above the IC track (The IC and Manager Tracks are peers). Cagan puts it well: management is coaching plus staffing. If you take the manager fork to "get promoted," you'll end up doing a job you don't want, and doing it resentfully, which your team will feel. Pick the work, not the title.

#What each fork's job actually is

Strip away the titles and look at what you'd do all day:

IC track (Staff/Principal)Manager track (GPM+)
Your outputYour own work + the bar you raise across teamsYour team's work
Your dayStrategy, the hardest problems, the craft, cross-team influenceCoaching, hiring, 1:1s, unblocking, calibration
The dial you maxAmbiguity + influence (no headcount); see What Changes at Each LevelInfluence through people
You're judged onThe quality and reach of your thinkingWhether your people and org succeed
Core competencyStrategic Impact, Leading Without AuthorityTeam Leadership, The Manager as Coach

#The honest questions I ask

✦Where does your satisfaction actually come from?

Not where you think it should come from, but where it does. Two diagnostic questions cut through most of the fog:

  1. When a PM on your team ships something great that you coached but didn't build, is that a genuine high, or a hollow one? If it's a real high, the manager track will feed you. If you feel a pang of "but I didn't make it," respect that signal.
  2. Would you rather be the person with the deepest answer in the room, or the person who grew the people who have the answers? Neither is nobler. They're just different.

Other things I tell people to weigh honestly:

  • Management is mostly not product work. Roughly half a manager's time goes to coaching alone (The Manager as Coach), plus hiring, performance, and politics. If what you love is the craft, the discovery, the judgment, the shipping, the IC track keeps you in it.
  • The IC ceiling is real and high. A Principal/Distinguished PM shapes company strategy with zero reports. You are not trading away impact by staying IC. You're trading people-leverage for craft-and-influence-leverage.
  • Aptitude isn't appetite. I've seen brilliant ICs who'd be fine managers but would hate it, and average ICs who light up the moment they're coaching. Capability is necessary; wanting it is decisive.

#How to de-risk the choice

  • Try management before you commit. Mentor formally, lead an intern, run a workstream with borrowed people. Practice Coaching and Feedback and Leading Without Authority and notice how it feels. A "tour of duty" into management is reversible.
  • You can change your mind, both ways. Round-tripping the fork is normal, not failure. Better an honest IC than a resentful manager (and vice versa). The tracks are a fork, not a one-way door.
  • Decide on data, not drift. Don't let the next open req or a flattering title make the call. Use the diagnostic questions, then choose deliberately.
β„ΉWhat this means for managers leveling their people

If you manage PMs, do not push your best IC into management as the only reward for excellence. That's how you lose a great builder and gain a mediocre manager. Build a real senior IC track (Staff and Principal Product Manager) and reward both forks equally at Calibration and Promotion time. Talk about the fork before someone's at it, and see The Manager as Coach.

#Continue Reading