Skip to main content
Product Assessment

FOR MANAGERS

How to assess product manager performance

The short answer: rate the decision, not the delivery. Most performance conversations drift toward what shipped, how confidently someone presents, or how long you’ve worked with them. None of those are reliable signals of product judgment on their own. The more useful question is whether a specific decision, examined closely, holds up.

Key takeaways

  • Rate the decision, not the delivery. Most performance conversations drift toward what shipped, not whether the judgment behind it holds up.
  • Easy to overweight: confidence and polish, self-reported impact ("I drove alignment on X"), and tenure or familiarity.
  • What to ask for instead: a specific decision with the alternative rejected and why; a tradeoff someone pushed back on; a moment they changed their own mind.
  • Tie one decision to a specific result. Not just a feature that shipped, but an outcome connected to the choice.
  • An evidence-based report informs development conversations. It is not intended as the sole basis for hiring, promotion, or termination decisions.

Next action

Assess your product team on one standard

See demonstrated strengths, readiness, coaching priorities, and team gaps without relying on self-ratings.

Assess my product teamExplore a sample team

Sample team view

Email me the sample team assessment view

You will receive a link to the sample team report: team profile, strengths and gaps, every-member heatmap, roster, and a sample 1-on-1 agenda.

Signals that are easy to overweight

Confidence and polish

A PM who presents well in a 1-on-1 or a roadmap review is not necessarily demonstrating stronger judgment than a quieter one. Polish is easy to overweight and hard to unlearn overweighting.

Self-reported impact

"I drove alignment on X" is a claim, not evidence. Without a specific example of the disagreement and how it was actually resolved, there is nothing to evaluate.

Tenure and familiarity

How long you have worked with someone, and how comfortable that makes a rating feel, is not the same as evidence of what they have actually demonstrated recently.

What to ask for instead

In a 1-on-1 or a calibration conversation, push for:

  • A specific decision, with the alternative they rejected and why
  • A tradeoff someone pushed back on, and how they actually resolved it
  • A moment they changed their own mind because of new evidence, not because they were told to
  • A result they can tie to the decision, not just a feature that shipped

This is the same standard Product Assessment’s adaptive interview applies, scored against the same 16 dimensions for every person on your team, so a development conversation starts from consistent evidence rather than whoever presents most confidently in the room.

What this does not replace

An evidence-based report informs a development or promotion conversation. It does not make the decision for you, and it is not intended to be the sole or primary basis for a hiring, promotion, compensation, or termination decision. See /trust for exactly where things stand on validation.

Related reading