"X contributed meaningfully this half. Shipped the payments refactor, contributed to onboarding, ran 3 tech talks. A core senior on the team. Continues to meet expectations of their level."
"X performed above the Senior bar this half, but not yet stably enough for Staff. They independently delivered the payments refactor — a project originally scoped at Staff — and Z (a calibrated Staff) reviewed the delivery and called it promo-ready. However, on the Staff dimensions of cross-team alignment and unblocking peers, the evidence is still thin. If next half they can act as technical lead on 1–2 cross-team projects, the promo case is made."
• "X consistently operates above the Senior bar in Y, and is approaching the Staff bar in Z." — Anchor the rating to the level rubric, not to "how much they did."
• "The pattern I'd like to see shift next half is…" — More precise and behavior-pointed than "they need to improve."
• "This is a strong half, but not yet a promotion case, because…" — Say it plainly. No hedging.
"X has been really solid this half. Hit all her OKRs, the team loves her. She's the most reliable senior on my team, I think she's clearly at Exceeds."
→ No anchor to the level rubric, no concrete cross-team evidence, "the team loves her" is unverifiable in this room. The next manager to speak will dismantle this in one sentence.
"X for Exceeds, anchored on three Senior rubric criteria. (1) Scope — she independently owned the payments refactor, which was scoped at Staff; I had Z (a calibrated Staff) review the delivery and they called it promo-ready. (2) Multiplier — both mids she mentored were promoted to Senior this half, and her onboarding doc is now being used by two other teams. (3) Cross-team — she has substantive comments adopted in RFCs from infra, billing, and growth. Anchoring her against the other three Exceeds proposals in this room, she's at least stronger on Multiplier."
• "I'd like to anchor her against Y, who's a calibrated Exceeds — on multiplier she's stronger; on scope they're equivalent."
• "I hear the concern. Let me concede X, but the case still holds on Y and Z." — Give ground on the small point, hold the core.
• "This is a Meets, not a Below — and here's why the room shouldn't push it down." — Proactive defense.
"X is sometimes too assertive in design discussions, which can make junior engineers hesitant to push back."
"In 3 design reviews this half (Q1 payments, Q2 onboarding redesign, Q2 search migration), X arrived with a strong proposed solution. In 2 of those, junior engineers told me afterward they had alternative ideas they didn't raise. Next half, I'd like to see X open these reviews with the problem framing only, and invite proposals before sharing her own."
→ Same behavioral observation, but (1) specific count and scenes, (2) feedback aimed at behavior, not "character," (3) a concrete actionable direction. The original "too assertive" is precisely the gendered language Snyder's research identifies.
As a woman leader, you have to watch perf review from two sides:
(1) The reviews you write: Research shows female managers sometimes rate female reports more harshly — sometimes called "Queen Bee," but more accurately: you unconsciously hold "people like you" to a higher bar. After writing any review of a female report, ask yourself: "If they were male, would I have used the same words?"
(2) The reviews you receive: If you see "abrasive / too direct / intimidating / needs to be more collaborative" in your own review, ask your manager for the specific business impact. Sheryl Sandberg in Lean In describes the first time she got this kind of feedback at Google: instead of accepting it as "well-meaning advice," she asked, "Can you tell me which decisions would have been better if I'd been less direct?" That single question changed how she received feedback afterward — and changed the quality of the feedback she got.
• Don't write "abrasive" → write "In meeting X, she interrupted Y twice; this is the pattern I'd like to shift."
• Don't write "not a team player" → write "declined to take on 2 cross-team requests that the team needed."
• Don't write "too quiet" → write "in our design reviews, his strongest ideas surface in 1:1s afterward rather than in the room — I'd like to help him bring them into the room."
"Honestly, you did great — the company caps Exceeds at 15% this year, and calibration was brutal. You were close, you'll get it next time."
→ Shifts responsibility to "the system." They conclude "it's not me, it's luck." They change nothing next half.
"You're solid at Senior. A little more visibility, a little more ownership, and you're there. Keep it up!"
→ "Visibility / ownership" is empty. They walk out with no idea what to actually do — but with a warm fuzzy feeling. The textbook version of Ruinous Empathy.
"Good question. First — Meets is not me being unhappy with the half. You delivered payments refactor and two core onboarding modules; the quality was solid.
Exceeds at this level has two specific bars: (1) Scope expansion — independently owning an ambiguous problem originally scoped at Staff; (2) Multiplier — measurably raising the output of others on the team. On the first one, you got halfway: the payments refactor was Staff-sized, but the scoping was done by Y; you took over execution. On the second, I saw signals but not yet a stable pattern — you mentored Z, but your design doc didn't get adopted outside our team, so it didn't produce leverage.
So this isn't 'a hair short' — there are two concrete things that didn't fully happen. Next half, if you can own the search project end to end, starting from the problem framing, and write up your caching pattern so the platform team adopts it, the Exceeds case is made. I'll put both of those in your next-half focus."
As a woman leader, when you get a Meets and expected an Exceeds, research suggests you're more likely than male peers to: (a) accept it immediately, blame yourself, "I should have worked harder"; (b) swallow the "why not Exceeds" question because asking feels "ungrateful"; (c) quietly burn out instead of asking for more scope or resources.
The right move is Sandberg's: "Can you walk me through what would have made this an Exceeds — specifically, which scope or which artifact?" That isn't ungrateful, it's professional. If you don't ask, next half you'll get the same fuzzy feedback and the same Meets — and by year three you'll think you've hit your ceiling.
Conversely, when you're the manager giving a female report Meets: proactively open the "why not Exceeds" door. Don't wait for them to ask — many of them won't.
• "Meets is not a consolation prize — let me first say what made this a strong half." — Open. Set the tone.
• "The two specific things that would have made this Exceeds are…" — Cut to the core. No hedging.
• "This is concretely actionable. Let's put it in your next-half focus." — Close. Pivot to the future.
• Avoid "You were close" / "Next time" / "It was competitive" — these three are the throwaway phrases of perf review.
If you're writing or just finished perf reviews this week — do this before you submit: