What This Template Is For
PM performance reviews are notoriously difficult because the PM role resists clean measurement. Engineers ship code. Designers deliver screens. PMs deliver outcomes through other people's work, which makes it hard to isolate their contribution. The result is that most PM reviews fall into one of two failure modes: pure vibes ("she's doing a great job") or over-indexing on a single metric ("the feature shipped on time").
This template provides a structured review framework that evaluates PMs across three dimensions: outcomes (what happened), competencies (how they operated), and development (where they are growing). It combines quantitative evidence with qualitative peer feedback and results in both a backward-looking assessment and a forward-looking development plan.
Use this template for quarterly or semi-annual performance reviews. For defining what the PM role looks like before evaluating performance against it, see the role expectations template. The Product Operations Handbook covers how performance reviews fit into the broader PM operating model. For ongoing feedback between reviews, the one-on-one template provides a structure for regular check-ins.
How to Use This Template
- The manager fills out Sections 1-3 (Outcomes, Competencies, Peer Feedback) before the review conversation. This takes 2-3 hours of preparation.
- The PM fills out their self-assessment using the same Outcomes and Competencies sections. Compare the two during the conversation.
- Schedule a 60-minute review conversation. Spend 40 minutes on the backward-looking assessment and 20 minutes on the forward-looking development plan.
- During the conversation, discuss areas of alignment and divergence between the manager assessment and self-assessment. Divergence is the most productive discussion topic.
- Co-create the Development Plan (Section 4) during the conversation. Goals should be mutually agreed, not assigned.
- Document the final review and share it with HR/People Ops per your company's process.
The Template
Section 1: Outcomes Assessment
Evaluate the PM's impact on product and business outcomes over the review period.
Review Period: [e.g., Q3-Q4 2025 / H2 2025]
PM Name: [Name]
Level: [e.g., PM / Senior PM / Staff PM / Group PM]
Manager: [Name]
Key Metrics Owned
| Metric | Target | Actual | Delta | Attribution Notes |
|---|---|---|---|---|
| [Primary metric, e.g., trial-to-paid conversion] | [Target] | [Actual] | [+/- %] | [PM's specific contribution vs. external factors] |
| [Secondary metric] | [Target] | [Actual] | [+/- %] | [Attribution notes] |
| [Secondary metric] | [Target] | [Actual] | [+/- %] | [Attribution notes] |
Key Deliverables
| Deliverable | Status | Quality | Impact | Notes |
|---|---|---|---|---|
| [Feature/initiative 1] | [Shipped on time / Late / In progress / Cut] | [Exceeded bar / Met bar / Below bar] | [Measurable impact if available] | [Context] |
| [Feature/initiative 2] | [Status] | [Quality] | [Impact] | [Context] |
| [Feature/initiative 3] | [Status] | [Quality] | [Impact] | [Context] |
Outcomes Rating
| Rating | Definition |
|---|---|
| Exceptional | Significantly exceeded targets. Delivered outsized business impact. Clear evidence of PM driving outcomes beyond expectations. |
| Strong | Met or slightly exceeded targets. Delivered meaningful business impact. Solid execution across all key deliverables. |
| Meeting Expectations | Met most targets. Delivered expected impact. Reliable execution with some areas for improvement. |
| Below Expectations | Missed key targets. Impact was below what the role and level require. Clear performance gaps to address. |
| Significantly Below | Missed most targets. Impact was materially below expectations. Requires immediate improvement plan. |
Outcomes Rating: [Select one]
Outcomes Summary: [2-3 sentences summarizing the PM's outcome impact this period. Be specific about what they delivered and what the business impact was.]
Section 2: Competency Assessment
Rate the PM on each competency dimension. Use the level-calibrated descriptors (what "meets expectations" looks like varies by PM level).
| Competency | Rating | Evidence |
|---|---|---|
| Product Sense | [Exceptional / Strong / Meeting / Below / Significantly Below] | [Specific example of how they identified user needs, defined solutions, and evaluated trade-offs] |
| Analytical Rigor | [Rating] | [Specific example of data-informed decisions, metric selection, experiment design] |
| Execution | [Rating] | [Specific example of shipping, scope management, cross-functional coordination] |
| Strategic Thinking | [Rating] | [Specific example of roadmap planning, market awareness, long-term vision] |
| Communication | [Rating] | [Specific example of stakeholder management, written docs, verbal clarity] |
| Technical Fluency | [Rating] | [Specific example of engineering partnership, technical trade-off understanding] |
| Leadership | [Rating] | [Specific example of team influence, mentoring, organizational impact] |
Level Calibration Guide
PM (IC, L3-L4):
- Meets expectations: Executes well within defined scope. Delivers assigned features with quality. Communicates proactively with their squad.
- Exceeds: Takes ownership beyond assigned scope. Identifies opportunities independently. Influences squad direction.
Senior PM (IC, L5):
- Meets expectations: Owns a product area end-to-end. Drives strategy for their domain. Influences cross-functional partners without authority. Mentors junior PMs.
- Exceeds: Shapes product direction beyond their domain. Recognized as a thought leader within the org. Drives org-wide process improvements.
Staff / Principal PM (IC, L6+):
- Meets expectations: Defines strategy across multiple product areas. Drives org-level priorities. Influences executive decisions. Sets standards for PM practice.
- Exceeds: Recognized as an industry-level practitioner. Drives company strategy. Creates frameworks and processes adopted across the organization.
Group PM / Director (Manager, L6+):
- Meets expectations: Manages 3-6 PMs. Develops and retains PM talent. Sets quarterly priorities for their area. Partners with engineering and design directors.
- Exceeds: Builds high-performing teams. Develops PMs who get promoted. Drives organizational strategy beyond their area.
Section 3: Peer Feedback Synthesis
Collect feedback from 3-5 peers (at least one engineer, one designer, and one cross-functional partner). Synthesize themes here.
Feedback collected from: [List names and roles]
Feedback Themes
| Theme | Sources | Summary |
|---|---|---|
| Strength 1 | [Who mentioned this] | [Specific example or quote] |
| Strength 2 | [Who mentioned this] | [Specific example or quote] |
| Growth area 1 | [Who mentioned this] | [Specific example or quote] |
| Growth area 2 | [Who mentioned this] | [Specific example or quote] |
Peer feedback questions (send these 2 weeks before the review):
- What is [PM Name]'s most impactful contribution this [quarter/half]?
- What is one thing [PM Name] could do differently to be more effective?
- How effective is [PM Name] at communicating priorities and decisions?
- How well does [PM Name] incorporate input from your function?
- Would you want to work with [PM Name] again on a future project? Why or why not?
Section 4: Development Plan
Co-create this section during the review conversation. The PM should drive their own development goals with the manager providing context on organizational needs and opportunities.
Strengths to Amplify
| Strength | How to Amplify | Timeline |
|---|---|---|
| [Strength 1, e.g., "Strong analytical skills"] | [e.g., "Lead the metrics review for the full product team, not just your squad"] | [e.g., "Next quarter"] |
| [Strength 2] | [Amplification plan] | [Timeline] |
Growth Areas
| Growth Area | Current State | Target State | Development Actions | Support Needed | Timeline |
|---|---|---|---|---|---|
| [e.g., "Strategic communication to executives"] | [e.g., "Writes detailed docs but struggles to distill into executive-level summaries"] | [e.g., "Can present a 5-minute strategic update to the C-suite with clear ask and supporting data"] | [e.g., "1. Shadow VP Product in 2 exec meetings. 2. Write 3 exec summaries with manager feedback. 3. Present at one product council meeting."] | [e.g., "Manager facilitates shadowing opportunities"] | [e.g., "6 months"] |
| [Growth area 2] | [Current] | [Target] | [Actions] | [Support] | [Timeline] |
Career Trajectory
| Dimension | Details |
|---|---|
| Current level | [e.g., Senior PM (L5)] |
| Next level | [e.g., Staff PM (L6)] |
| Gaps to next level | [1-3 specific gaps based on the level calibration guide] |
| Estimated timeline | [e.g., "12-18 months if growth areas are addressed"] |
| PM's stated career goal | [e.g., "Staff PM IC track" or "Move to Group PM management track"] |
The PM career path finder can help PMs explore different career trajectories and understand what skills to develop for each path. The PM salary guide provides compensation benchmarks by level for calibration conversations.
Section 5: Overall Assessment
| Dimension | Rating |
|---|---|
| Outcomes | [Rating from Section 1] |
| Competencies | [Overall competency rating: average or weighted] |
| Peer Feedback | [Positive / Mixed / Concerning] |
| Overall Rating | [Exceptional / Strong / Meeting / Below / Significantly Below] |
Manager Summary: [3-5 sentences capturing the overall assessment. What is the headline? What should the PM be most proud of? What is the single most important area for growth?]
PM Self-Assessment Summary: [PM writes 3-5 sentences on their own assessment of the period]
Areas of Alignment: [Where the manager and PM agree]
Areas of Divergence: [Where assessments differ, and how they were resolved in conversation]
Filled Example: Senior PM Quarterly Review
Section 1: Outcomes
Review Period: Q4 2025
PM: Alex Rivera, Senior PM (Growth Squad)
Manager: Lisa Park, VP Product
Key Metrics
| Metric | Target | Actual | Delta | Attribution |
|---|---|---|---|---|
| Trial-to-paid conversion | 10% | 11.3% | +13% | Alex designed the activation experiment that drove 2.1pp of the 3.3pp improvement. The remaining 1.2pp was from pricing page redesign (Marketing). |
| Time-to-first-value | < 3 min | 2.4 min | -20% (improved) | Alex scoped the guided setup wizard that reduced median time from 4.2 min to 2.4 min. |
| Onboarding completion | 75% | 72% | -4% | Missed target. New onboarding steps were too complex for SMB users. Alex identified the issue in week 3 and simplified in sprint 2, recovering from 68% to 72%. |
Outcomes Rating: Strong
Summary: Alex drove meaningful improvement on the Growth Squad's two primary metrics. The activation experiment was well-designed, properly instrumented, and delivered clear results. The onboarding completion miss was caught early and partially recovered, showing good metric vigilance. The miss itself was a scoping error (too many steps for SMB segment) that Alex could have caught with earlier user testing.
Section 2: Competencies
| Competency | Rating | Evidence |
|---|---|---|
| Product Sense | Strong | Identified the "setup wizard" opportunity from user session analysis. Scoped an MVP that addressed 80% of the drop-off with 30% of the engineering effort. |
| Analytical Rigor | Exceptional | Designed the activation experiment with proper holdout groups, pre-registered success criteria, and a 2-week analysis window. Caught the onboarding completion issue from daily metric monitoring. |
| Execution | Strong | Shipped 4 experiments in the quarter. Managed scope well on all but the onboarding redesign, where the initial scope was too ambitious. |
| Strategic Thinking | Meeting | Executed well within the defined growth strategy but did not contribute to strategy evolution. Did not surface competitive insights or propose strategic pivots. This is the primary growth area for L6 readiness. |
| Communication | Strong | Weekly updates were clear and data-rich. Stakeholder presentations were well-structured. Written PRDs were thorough. |
| Technical Fluency | Meeting | Partnered well with engineering on implementation details. Could go deeper on data pipeline architecture to unlock faster experiment iteration. |
| Leadership | Strong | Mentored the new APM (Chris) effectively. Chris shipped his first solo feature under Alex's guidance. |
Overall Assessment
Overall Rating: Strong
Manager Summary: Alex delivered a strong quarter that moved the Growth Squad's key metrics meaningfully. Analytical rigor is a standout strength. The primary growth area for reaching Staff PM level is strategic thinking: Alex excels at executing within a defined strategy but needs to develop the ability to shape strategy independently. Over the next 6 months, the focus should be on competitive analysis, market insights, and proposing strategic pivots to the Growth roadmap.
Common Mistakes to Avoid
- Reviewing recency, not the full period. The review should cover the entire quarter or half, not just the last 2-3 weeks. Review your 1:1 notes, sprint reviews, and metric dashboards from the full period before writing the assessment.
- Conflating PM contribution with team outcome. A team can ship a successful feature despite a weak PM (strong engineers can compensate) or miss targets despite a strong PM (external factors, bad luck). Isolate the PM's specific contribution through attribution notes.
- Generic feedback. "You need to improve communication" is useless. "Your sprint review presentations lack a clear narrative arc. You present data without connecting it to the strategic context. Try the situation-data-recommendation format for your next 3 reviews" is actionable.
- Skipping the self-assessment comparison. The most productive part of the review conversation is where the manager and PM assessments diverge. A PM who rates themselves "Strong" on execution while you rate them "Meeting" is a coaching opportunity.
- No development plan. A review without a forward-looking plan is a report card, not a development tool. The development plan is the most important section.
Key Takeaways
- Evaluate PMs across three dimensions: outcomes (what happened), competencies (how they operated), and development (where they are growing)
- Isolate PM contribution from team outcomes through specific attribution notes
- Collect peer feedback from at least one engineer, one designer, and one cross-functional partner
- The development plan is the most important section. Co-create it during the review conversation
- Review divergence between manager and self-assessment. Divergence is the most productive discussion topic
About This Template
Created by: Tim Adair
Last Updated: 3/5/2026
Version: 1.0.0
License: Free for personal and commercial use