What is the difference between a PM and a senior PM?

The core difference is evidence of judgment at a broader scope. A PM demonstrates execution against a defined roadmap. A senior PM also demonstrates ownership of the roadmap itself: the decisions behind what was built, what was not built, and why. The level shift is from executing well to deciding well, and being able to articulate both.

How do I know if I am ready for a senior PM role?

Ask whether you can name a specific decision, not a process. Not "I improved prioritization" but a single call: the option you rejected, the tradeoff you made, what happened after. If every example you can think of ends cleanly with no tension or cost, that is a sign the examples are either not specific enough or not at senior-level scope yet.

Does confidence predict senior PM readiness?

Only weakly. Most people asking this question are either better at the job than they feel, or less prepared to prove it than they assume. Confidence reflects how you feel about your experience. Readiness reflects whether that experience, when described specifically and tested with a follow-up question, holds up as evidence of operating at the next level.

SELF-ASSESSMENT

Am I ready for a senior product manager role?

The honest answer is rarely about how confident you feel. It is about what you can point to: specific decisions, specific tradeoffs, specific moments where the evidence changed your mind. Confidence and readiness are only weakly related, and most people asking this question are better at the job than they think, or worse prepared to prove it than they realize. Here is what actually separates the two.

Key takeaways

Senior PM readiness is about specific evidence, not how confident you feel.
Strong signal: naming a real decision (the alternative you rejected, the reasoning, what happened), not a general trend.
Strong signal: changing course because evidence contradicted your assumption, on your own judgment, not because a manager overruled you.
Weak signal: "I led cross-functional alignment" with no specific disagreement you resolved.
The gap is narrow: most people asking this are better at the job than they think, but less prepared to prove it than they realize.

Next action

Assess your readiness against real evidence

See what your product experience already demonstrates and what evidence would close the next gap.

Assess my readiness See a sample report

Checklist

Email me the Product Promotion Readiness Checklist

You will receive a link to the checklist page for pressure-testing whether your examples show next-level scope, judgment, and impact.

Signals that hold up under a follow-up question

You can name a specific decision, not a general trend

Not "I improved our prioritization process": a single, dated decision, the option you rejected, the reasoning, and what happened after.

You changed course because of evidence, not pressure

A senior-level track record includes at least one real reversal, a plan you defended, then abandoned once new data contradicted it, on your own judgment rather than because a manager overruled you.

Your examples span more than one team or system

If every strong example comes from the same product area with the same stakeholders, that's real evidence of depth, but not yet evidence of the broader scope a senior role usually adds.

You can separate what you were told to build from what you decided to build

Execution against someone else’s roadmap is a real skill. Readiness for the next level usually also requires evidence of the roadmap itself being your call.

What “not yet ready” usually sounds like

This is not the same as being a weak PM. It is the specific, narrow gap between executing well and having proof of operating at the next level:

"I led cross-functional alignment on X" with no specific disagreement you can describe resolving
Every prioritization example ends the same way: the plan worked, with no tension, tradeoff, or cost
Influence examples rely on your title or role, not on a specific conversation that changed someone’s mind
Technical or commercial claims that sound rehearsed rather than something you could be asked a follow-up question about

Why this is hard to judge about yourself

You remember your own reasoning better than you remember whether it was actually sound at the time. Hindsight makes every past decision look more deliberate than it was. You also tend to overweight effort you personally felt ("I worked so hard on this") over what an outside evaluator would actually count as evidence. Neither is a character flaw. It is just why a structured, evidence-first conversation tends to surface a clearer picture than sitting down and asking yourself the question directly.

Product Assessment’s adaptive interview asks about real decisions, probes the ones that sound rehearsed, and separates what you clearly demonstrated from what you claimed but couldn’t back up when asked to be specific. The resulting report states plainly what is already proven at the next level, what is not yet proven, and exactly what evidence would close the gap against the same competency framework every real assessment uses, including prioritization judgment, the dimension most of the signals above are actually testing.

Common questions

What is the difference between a PM and a senior PM?: The core difference is evidence of judgment at a broader scope. A PM demonstrates execution against a defined roadmap. A senior PM also demonstrates ownership of the roadmap itself: the decisions behind what was built, what was not built, and why. The level shift is from executing well to deciding well, and being able to articulate both.
How do I know if I am ready for a senior PM role?: Ask whether you can name a specific decision, not a process. Not "I improved prioritization" but a single call: the option you rejected, the tradeoff you made, what happened after. If every example you can think of ends cleanly with no tension or cost, that is a sign the examples are either not specific enough or not at senior-level scope yet.
Does confidence predict senior PM readiness?: Only weakly. Most people asking this question are either better at the job than they feel, or less prepared to prove it than they assume. Confidence reflects how you feel about your experience. Readiness reflects whether that experience, when described specifically and tested with a follow-up question, holds up as evidence of operating at the next level.