Here's the short answer: constructive feedback in a performance review works when it names a specific behavior, explains the impact it had, and points toward what better looks like. That's it. Most feedback that lands wrong isn't harsh — it's vague. And vague feedback is unkind because it gives the employee nothing to act on.
The rest of this guide covers how to actually write that feedback in practice — with real before-and-after examples, a simple formula, and the mistakes that make review feedback feel useless even when you mean well.
Why Written Feedback Is Harder Than Saying It Out Loud
When you give feedback in a one-on-one, you get to read the room. You add tone, body language, and context in real time. Written review feedback has none of that. The words on the page are the entire message — and they'll be reread long after your conversation. An employee might revisit their review six months later when they're frustrated or doubtful about their standing. What you wrote becomes the record.
That's why written constructive feedback needs more precision than verbal feedback. A vague comment that felt clear in conversation looks damning or meaningless on a page. Precision is respect.
The Formula
Good written constructive feedback has four parts:
- Situation — When or where did this happen? Ground it in a real context.
- Behavior — What did they actually do (or not do)? Observable, specific, not inferred.
- Impact — What was the effect on the team, the work, or the outcome?
- Direction — What does improvement look like? Give them something to aim at.
You don't need to label each element explicitly. The goal is that all four are present in what you write. Missing even one usually makes the feedback fall apart.
Before & After: 5 Examples
These are the most common feedback situations managers face during reviews. For each one, here's what the vague version looks like and what the specific version says instead.
1. Communication
"Jordan needs to work on communicating more clearly with the team."
"During Q1 planning, Jordan's project updates were often sent after key decisions had already been made in Slack. The team ended up revising scope twice because they didn't have Jordan's input in time. A standing Friday update before EOD would give everyone the context they need going into the following week."
2. Meeting Preparation
"Sam sometimes comes to meetings unprepared."
"In three of the four client syncs this quarter, Sam arrived without reviewing the pre-read doc. This pushed 15–20 minutes of each call into recap territory, which visibly frustrated the client in February. Coming with the pre-read reviewed and one prepared question would meaningfully shift the dynamic."
3. Ownership and Follow-Through
"Morgan could show more ownership over their work."
"Three deliverables this quarter (the launch checklist, vendor summary, and onboarding doc) required follow-up nudges before they were completed. None were flagged proactively when they were at risk of slipping. Going forward, a quick note when a deadline is in jeopardy would let us adjust without scrambling at the last minute."
4. Technical Skill
"Alex needs to improve their technical skills."
"Alex's Q1 pull requests averaged two rounds of revision due to missed edge cases in error handling. This added about a day to the review cycle each time. Pairing with a senior engineer on one project next quarter and working through a structured code review checklist would address the pattern directly."
5. Interpersonal Dynamics
"Riley can be difficult to work with sometimes."
"In two sprint retros this quarter, when colleagues raised concerns about timelines, Riley dismissed them before hearing the full context — once with 'that's not how it works' before the person finished speaking. This has made some teammates hesitant to surface risks early. Pausing to ask a clarifying question before responding would go a long way in rebuilding that dynamic."
Common Mistakes
One More Thing Before You Write
Before you sit down to write, ask yourself: Could I give this feedback to the employee's face, in that exact wording? If the answer is no — because it's too harsh, too vague, or too abstract to say out loud — it's not ready for the page either. Written review feedback should meet the same standard as a clear direct conversation, just without the real-time give-and-take.
See a sample Kudo review to watch how AI-assisted feedback maintains that specificity even for managers who are doing reviews for the first time.
Q1 reviews are due soon for most teams. If you've got 8–10 reviews to write this month, the difference between vague and specific feedback isn't just quality — it's how long each review actually takes. Vague feedback is usually the result of not having the right examples in front of you. Specific feedback flows quickly when the material is there.
Write reviews that actually say something.
Kudo interviews each employee about their Q1 work, then drafts a full performance review with specific, cited feedback — ready to review and ship. Free tier: 2 reviews per cycle, forever.
Try Kudo Free →