360 Review Questions for Product Managers
12 targeted questions to gather meaningful peer feedback. Covers strategy, stakeholder management, prioritization, and cross-functional leadership.
Run Your 360 ReviewWhat you'll learn
- 12 copy-paste ready questions organized by PM competency
- Designed for associate PMs through senior/principal levels
- Focuses on behaviors that cross-functional partners can observe
- Works for self-review, peer review, or manager assessment
Why PM 360s Are Essential
Product managers operate at the intersection of engineering, design, and business. Their effectiveness depends heavily on influence, communication, and relationships—things peers can see clearly that metrics often miss.
A PM might hit their OKRs while leaving a wake of frustrated partners. Or they might miss short-term targets while building the trust and alignment that enables long-term success. 360 feedback surfaces these dynamics.
Strategic Thinking
"How effectively does this PM connect daily decisions to broader product and company strategy?"
"Does this PM demonstrate a clear, compelling vision for their product area?"
"How well does this PM anticipate market changes and competitive threats?"
Stakeholder Management
"How effectively does this PM communicate product decisions and rationale to leadership?"
"Does this PM actively seek input from diverse stakeholders before making major decisions?"
"How well does this PM manage expectations when timelines or scope changes?"
Prioritization & Execution
"How clearly does this PM articulate the "why" behind prioritization decisions?"
"Does this PM balance customer needs, business goals, and technical constraints effectively?"
"How well does this PM adapt plans when new information emerges?"
Cross-Functional Leadership
"How effectively does this PM partner with engineering to scope and deliver work?"
"Does this PM create an environment where team members feel ownership over outcomes?"
"How does this PM handle disagreements or conflicts within cross-functional teams?"
Frequently Asked Questions
What makes PM 360 reviews different from engineering reviews?
PM effectiveness is harder to measure objectively. While engineering output is somewhat quantifiable (code shipped, bugs fixed), PM impact is often indirect and long-term. 360 feedback is especially valuable for PMs because peer perception is a strong signal of actual influence and effectiveness.
Who should review a product manager?
Include the engineering team they work with, design partners, their manager, other PMs they collaborate with, and key stakeholders (sales, marketing, customer success) they interact with. Cross-functional feedback is essential for PMs.
Should I include customer outcome questions?
These questions focus on how the PM works with their team and stakeholders. Customer outcomes matter but are better assessed through metrics and business reviews. Peers can observe behaviors; outcomes require different data sources.
How often should PMs get 360 feedback?
Annually is standard, but bi-annual can be valuable for PMs in new roles or working on growth areas. More frequent feedback helps PMs adjust their approach faster, which matters since so much of PM work is relational.
What about technical PM skills?
Technical depth varies by PM role. For technical PMs, add questions about technical credibility and ability to engage in architecture discussions. For less technical roles, focus on the ability to translate between technical and business contexts.
Related Templates
Get Real Feedback on Your PM Skills
Our free tool makes it easy to gather anonymous feedback from your cross-functional partners.
Start Your Free 360