Is 360 feedback useful at all for product managers?

Yes, for the right purpose. 360 feedback captures how a PM is perceived by the people around them, which is genuine useful information for coaching, team dynamics, and development conversations. The problem is using it to evaluate PM level or readiness for promotion, which requires evidence of decisions made, not ratings of behavior observed.

What should a 360 be used for instead?

As an input to a development conversation, not a level assessment. A 360 result that shows a PM is perceived as a weak communicator by peers is a starting point: it tells you where to look. An evidence-based assessment can then determine whether the underlying decisions and reasoning are sound but poorly presented, or whether the communication gap reflects something deeper about how they operate.

What does behavioral evidence assessment measure that 360 does not?

Behavioral evidence assessment measures specific decisions: what the PM decided, what they chose not to do, what tradeoff they made, and what happened after. It evaluates whether a PM can name a real prioritization call and defend the reasoning under follow-up questions. This is the same standard a rigorous PM interview applies, and it maps to a level-specific PM competency framework rather than generic leadership dimensions.

VS. ALTERNATIVE

360 feedback vs. behavioral evidence assessment for product managers

360 feedback is useful. It captures how a PM is perceived by their manager, peers, and direct reports, and perception is real information. The problem is treating perception as a proxy for decision quality or level readiness. A PM who presents well and has worked with the same team for three years can score identically to a PM whose last three prioritization calls were genuinely strong. The 360 cannot distinguish them.

Key takeaways

360 feedback measures how a PM is perceived. It does not measure whether their decisions were sound, what tradeoffs they made, or whether they are ready for the next level.
Rating inflation compresses the signal: when everyone scores 4 out of 5, the distribution no longer distinguishes anything.
Most 360 surveys use generic leadership dimensions, not PM-specific competency frameworks with level-specific evidence standards.
Raters evaluate what they observed. A peer who attended roadmap reviews may never have seen the decisions behind them.
360 is useful as a coaching input. It is not sufficient as a level or promotion assessment.

Five reasons 360 feedback falls short as a PM level assessment

It measures perception, not decisions

A 360 tells you how a PM is perceived by the people around them. It does not tell you whether their last prioritization call was sound, what tradeoff they made, or what the outcome was. Strong perception can reflect strong judgment. It can also reflect confidence, tenure, and presentation skill.

Rating inflation compresses the signal

Likert-scale 360s cluster toward the top of the scale. When everyone receives 4 out of 5 on strategic thinking, the rating no longer distinguishes anything. The signal you need (this PM demonstrates stronger product strategy than that one) is precisely what the compressed distribution destroys.

There is no consistent PM-specific framework

Most 360 surveys are built by each organization from scratch, or from a generic leadership competency library not specific to product management. "Communicates clearly" is not the same as a PM-specific communication standard that distinguishes what senior PM communication looks like from what director-level communication requires.

It does not distinguish levels

"Meets expectations" against what benchmark, at what level? A 360 that gives a PM 4.2 on stakeholder management says nothing about whether that score reflects senior PM expectations or director expectations. Without a level-specific rubric, the score has no reference point.

Raters evaluate exposure, not evidence

A peer who worked alongside a PM for a year may have seen dozens of roadmap reviews and none of the underlying decisions behind them. They rate the surface they observed. A manager who meets weekly may rate familiarity, not capability. Neither rater has the information needed to evaluate whether a specific decision held up under pressure.

What 360 feedback captures that behavioral evidence does not

Stakeholder perception is real. Whether a PM is seen as collaborative, reliable, and easy to work with matters for team function and organizational influence. A 360 can surface patterns a PM cannot see in their own behavior, things like how they come across in a room they do not control, or whether peers trust their judgment over time. These signals are worth having.

The distinction is between perception as context and perception as evidence. A 360 score on stakeholder management is useful context for a development conversation. It is not evidence that the PM can name a specific cross-functional disagreement they resolved, or explain what they gave up to get alignment. That distinction is what the stakeholder management and influence dimension in a behavioral assessment actually evaluates.

Common questions

Is 360 feedback useful at all for product managers?: Yes, for the right purpose. 360 feedback captures how a PM is perceived by the people around them, which is genuine useful information for coaching, team dynamics, and development conversations. The problem is using it to evaluate PM level or readiness for promotion, which requires evidence of decisions made, not ratings of behavior observed.
What should a 360 be used for instead?: As an input to a development conversation, not a level assessment. A 360 result that shows a PM is perceived as a weak communicator by peers is a starting point: it tells you where to look. An evidence-based assessment can then determine whether the underlying decisions and reasoning are sound but poorly presented, or whether the communication gap reflects something deeper about how they operate.
What does behavioral evidence assessment measure that 360 does not?: Behavioral evidence assessment measures specific decisions: what the PM decided, what they chose not to do, what tradeoff they made, and what happened after. It evaluates whether a PM can name a real prioritization call and defend the reasoning under follow-up questions. This is the same standard a rigorous PM interview applies, and it maps to a level-specific PM competency framework rather than generic leadership dimensions.