The Ambiguous Performance Review
You are editing a manager's written feedback before it goes to an employee. The draft reads:
"Overall your work has been fine, but there are concerns. You sometimes miss deadlines which is a problem and you need to improve your communication with the team because it's not always clear what you're doing. Also your reports could be better. I think you have potential but you need to step up. Let's discuss."
The employee has a documented right to receive specific, actionable feedback. The manager insists the message is clear enough.
1. Rewrite the feedback so it meets the specificity standard, and explain the three most serious defects in the original.
Read the worked answer
Three most serious defects:
- Unquantified vagueness. "Sometimes miss deadlines," "could be better," "step up" give no frequency, no example, no standard. The employee cannot tell what to change.
- Unattributed "communication" problem. "It's not always clear what you're doing" names a symptom but not the behaviour, audience, or occasion - is it status updates, written handoffs, meetings?
- Mixed and hedging register. "Fine," "I think you have potential," and "Let's discuss" dilute the message and bury the concerns; the sandwich structure makes the substantive issues easy to miss.
Rewrite (model):
"I want to recognise your strengths and be specific about two areas to improve. Deadlines: in the last quarter, two of your six project deliverables (the March data migration and the April client report) arrived after the agreed date - by 3 and 5 days. Communication: your weekly status updates have been sent on 3 of the last 8 weeks, which leaves the team unsure of your progress. Reports: the Q1 analysis lacked a summary section and cited no sources. For the next month, please send status updates every Friday by noon and include a summary and sources in reports. Let's meet Thursday to agree on support."
Why it works: each concern is anchored to a count, a date, or an artefact; each is paired with a concrete expectation; the tone is direct but respectful. A strong answer shows the transformation, not just a list of complaints about the original.
2. The manager objects: "Naming specific incidents will make the employee defensive." Construct the strongest response, acknowledging the manager's concern while defending specificity.
Read the worked answer
Acknowledge the concern: Specificity can feel like an attack if it arrives as a list of failures with no context - defensiveness is a real risk, and the manager is right to care about the relationship.
Defend specificity anyway:
- Vagueness is also threatening. "You need to step up" gives the employee no way to succeed and no way to contest a claim. That breeds anxiety and grievance, not safety.
- Specificity is falsifiable and therefore fair. "Two of six deliverables late" can be checked; if the manager is wrong, the employee can say so. "Sometimes late" cannot be rebutted or corrected.
- Specificity protects the manager. Documented, dated feedback is defensible in a formal review; impressions are not. If the issue escalates, the specific record is the manager's ally.
Reconcile the two: the content should be specific; the delivery should be collaborative. Pair each specific observation with an invitation ("tell me what got in the way") and a forward-looking expectation. Specificity about behaviour, warmth about the person.
Model insight: The false choice is "specific OR supportive." The exam rewards recognising that specificity and psychological safety are complements, not substitutes - and that the manager's real fear is about tone, which can be fixed without sacrificing precision.