Measuring Product Management Performance: What Works and What Doesn't
Measuring product management performance is one of the most consistently mishandled aspects of product organization management. The challenge is structural: the outcomes that best reflect PM quality — product success, user value created, business results — are influenced by many factors beyond any individual PM’s control. And the outputs that are most directly attributable to PM work — documents produced, features shipped, ceremonies facilitated — often reflect activity more than value.
The result is that many product organizations either measure PMs on metrics that create perverse incentives, or avoid formal PM evaluation entirely. Neither approach serves the goals of developing PM capability or building high-performing product teams.
What Doesn’t Work
Feature velocity as PM performance: Measuring PMs by how many features their teams ship per sprint conflates activity with value and creates the incentive to ship small, easy features rather than investing in the hard work of discovering and delivering significant user value.
Business metrics in isolation: Holding PMs accountable for revenue, retention, or market share metrics that they significantly influence but don’t control creates both unfairness and learned helplessness. The PM who works in a shrinking market, with an under-resourced team, or with a flawed go-to-market strategy cannot drive business metrics regardless of product quality.
360-degree feedback as the primary evaluation: Peer and stakeholder ratings reflect relationship quality and communication effectiveness more than product judgment. A PM who builds excellent relationships while making poor product decisions will score well on 360-degree feedback; one who makes excellent product decisions while struggling with organizational politics will score poorly.
What Works Better
Outcome-oriented OKRs with honest attribution: Define specific product outcomes the PM is responsible for advancing, evaluate progress against those outcomes, and maintain honest attribution — acknowledging what contributed to outcomes beyond the PM’s control while holding the PM accountable for their specific contribution.
Process quality assessment: Evaluate the quality of PM practices that predict outcome quality: the rigor of user research conducted, the coherence of the product strategy, the clarity of requirements, the quality of stakeholder communication, the effectiveness of prioritization processes. These are more directly attributable to PM work and are leading indicators of outcome quality.
Strategic contribution evaluation: Assess the PM’s contribution to strategic clarity, organizational alignment, and team capability. Did the product direction become clearer? Did cross-functional collaboration improve? Did the PM develop the capabilities of product team members? These are genuine PM value contributions that deserve evaluation.
Building a Fair Evaluation System
The most effective PM evaluation systems combine multiple inputs: outcome metrics that the PM significantly influenced, process quality assessments conducted by their direct manager, and peer/stakeholder input that’s explicitly framed as one input among several rather than the primary evaluation mechanism.
They also acknowledge the significant role of context: a PM in a favorable market with strong team support and clear organizational alignment should be expected to produce better measured outcomes than one operating in unfavorable conditions, holding all else equal.
Key Takeaways
Measuring PM performance requires moving beyond feature velocity and business metrics in isolation to systems that assess outcome contribution, process quality, and strategic contribution simultaneously. The investment in building better evaluation systems produces better PM development, fairer accountability, and stronger product organizations — all of which produce better outcomes than the activity metrics that feel easier to track.
The Dual Accountability of Product Executives
Product executives who successfully navigate the PM-vs-executive tension develop a specific kind of dual identity: genuinely excellent product people who have developed genuine executive capabilities. This combination is rare but recognizable — the product leader who can engage deeply in user research on Tuesday and present to the board on Wednesday with equal credibility. Building this dual identity is the defining development challenge of product executive careers.