How PMs Really Get Promoted
The framework that makes career growth transparent, fair, and achievable.
I turned down a six-figure salary in Europe for a Head of Product role.
The money was tempting, but their promotion criteria made my stomach turn.
They measured PM performance by story points delivered. Pure output, zero outcome focus. Associate PMs needed 25 story points. Mid-level targeted 40. Seniors had to hit 50.
Think about that backwards logic: The Associate PM needs senior support to progress, but the Senior PM can't provide it because they're too busy chasing more story points than everyone else.
This creates competition where collaboration is needed. It punishes the very behaviors that create great product leaders.
I’m done with confusion about career progression. And I imagine you’re too.
Now, let me set expectations.
Most readers won’t get to the end of this episode. I get it. We long for shortcuts and instant gratification. The hard truth is that growth requires effort and strategic thinking.
This post is a serious one and will require you to put in some work. I will give you precise guidance, and that will help you grow, yet there is no shortcut.
Before we dive into that, we need to address what's been bothering me lately about the PM career.
The AI PM Nonsense
People keep asking the wrong question: "Are you a PM or an AI PM?"
This question is as ridiculous as asking, "Are you a driver or an electric car driver?"
A PM is a PM. Period.
Your core mission never changes: identify what's worth solving and create value for customers and the business. AI is just another technology in your toolkit. It's a means to an end, not the end itself.
"AI PM" has become a buzzword that helps people negotiate higher salaries. It suggests you can magically accelerate value creation, but here's where it gets dangerous: it implies you can ship more stuff faster without understanding what actually matters.
Yes, you should understand AI and explore it. I love Claude, and I've been playing with Lovable, Bolt.new, and other tools. However, I use them to accelerate learning, not to replace critical thinking, which is yours, not AI's.
Whether you're using Excel spreadsheets or AI-powered analytics, whether you're sketching wireframes or generating prototypes with AI, the core question remains: Are you creating value that matters?
Now, I stop with my ventilation. Sorry, I had to do that before clarifying the career progression. It’s so much noise that distracts us from what matters. I hope you got the point.
Let’s take a two-step approach to career progression: understanding the level and the expected behaviors for each level.
The Real Problem with PM Career Progression
Most organizations have zero transparency about what it actually takes to get promoted. You're left guessing, playing politics, or hoping someone notices your hard work.
When I ask PMs "What do you need to do to reach the next level?" I get blank stares. When I ask their managers the same question, I get vague responses about "demonstrating leadership" or "taking more ownership."
What the heck is that? This truly disturbs me because it's unfair.
Stick with me, and I will help you get out of this trap.
Nobody knows what it takes to grow. So growth becomes about who you please and how often you do it. That approach breeds frustration and kills motivation.
After coaching dozens of PMs through promotions, I've learned something critical: the more junior the team member, the more guidance they need from seniors to ship value. But most organizations reward individual output instead of collective growth.
How Transparency Changes Everything
I've developed a framework that brings clarity to PM career progression. It's built on two fundamental dimensions:
Value Creation Ability: How effectively can you identify problems worth solving and deliver solutions that matter?
Independence: How autonomously can you operate without constant guidance or approval?
These two factors create four distinct quadrants that define PM levels:
Associate PM: Low independence, developing value creation skills
Needs significant guidance and mentorship
Learning to identify valuable problems
Building foundational product skills
Success measured by growth rate, not output
Mid-Level PM: Growing independence with solid value creation
Can work autonomously on defined problems
Demonstrates consistent value delivery
Seeks guidance for strategic decisions
Balances execution with learning
Senior PM: High independence with proven value creation, plus one crucial difference
Operates autonomously on complex problems
Can elevate junior PMs to the next level
Success includes team development, not just personal results
Teaches while executing
Lead PM: Master both dimensions, with a leadership multiplier
Highest independence and value creation ability
Creates the environment for entire PM teams to thrive
Success measured by organizational PM capability growth
Builds systems that develop others
This isn't just theory.
I've used this matrix at several companies to create transparent growth paths. The results speak for themselves: PMs know exactly what behaviors to develop, managers can give specific feedback, and promotions become merit-based instead of political.
Why This Framework Works
Traditional PM career ladders focus on scope and seniority. "Senior PMs work on bigger features." "Leads manage more people."
That misses the point entirely. You already know what I call that. Bullshit.
The best Senior PMs I've worked with aren't just better at their own work. They make everyone around them better.
The best Lead PMs don't just manage people - they create environments where PMs can thrive without constant oversight.
Now, a drop mic for you. Steal this one: Your value isn't just what you deliver. It's what you enable others to deliver.
The CLAIM Framework: Your Roadmap to the Next Level
The matrix gives you direction. The CLAIM framework gives you the specific behaviors to develop at each level.
CLAIM stands for:
Communication
Leadership
Alignment
Impact
Methods
The order matters.
Most teams start with Methods (frameworks, processes, tools) and ignore everything else. That's backwards. Methods are means to an end, not the end itself.
You can download the full framework for PMs, Designers, and SWE:
Note: Start with this, but adapt it to your specific scenario. We will continue this episode to provide you with more guidance.
The CLAIM Framework in Action
Instead of listing behaviors (all of them in the above links), let me show you how each level handles real PM challenges.
C - Communication: Crisis Response
The Scenario: The team just missed an important release date, which created friction with customers and sales. The CEO is furious and asking questions.
Question for you: How would you act with the presented scenario?
Associate: Sends long Slack messages to everyone explaining technical debt. Gets defensive when the tech lead gives feedback about unrealistic timelines. Rambles in meetings.
Mid-Level: Calls the tech lead first, then sends a concise update with facts. Listens to feedback but takes it personally. Clear in meetings, but when someone asks for new stuff, the default answer is yes, and you will regret it later
Senior: Sets up targeted calls, chooses channels based on stakeholder needs. Asks strategic questions that reframe the problem. Uses crisis to teach junior PM communication skills.
Lead: Builds systems that scale communication best practices. Use every opportunity to give feedback and help people practice it. Continuously look beyond what’s said.
L - Leadership: Feature Prioritization
The Scenario: Sales wants the beautiful AI feature the competitor just launched, Support wants the chatbot that will give them back time, and Engineering thinks both are wrong.
Question for you: How do you handle such conflicting situations?
Associate: Tries to please everyone. "Maybe we can do both if we work harder?" Can't facilitate conflicting viewpoints.
Mid-Level: Facilitates team discussion, links decisions to company strategy with manager's help. Sets goals but needs senior guidance.
Senior: Uses data to guide decision, facilitates cross-functional alignment. Sets clear goals that everyone understands. Develops junior PM's decision-making skills through coaching.
Lead: Creates decision-making framework used across product teams. Facilitates org-wide strategy sessions. Builds systems that develop leadership capabilities at scale.
A - Alignment: Conflicting Roadmaps
The Scenario: Three different teams have goals that compete for the same engineering people. Oh, that sucks, but that’s the product life, isn’t it?
Question for you: How do you reach alignment when people expect you to please everyone?
Associate: Gets overwhelmed by competing goals. Focuses only on immediate team needs. Struggles to see the bigger picture.
Mid-Level: Builds alignment within a defined opportunity. Navigates competing goals with manager guidance. Collaborate with immediate stakeholders effectively.
Senior: Aligns multiple teams around shared outcomes. Resolves conflicts through strategic thinking. Teaches junior PMs alignment techniques while executing.
Lead: Creates alignment systems that work without constant intervention. Aligns leadership on long-term vision. Builds organizational capabilities for sustained alignment.
I - Impact: Measuring Success
The Scenario: Feature shipped 3 months ago. Forgotten, valuable, or just another AI stuff nobody cares about?
Question for you: How do you measure the impact of your work?
Associate: Points to download numbers and user signups (output metrics). Needs help understanding what business impact actually means.
Mid-Level: Balances downloads with retention and engagement. Connects feature performance to business results. Tracks meaningful metrics independently.
Senior: Optimizes for strategic outcomes, not just feature success. Uses insights to influence broader product strategy. Teaches measurement thinking to team members.
Lead: Creates measurement frameworks adopted by multiple teams. Influences the company-wide approach to impact measurement. Builds organizational capability for outcome focus.
M - Methods: Process Breakdown
The Scenario: Scrum isn't working (has that ever worked?) The team is frustrated with the endless ceremonies and the lack of time to work (classic complaint).
Question for you: How do you adapt tools & frameworks?
Associate: Follows the process religiously even when it's not working. Needs guidance to adapt. "But the Scrum guide says..."
Mid-Level: Adapts framework to team context. Balances process with pragmatism. Knows when to bend rules but unsure how far.
Senior: Creates a custom approach for the team's unique situation. Teaches method selection and helps team understand the "why" behind frameworks.
Lead: Designs org-wide process improvements. Creates learning systems around method effectiveness. Builds capability for continuous process evolution.
The Pattern: Each level handles the same challenge with increasing strategic impact and development focus.
How to Use This Framework
The CLAIM assessment isn't just theory. It’s about action.
Now, I must be honest with you, if you got here. Great! Most readers won’t get this far. It’s alright, I cannot help those looking for shortcuts. This takes time, now are you willing to invest that time?
If you’re serious about your career, here's your implementation roadmap:
