1

Multi-Team Delivery

Portfolio delivery across multiple engineering teams. Resource allocation, prioritization, and cross-team coordination.

Exceeds

Multiple teams operate with high autonomy and deliver consistently. Portfolio commitments are met despite changing priorities. Trade-offs are surfaced and resolved proactively.

Meets

Most teams deliver on commitments. Escalations are handled without significant delay. Portfolio priorities are managed reasonably.

Below

Teams frequently miss commitments. Resource conflicts go unresolved. Cross-team dependencies cause avoidable delays.

Example review phrases

  • "Coordinated delivery across 5 teams for the platform migration—zero missed dependencies despite 4 scope changes from Product."
  • "Has the trust of all 5 EMs who report in: they described the decision-making environment as clear, consistent, and fair."
2

Org Design & Structure

Quality of team structure, span of control decisions, and how well the org is set up to deliver.

Exceeds

Team structures are optimized for the current business stage. Span of control enables manager effectiveness. Org design decisions are anticipatory, not reactive.

Meets

Team structures broadly work. Span of control is reasonable. Org changes are responsive to business needs.

Below

Org structure creates friction rather than removing it. Team structures are inherited rather than actively designed.

Example review phrases

  • "Reorganized the platform team structure before it became a bottleneck—the result was faster execution and clearer ownership."
3

Executive Presence & Communication

Ability to communicate engineering context to the C-suite and translate business priorities back to engineering.

Exceeds

CEO and CPO trust their engineering assessments. Proactively escalates risks before they become surprises. Engineering perspective is consistently represented at the executive table.

Meets

Communicates engineering status clearly to leadership. Represents engineering tradeoffs in executive discussions.

Below

Engineering visibility at the executive level is limited. Risks surface through escalation rather than proactive communication.

Example review phrases

  • "The CEO described their Q2 roadmap communication as the clearest engineering briefing they'd received—concrete trade-offs, not jargon."
🔮

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 →