A framework for PM career growth: the three Ws

Executive overview

Most product managers conflate impact on the product with impact on their career — these are not the same thing. Career growth depends on three distinct axes: what you produce (outputs and outcomes), what you bring to the table (the quality of your artifacts and contributions), and your operating model (how you work with others).

The framework applies at every career stage. Seniors still need to ship outputs. New joiners haven't yet earned the right to set strategy.

The moment you stop controlling what you can control and start blaming what you can't, your career stalls.

The three Ws

• What you produce: outputs first (shipping, drafts, experiments), then outcomes (owning goals), then direction
• What you bring to the table: the quality of PRDs, product notes, strategy docs, briefs — your artifacts are your proof
• What's your operating model: raise difficult issues without being difficult to work with; surface important topics without drawing importance to yourself; get decisions made without making all the decisions yourself
• Early-career PMs should obsess over outputs, not strategy — execution is what teams need from new joiners
• Mid-senior and senior PMs must not abandon outputs; IC-level craft builds credibility at every level
• The operating model tenet is hardest to embody day-to-day and is the biggest differentiator at senior levels

Outputs vs. outcomes vs. direction

• An output is tangible, quick to define, and immediately useful — ranking content sources, preparing a brief, writing a first draft
• The mistake: jumping to outcomes while letting output quality drop
• As you grow, keep doing the IC work; it earns trust and keeps you grounded in execution
• Volunteering for leadership blockers (summit briefs, legal reviews, slide prep) is an underrated output play
• Strategy and vision rights are earned — new joiners, even senior ones, should prove craft first

What you bring to the table

• "Impact on impact": you contributed to a result, but can you prove it?
• Artifacts are the proof: PRD, product notes, strategy doc, design briefs, pre-sprint planning, Jira stories
• Four dimensions to demonstrate via artifacts: data and metrics, design and research, technology skills, strategy
• Weak artifacts — empty Jira titles, missing briefs, no pre-sprint planning — signal low contribution regardless of product success
• Quality over breadth: channelling inputs into strategic choices outperforms bringing arguments and pushback

Operating model and stakeholder relationships

• Bring conversations from emotional to logical space — the skill of de-escalation drives faster career growth
• Pushback that's seen as an obstacle ends careers; pushback that unblocks teams advances them
• "You are one part of the cog wheel, not the entire wheel"
• The PM is the only function that pairs with every other discipline — data, design, tech, strategy — and that unique cross-team view is the value

Why careers stall: three mindset traps

• Focus on what you control: early-career PMs obsess over craft; mid-senior PMs shift to blaming org, stakeholders, or opportunities — a dangerous drift
• Relationship with change: growth tracks rate of skill change; when learning slows, growth slows; benchmark yourself externally, not just within your team, to keep the gap visible
• Stories you tell yourself: "high agency" can excuse being brash; "hyper-collaborative" can excuse indecision — these self-labels become anti-signals
• Correcting the internal story is upstream of any framework or structure
• Seeing yourself as a learner is enabling even if it's not glamorous

Transitioning into product management

• Identify the two axes where you're weakest across: data, design/research, technology, strategy
• From design/research background: prioritise data or tech
• From data/tech background: prioritise design and research
• Once two of the three technical axes are demonstrated, move to strategy
• Going slower in transition pays dividends — avoid getting fast early and then stuck
• Strong product leaders accelerating the transition matter enormously

Skill axes for PM career development

• Data and metrics: level zero cannot define basic product metrics; level five could run a data startup
• Design and research: level zero identifies user problems; level five ties user problems to business goals
• Technology: ranges from no knowledge of HTTP/API to writing technical design documents
• Strategy: not corporate strategy — how to climb the mountain once the mountain is chosen; user segments, needs, sequencing
• Communication and collaboration: never finish at five; every new company, team, or culture resets the benchmark
• Organisational skills and community: PM as community enabler is especially critical for remote and distributed teams
• Pick one focus area at a time — improving data, design, and strategy simultaneously leads to overwhelm and no progress

Feedback and growth

• Feedback is only useful if you actually internalise it — the instinct is to dismiss criticism
• Map feedback to the eight axes; not all feedback is equally relevant to your growth priorities
• Fix the deepest deficits first — they give highest leverage
• Softer skills (communication, collaboration, community) are lifelong; technical axes have more defined endpoints
• Recalibrate self-assessment by working with people significantly better than you — it creates hunger, not despair