The most useful thing review language can do is separate behaviour from character. "You missed three deadlines this quarter" is checkable and changeable. "You are disorganised" is neither, and it is what people hear for years afterwards. Almost every rewrite below is that same move applied to a different sentence.
Four rules before the wording
- Name the behaviour and its effect. What happened, and what it cost or caused.
- Use a specific instance. One real example beats a generalisation, and it is harder to argue with.
- Say what you want instead. The same sentence, ideally, rather than a separate lecture.
- State what happens next. Support, timeline, review point — or nothing changes.
Praise that lands
Vague praise is discounted instantly. These say why:
- "The [project] handover was the reason [downstream team] did not lose a day — the documented handover was complete enough to work from without asking you."
- "When [situation] came up, you chose [action] rather than escalating it, and that was the right call because [reason]."
- "Your review comments on [thing] caught [specific issue] before it reached a customer. That is the kind of thing that does not show up in any metric."
- "Three people raised [topic] with me unprompted as something you helped them with. Specific to you rather than to the team."
Direct feedback, stated once
- "The [deliverable] went out on [date] with [specific error]. It was [effect]. I would rather it went out a day later and was right — agree?"
- "In the last two reviews of [project] you were not ready with the numbers. When that happens the discussion moves to whoever did bring theirs. Can we agree you come with figures next time?"
- "You said in the meeting that [claim]. That was not accurate — [correction]. It matters because [reason]. Next time, check it or flag it as an estimate."
- "I have asked three times for [thing]. I would rather understand what is blocking it than ask a fourth time."
Naming underperformance without drama
- "This is below what is needed for [role] at this level. Here is specifically what is short: [list]. Here is what would meet it: [list]. We will look at this again on [date]."
- "I do not think this is an effort problem. I think it is [specific gap], which is addressable — if you agree, here is what I would suggest."
- "I want to be clear rather than kind: if [thing] does not change by [date], the next step is [stated process, not a threat]."
- "You are good at [strength] and I do not want that lost in this. The part that needs to change is [specific], and it is separable."
When you disagree with their self-assessment
- "I have a different read on [item]. You see it as [their framing]; I see [your framing]. The difference matters because [consequence]. Here is the evidence I am working from."
- "That rating is higher than the one I would give, and rather than negotiate the number let us go through what it is based on."
- "It is possible I am wrong. What would have to be true for your version to be right, and can we check it?"
Phrases that read as evasion
Each of these is recognisable as a way of not saying it, and the person usually hears the real message anyway — just without the detail they need:
- "Some areas for development." Which ones?
- "Could be more proactive." About what, specifically?
- "Not always meeting expectations." Expectations of what?
- Sandwiching. Praise–criticism–praise teaches people to discount both halves. Say the hard part plainly and praise separately.
- "Room for improvement." True of everyone, useful to nobody.
What to write yourself
Anything with consequences attached: formal warnings, anything referenced in a performance process, anything touching pay, and any document that could later be read by someone who was not in the room. Those get written in your own words, checked against your policy, and kept factual — the adjectives are what cause trouble later.
Editing time, from our 30-day benchmark
Our 30-day test measured roughly 8 minutes per review with a general assistant against about 22 minutes per 1,000 words on a low-cost writer. Reviews are short documents where the editing is mostly deleting hedges — the tools are useful at spotting softened language, less so at deciding what the honest version is.
Frequently Asked Questions
How do I give critical feedback without demoralising someone?
Describe the specific behaviour and its effect rather than the person, cite one real instance, and say what you want instead. The tone follows from specificity rather than from softening.
Should I use the praise-criticism-praise structure?
Generally not. It trains people to discount both halves. Give praise on its own when it is earned, and say the difficult part plainly when it is needed.
What phrasing makes reviews unclear?
Hedged generalities — "areas for development", "could be more proactive", "room for improvement". Each is true of everyone and actionable by nobody.
Can AI write performance reviews?
It can help spot hedged or vague language and suggest plainer constructions. The content has to be yours: real instances and real consequences.
What should I always write myself?
Anything with consequences attached — formal process documents, pay decisions, or anything someone outside the room may later read. Keep those factual and adjective-light.