09 · Career Growth: IC to Director/VP¶
Product careers are unusually badly signposted. Engineers have a visible ladder with an obvious IC track; sales has a number. Product has neither, so most PMs advance by doing more of what got them here and are surprised when it stops working. It stops working because each level is a different job, not a bigger one, and the behaviour that earned the last promotion is frequently the behaviour blocking the next.
The pattern is consistent enough to state as a rule: at every transition, the thing you are best at becomes the thing you must do less of. The Senior PM promoted for exceptional specs becomes a Group PM who must stop writing them. The Director promoted for decisive judgement becomes a VP whose judgement must be exercised through other people or not at all.
This module covers the transitions, how promotion decisions are actually made at this level, what the packet looks like, what the money looks like, and when the right move is to leave.
The transitions¶
| Transition | The real change | Must stop | New skill | Failure mode |
|---|---|---|---|---|
| PM → Senior PM | From executing a defined problem to choosing which problem | Waiting to be assigned | Judgement under ambiguity | Staying busy on well-defined work |
| Senior PM → Staff / Group PM | From your product to a portfolio, or to a problem too hard for one team | Doing the PM work yourself | Influence without authority; developing others | Becoming a super-PM across three teams |
| Group PM → Director | From influencing to owning outcomes and people | Being the best PM in the room | Hiring, performance management, strategy for an area | Managing the work instead of the people |
| Director → VP | From an area to the whole org and the company's product strategy | Making the calls your Directors should make | Org design, exec peering, board communication | Becoming a scheduler with no product point of view |
| VP → CPO | From product org to company strategy alongside the CEO | Thinking of product as your function | Company-level allocation, commercial ownership | Advocating for product against the company |
The two hardest are the second and the fourth, for the same reason: both require abandoning the thing you are visibly excellent at, and both offer no short-term reward for doing so. The Staff PM who stops writing specs looks, for about two quarters, like someone who has stopped working.
How promotion actually works at this level¶
Below Senior PM, promotion is roughly a performance judgement. Above it, it is a business decision constrained by structure, and understanding that changes how you approach it.
| Factor | Weight above Senior PM | What it means |
|---|---|---|
| Scope available | Very high | You cannot be promoted to Director if there is no group to run |
| Already operating at the level | Very high | Nobody is promoted into a level as an incentive to reach it |
| Sponsorship | High | Someone senior arguing for you in a room you are not in |
| Visible artefacts | High | Strategy docs, org designs, hiring outcomes others can point to |
| Peer perception | High | Calibration is a room of leaders; your reputation is voting |
| Performance in role | Necessary, not sufficient | Excellence at your current level is table stakes |
| Tenure | Low | And should be zero |
Two consequences most people learn too late:
- Scope is granted before the title, always. The sequence is: you take on the harder problem, you operate at the level for two or three quarters, then the title follows. Waiting for the title before operating at the level is the most common self-inflicted career stall in product.
- Sponsorship is different from mentorship and more valuable. A mentor gives you advice. A sponsor spends their own credibility arguing for you in calibration. You get sponsors by making them look right — deliver something visible that they backed.
The promotion packet¶
Whether or not your company uses a formal packet, write one. It clarifies the gap even when nobody reads it, and if a sponsor is going to argue for you in a room, they need the argument written down.
| Section | Content | Length | Test |
|---|---|---|---|
| Scope claim | The scope you already run, stated in the next level's terms | 3 lines | Would your manager's manager recognise it? |
| Outcomes | 3–4 results with before/after numbers and your specific contribution | 1 page | Could a sceptic attribute these to someone else? |
| Level evidence | For each dimension of the matrix, one concrete example | 1 page | Does each map to a written competency? |
| Multiplier evidence | People developed, standards raised, artefacts others copied | Half page | The section that decides Director and above |
| Peer testimony | Quotes from engineering and design partners | Half page | Are they specific, or generically warm? |
| Gap | What you are not yet good at, and the plan | 3 lines | Its absence reads as low self-awareness |
The multiplier section is the one that decides it. Above Senior PM, companies are not buying more of your output; they are buying the output of people you make better. Three PMs who improved measurably under your guidance outweighs any feature you shipped.
The gap section is counter-intuitive and worth writing anyway. A packet with no acknowledged weakness reads as a person who does not know themselves, and the calibration room will supply the weakness for you, uncontested and probably worse than the one you would have named.
What the money looks like¶
Comp shape matters more than any specific number, and the shape is the same almost everywhere: cash grows roughly linearly, equity grows disproportionately, and the mix flips.
Illustrative bands at a US-based company at ListUp's stage — $52.4M ARR, private, venture-backed. Treat these as a shape, not a benchmark; geography, sector and stage move them substantially.
| Level | Base | Target bonus | Cash | Annual equity | Total | Equity share | Step |
|---|---|---|---|---|---|---|---|
| PM | $145,000 | 15% | $166,750 | $35,000 | $201,750 | 17.3% | — |
| Senior PM | $175,000 | 15% | $201,250 | $60,000 | $261,250 | 23.0% | +29.5% |
| Staff / Group PM | $205,000 | 20% | $246,000 | $110,000 | $356,000 | 30.9% | +36.3% |
| Director | $240,000 | 25% | $300,000 | $180,000 | $480,000 | 37.5% | +34.8% |
| VP Product | $300,000 | 40% | $420,000 | $350,000 | $770,000 | 45.5% | +60.4% |
| CPO | $360,000 | 50% | $540,000 | $600,000 | $1,140,000 | 52.6% | +48.1% |
Three things this table says that salary conversations usually miss:
- Equity share rises from 17.3% to 52.6% of total comp. By VP, most of your compensation is a bet on the company's outcome, which means choosing the company becomes a bigger financial decision than negotiating the offer.
- The step into VP is the largest, at +60.4%, and it is also where the role changes most and the failure rate is highest. The premium is priced risk, not seniority.
- Base is the smallest lever above Director. Negotiating $15,000 of base at VP is 2% of total comp; negotiating refresh cadence, acceleration on change of control, and the size of the initial grant is worth multiples of it. Most people spend their negotiating energy on the wrong line.
Ask about the refresh policy before you accept anything. A large initial grant with no refresh is a four-year package that decays to nothing in year three, and it is the most common way senior product hires end up underwater without noticing.
Worked example — a Group PM going for Director¶
Situation. Priya runs ListUp's Console group: two squads, 13 engineers, the $10.5M agency line. She has operated as a Director in everything but title for three quarters. She has been told "keep doing what you're doing", which is the most common and least useful feedback in product.
What she assembled:
| Section | Evidence |
|---|---|
| Scope | Two squads, 13 engineers, 214 agencies, $10.5M ARR line, growing 62% |
| Outcome 1 | Agency NRR 108% → 121% over four quarters, driven by the approvals workflow she chose over three louder alternatives |
| Outcome 2 | Console attach among direct accounts 14% → 21.2%; $2.1M incremental ARR from two shipped workflows with 4 engineers |
| Outcome 3 | Cross-group dependencies for Console cut from 11 to 3 per quarter after she proposed the platform contract |
| Multiplier | Hired 2 PMs; one promoted to Senior; her launch template was adopted by all four groups |
| Multiplier | Ran the monthly product review for two quarters while the VP was on leave |
| Peer testimony | Console engineering manager and design lead, both specific about her handling of a contested pricing decision |
| Gap | Has never managed a manager, and has never run a performance case to conclusion |
What actually happened, and why it is instructive. She was not promoted in the first cycle. The stated reason was the gap she had named herself — no experience managing managers. The VP's response was not "keep doing what you're doing" but a specific, bounded assignment: take the Onboarding squad's PM lead as a dotted-line report for two quarters, and own one performance case end to end with HR support.
She was promoted the following cycle.
The lesson is not that naming the gap delayed her. It is that naming the gap converted an unanswerable question into a bounded assignment with a finish line. Without it the feedback stays at "keep doing what you're doing", which can be repeated indefinitely because it identifies nothing. Candidates who hide their gap do not remove it; they remove their ability to close it on a schedule.
When to stay and when to leave¶
| Situation | Signal | Move |
|---|---|---|
| Operating a level up for 3+ quarters, no path named | Structural, not performance | Ask for the specific gap and a date. No answer twice → leave |
| No scope available above you | The org has no room, regardless of your merit | Leave, or take a lateral into a growing area |
| Your manager is not a sponsor | Nobody argues for you in calibration | Find a sponsor internally, or move |
| You have stopped learning | Two quarters with no new hard problem | Take on something you might fail at, internally first |
| The company's product is not working | Your outcomes will be bad regardless | Leave before the results are on your record |
| You are the strongest product person in the building | Nobody to learn from | Move, or hire above your own comfort |
| Bored, but the company is compounding | Common at 2–3 years | Usually stay; boredom near a growing business is a scope problem, not a company problem |
The most reliable reason to leave is the absence of a next hard problem, and the least reliable is a single bad quarter. Product outcomes lag decisions by six to eighteen months; leaving during the lag means you never learn whether your judgement was good.
Note the asymmetry that people ignore: title inflation at a shrinking company is worthless and title patience at a compounding one is enormously valuable, because the equity share of comp above Director means the company's trajectory dominates your title's. A Director at a company that triples out-earns a VP at one that flattens.
The senior loop, from the other side¶
Having run these loops (Level 4, Module 1), here is what Director and VP interviews actually assess:
| Stage | What is really being tested | How candidates fail |
|---|---|---|
| Strategy exercise | Can you diagnose, not just plan? | Presenting a roadmap when asked for a strategy |
| Org design | Do you understand that structure is a choice with costs? | Drawing boxes with no trade-offs named |
| Metrics deep-dive | Do you know your own numbers, unaided? | Vagueness about results they claim credit for |
| Hiring and performance | Have you actually managed someone out? | Never having had a hard conversation |
| Exec peer interview | Would the CTO and CRO want you in the room? | Advocating for product against the company |
| Reference checks | Everything | Being unable to name a peer who would speak candidly |
The single most common failure at VP level is answering a strategy question with a plan. "What would you do in your first 90 days" is not asking for a list of activities; it is asking what you would need to learn and what decision that learning would inform.
How It Actually Works: the equity-vesting math and signalling mechanics behind career progression¶
Why equity share compounds faster than base as a mechanical consequence
of how vesting is priced, not just company generosity. A standard grant
vests over four years, so each year's equity comp is a claim on 1/4 of a
grant priced at issuance — and each subsequent level's grant is issued at a
later valuation, typically higher than the last. If the company's valuation
grows at rate g per year and each level's grant is sized as a multiple of
current cash comp, total equity value scales with both the increasing grant
size and the compounding valuation base: equity_value ≈ grant_size ×
(1+g)^years_held. This is why the equity share climbs geometrically
(17.3%→52.6%) rather than linearly with base salary (which merely scales
arithmetically level to level) — you're not just being paid more, you're
being paid more in an asset that is itself compounding, which is exactly
why "refresh cadence" matters more than base at senior levels: a grant with
no refresh stops compounding the moment the original four-year clock runs
out, while base and bonus continue accruing regardless.
The VP comp step (+60.4%) is a risk premium, and it prices a specific, measurable failure rate. In compensation theory, a step-up that exceeds what a role's marginal output alone would justify functions like a risk premium — it compensates for the higher variance of outcomes at that level (a VP who fails is usually replaced within 12–18 months; a Senior PM who underperforms usually is coached first). The org-design module's own observation that VP failure often looks like "becoming a scheduler" is the concrete failure mode this premium is pricing: the company is paying extra specifically because a meaningful fraction of VP hires and promotions do not succeed at the transition, and the premium has to be large enough to attract candidates willing to bear that personal risk.
Why naming your own gap changes the outcome — it converts private information into a testable claim. Calibration committees operate under incomplete information: they cannot directly observe your competency, only proxies (packet, testimony, track record). A candidate who omits a known weakness leaves the committee to infer it from noisier signals, and inference under uncertainty defaults to the most available negative data point in the room, often worse and less specific than the truth. By contrast, self-naming the gap and pairing it with a bounded assignment (Priya's dotted-line manager-of-managers stint) converts an open-ended, unfalsifiable judgment ("is she ready?") into a falsifiable one with a fixed evaluation window — the same falsifier discipline used for board asks and kill criteria elsewhere in this level, applied to a promotion decision. This is mechanically why "keep doing what you're doing" is unfalsifiable and can recur indefinitely: it names no specific missing skill and sets no evaluation date, so there is no evidence threshold that would ever resolve it either way.
Exercise¶
- Name your current transition and write the one behaviour you are excellent at that you now need to do less of.
- Write the promotion packet for the level above you, including the multiplier section and the gap section. Do this even if no process requires it.
- Test the multiplier section: name three people who are measurably better because of you, and what specifically changed.
- Identify your sponsor — the person who would argue for you in a room you are not in. If you cannot name them, that is this quarter's work.
- Ask for the specific gap. Not "what should I work on" but "what is the one thing that would make this a yes, and when would we review it?" Push until you get something bounded.
- Audit your comp by shape, not by base: cash, equity, equity share of total, and the refresh policy. Find out the refresh policy today.
- Take one bounded assignment above your level this quarter, ideally one you might fail at, and tell your manager that is what it is for.
- Run the stay-or-leave table honestly against your situation and write the answer down with a review date.
- Practise the strategy question — "what is your product strategy, in one page" — for your current product, and check whether what you wrote is a diagnosis or a plan.