1

Requirements Quality

Clarity, completeness, and accuracy of requirements documentation.

Exceeds

Requirements are unambiguous and complete. Engineering rarely comes back with clarifying questions. Edge cases are pre-identified.

Meets

Requirements are clear for standard cases. Some follow-up questions from engineering.

Below

Requirements are ambiguous or incomplete. Engineering blocks are frequent.

Example review phrases

  • "Engineering lead said their requirements docs require the fewest clarifying questions of any BA they've worked with."
2

Stakeholder Management

Quality of relationships with and communication to business stakeholders.

Exceeds

Stakeholders trust their judgment on scope and priority. Disputes are resolved without escalation.

Meets

Stakeholder relationships are functional. Communication is timely.

Below

Stakeholder disputes escalate frequently. Communication is inconsistent.

Example review phrases

  • "Managed competing requirements from 4 business units on the ERP project—landed a scope decision everyone could execute behind."
3

Analytical Contribution

Quality of analysis supporting business decisions and project scoping.

Exceeds

Analysis shapes project scope and priorities. Business decisions are better because of their involvement.

Meets

Analysis supports decision-making adequately.

Below

Analysis is descriptive rather than decision-relevant.

Example review phrases

  • "The process mapping they did for the onboarding project identified 3 unnecessary steps that saved 2 weeks of engineering work."
🔮

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 →