Performance Review Framing
Frame difficult feedback so it is honest, fair and actually heard.
A structured, fair review with feedback that lands and a path forward.
Difficult feedback fails at delivery: too soft and the message dissolves, too blunt and the listener spends the meeting defending instead of hearing. The Executive Coach structures the conversation so change is actually possible, the People Lead keeps it fair, evidence-based and procedurally sound, and the Brutally Honest Friend performs the essential service of stating the undiluted message first — so everyone can see what must survive the softening. The Negotiation Expert reads the other side of the table: how this specific person will hear it, and what response keeps the conversation alive.
Help me prepare a performance review or piece of difficult feedback so it is honest, fair, and actually heard. THE SITUATION: [the person, the role, and the gap between expectation and reality] THE FEEDBACK: [what I need to convey, including the hard parts] THE GOAL: [what I want to change, and the relationship I want to keep] THE RISK: [how it might be received badly] Debate: 1. Is the feedback fair and evidence-based, or coloured by one incident or bias. 2. How to be honest without being either brutal or so soft the message is lost. 3. The balance of recognition and challenge that keeps it credible. 4. How to make it about behaviour and impact, not personality. 5. The forward path — concrete, owned, and supported. 6. How the person is likely to hear it, and how to keep the relationship intact. FINAL SYNTHESIS: - A structured outline: what is working, the honest gap, the impact, the path forward. - The exact framing for the hardest message. - The one thing to avoid that would derail the conversation.
An illustrative excerpt for a hypothetical brief of this type: A team lead must tell a talented senior developer — the team’s strongest technical contributor — that his dismissiveness in code reviews is driving two colleagues toward resignation. Every real run is generated fresh from your specifics, debated across rounds, and audited before the verdict.
The undiluted version, so we know what we are protecting: “Your code reviews are making people want to quit. Two of them. You are the strongest engineer here and the biggest reason the team is fragile.” Every softening pass from here must preserve that content — the failure mode of this conversation is walking out having discussed “communication styles” in the abstract while he heard a compliment.
Fairness audit before delivery: is this pattern documented with examples, or is it two complaints and an impression? He will — reasonably — ask “when?”. The lead needs three specific review threads with the actual comments, and dates. Also check the system’s contribution: if he is the only senior reviewer for a large team, the volume pressure is real and shared responsibility, which does not excuse the tone but belongs in the room.
Model his likely first move: technical justification — “my comments were correct”. Do not contest it; concede it instantly, because it is true and it is not the point. “The comments were right. The delivery is costing us people.” Separating correctness from impact removes his best defensive position without humiliating him — and keeps the conversation on the only contested ground, which is behaviour.
Structure for the meeting itself: open with the stakes stated plainly and without menace — his work matters, this behaviour is undermining it, this is fixable. One behaviour, three examples, impact in concrete terms, then hand him agency: what would reviews look like if they built the team’s skill instead of testing it? The forward path must be his sentence, not the lead’s script — owned changes survive; imposed ones last a fortnight.
Prefer drop-and-go? Use the Performance Review Framing tool — team pre-seated, included with Plus.
What if the person cries, argues, or shuts down?
The plan includes the likely-reaction branches for your specific situation — the rehearsal covers the hard moment, not just the opening. The general principles: do not retract the message to end the discomfort, do allow silence, and separate the emotion (acknowledged) from the content (unchanged). The one thing to avoid is softening the message in real time to buy relief.
How do I give hard feedback to someone more senior or more skilled than me?
Anchor on impact, not hierarchy: you are not judging their craft — often you concede it explicitly — you are reporting consequences they cannot see from inside their own behaviour. That framing survives the skill gap. The council rehearses the exact concession-plus-redirect for your case, because it is the move that most people fumble live.
Is this for annual reviews or for one difficult conversation?
Both — the structure (evidence, one clear message, likely reactions, owned forward path) is the same whether it lands in a review cycle or a Tuesday. What changes is the paperwork: for formal reviews the People Lead seat adds the documentation and consistency checks that make the feedback fair and defensible.