A manager sits down to write performance reviews for her team of six. She uses AI to help structure each one, typing the employee’s name, their role, and a few adjectives about how the review period went. What comes back for each person is well-written, professionally worded — and interchangeable. The same observations about “strong collaboration” and “continued development in communication” could appear in any of the six reviews with minor substitutions. She edits each one, trying to inject specificity. By the time she’s done, she has spent more time editing than she would have spent writing from scratch — and the reviews are only marginally more useful. The problem is not the AI. The problem is that she gave it almost nothing to work with, because she had not yet done the thinking that makes a review useful.
Why Generic Reviews Fail the People They Are About
A performance review that could describe anyone describes no one. It tells the employee nothing about what their specific contributions were, what specific behaviors drove good or bad outcomes, or what specific changes would make a meaningful difference in the next period. It is a compliance document masquerading as a development tool. The damage is not just motivational. Generic reviews fail at the practical function of a review: creating a shared, specific record of what happened, what worked, and what needs to change. When a review says “has shown growth in stakeholder management,” the employee and the manager will have different memories of what that means in twelve months. When it says “Q3 product launch delivered two weeks early despite scope increase in week six due to a rapid pivot in stakeholder requirements,” there is no ambiguity. AI produces the first version when given nothing. It can produce the second — but only when given something to work with.
The Brief That Makes a Review Useful
A useful performance review brief is essentially a structured collection of what the manager actually observed during the period. It does not need to be exhaustive — it needs to be specific. Two or three concrete examples of strong performance, with enough context to make them legible. One or two specific areas where development is needed, described in terms of observed behavior rather than trait labels. The goal the employee was working toward and how the period went relative to it. Any significant context — a difficult period, a major project, a change in team structure — that should inform how the performance is evaluated. This information exists. It is in the manager’s memory, in meeting notes, in project retrospectives. The brief is what gets it out of those places and into the review.
What a Properly Briefed Performance Review Request Looks Like
Role: You are an experienced HR professional helping a manager write a
fair, specific, and useful performance review.
Context: Employee: [Role]. Review period: [timeframe].
Strong contributions this period:
- [Specific example 1 — what they did, what the outcome was]
- [Specific example 2]
Development areas:
- [Observed behavior that needs to change, described specifically — not a trait label but what you actually saw]
Context that should inform the evaluation:
- [Any significant external factors — team changes, unusual projects, personal challenges that were disclosed]
Goal set at start of period: [What was agreed]. Outcome: [How it went].
Tone: This is a mid-senior employee who takes feedback seriously and responds
well to directness. The review should be honest about the development area without
minimizing the genuine strengths.
Output: A complete review that names specific contributions, frames the development
area constructively with a concrete suggestion for improvement, and reflects the
manager's genuine assessment rather than generic performance language.The review produced from this brief is about this person. It can be read back in twelve months and both parties will know what it referred to. It does the job a review is supposed to do.
The Thinking That Has to Happen Before the Writing
The reason performance reviews are routinely generic is not that managers don’t know their team members. It is that the thinking required to write a specific review — calling up the specific examples, naming the specific behaviors, connecting outcomes to individuals — happens in the writing process, not before it. Asking AI to do the writing before that thinking is complete produces the generic output. The brief forces the thinking first. The manager who has assembled two specific examples of strong performance, one specific development observation, and the relevant context has already done most of the work. AI completes the document. The result is a review worth having. For managers conducting reviews across a large team, Briefing Fox can structure the brief-building process — ensuring the specific observations get captured for each person before any writing begins.
Before Your Next Review Cycle
For each person you are reviewing, write down two things they did specifically well this period and one specific behavior you want them to change. Not trait labels — specific observations. Give those to AI as the brief, and add the context of the period and the tone that fits the individual. That is all it needs to produce a review worth giving. The review that actually develops someone is built on what you actually saw. The brief is where that goes. Try Briefing Fox free at www.briefingfox.com.