1

Outcome Ownership

Whether the PM is driving business outcomes, not just shipping features. Connection between roadmap decisions and product metrics.

Exceeds

Roadmap decisions are directly tied to business metrics with clear hypotheses and post-ship measurement. Owns outcomes, not just output.

Meets

Tracks product metrics for shipped features. Generally aware of business impact. Some measurement discipline.

Below

Roadmap is feature-focused. Little evidence of systematic measurement. Outcomes not clearly owned.

Example review phrases

  • "Every roadmap item comes with a hypothesis and a success metric—and they follow up 30 days post-launch with actual results."
  • "Drove the activation funnel redesign that improved 30-day activation by 22%—and measured it rigorously."
  • "Shipped 12 features this half. Unable to point to a single measurable outcome improvement connected to any of them."
2

Discovery Quality

Rigor of customer and market research that informs roadmap decisions. Evidence quality behind prioritization.

Exceeds

Discovery is systematic and evidence-based. Customer insights are specific and directly inform product decisions.

Meets

Conducts regular discovery. Customer feedback informs some roadmap decisions.

Below

Discovery is ad hoc. Roadmap decisions are more intuition-driven than evidence-based.

Example review phrases

  • "Interviewed 18 customers before proposing the integration feature—the scope was completely different from what the team assumed, and they were right."
  • "Changed the Q3 roadmap based on discovery data that showed the assumed pain point affected <10% of users."
3

Cross-Functional Alignment

Ability to build shared direction with Engineering, Design, Sales, and Customer Success.

Exceeds

Alignment is built before launches, not after. Engineering and Design describe the PM as the person who makes their work make sense.

Meets

Generally aligned with Engineering and Design. Escalates misalignment to leadership.

Below

Engineering and Design are often surprised by scope or priority changes. Alignment is reactive.

Example review phrases

  • "Engineering consistently says: 'They never surprise us with scope.' That's rare, and it compounds to faster delivery."
  • "CS team was looped in on the redesign before it shipped—they prepped support docs and had zero escalations at launch."
4

Roadmap Clarity

Quality of the roadmap as a communication tool. Whether stakeholders understand what's being built and why.

Exceeds

Roadmap is clear, prioritized, and understood by all stakeholders. Trade-offs are explained, not just communicated.

Meets

Roadmap is maintained and accessible. Most stakeholders understand current priorities.

Below

Roadmap is inconsistent or frequently revised without clear rationale. Stakeholders don't trust it.

Example review phrases

  • "The quarterly roadmap presentation was the clearest from any PM team—executives commented specifically on the trade-off framing."
🔮

Where do these examples come from in real reviews?

Most managers write performance reviews from memory—limited to what they personally observed. Confirm surfaces behavioral evidence from across the organization: who relied on this person, what they drove, how their impact extended beyond their direct manager's line of sight. Reviews written with Confirm's data are more accurate, more defensible, and faster to write.

See Confirm in action →