360 Feedback Questions for Product Managers

17 ready-to-use questions, example comments and tips — plus a free tool that runs the survey and writes the report for you.

Product managers lead without authority. Their success depends on how engineers, designers, sales, support and leadership experience working with them, which makes a 360 one of the most useful reviews for the role. These questions look at how a PM decides what to build, explains why, and keeps a cross-functional team moving in the same direction.

Use these questions in a free 360 → Build your own questionnaire from these questions

Product thinking and prioritisation

  1. How clearly does this product manager explain the problem a feature is meant to solve?
  2. How well do they use customer evidence and data to decide what comes first?
  3. How clearly do they explain what is not being built, and why?
  4. How well do they balance short-term requests with longer-term product goals?

Working with engineering and design

  1. How well does this PM involve engineers and designers early, before the solution is decided?
  2. How clear and complete are the requirements, user stories or briefs they write?
  3. How well do they make trade-offs between scope, quality and deadlines with the team?
  4. How available are they to answer questions while work is in progress?

Stakeholder communication

  1. How clearly does this PM share the roadmap and changes to it with other teams?
  2. How well do they say no to requests from sales, leadership or customers while keeping the relationship?
  3. How well do they prepare support, sales and marketing for a launch?

Ownership and learning

  1. How consistently do they check whether a release achieved what it was meant to?
  2. How openly do they admit when a decision or feature did not work?
  3. How well do they keep the team focused when priorities shift?

Open-ended questions

  1. What does this product manager do that helps the team build the right things?
  2. What is one habit that would make them easier to work with?
  3. Describe a recent decision they made and how they handled it with the team.

Example feedback comments

Good comments are specific, describe behaviour rather than personality, and explain the impact. A few examples:

Not sure your feedback is fair and specific? Paste it into our free feedback bias checker.

Tips for a useful 360

  • Invite engineers, designers, a data or research partner, and people from sales or support who depend on the roadmap.
  • Ask reviewers for examples from a specific release or planning cycle to keep comments concrete.
  • Compare how the delivery team and outside stakeholders rate communication: the gap is often the most useful finding.

Frequently asked questions

Who should give 360 feedback to a product manager?

The engineers and designers on their team, their own manager, and stakeholders from sales, support, marketing or data who work with them on a regular basis. Six to ten reviewers usually gives a balanced picture.

What skills should a product manager 360 cover?

Prioritisation, customer understanding, clear requirements, collaboration with engineering and design, stakeholder communication and learning from results. Product sense is hard to rate directly, so ask about the behaviours that show it.

Run this 360 for free in 10 minutes

Answer your self-assessment and get an instant report. Then invite colleagues by link — no accounts, anonymous by default.

Start my free 360°

No credit card. No signup for reviewers.

More 360 feedback questions