The Feedback Script That Prevents Surprise Performance Reviews

The Review That Broke the Relationship

Dana had managed Terrell for two years. He was reliable, collaborative, well-liked. So when she placed him at “meets expectations” with a note about inconsistent follow-through on cross-functional commitments, she expected a calm conversation.

Instead, Terrell went quiet. Then he said: “This is the first time anyone has told me this.”

Dana disagreed. She was sure she had mentioned it. Maybe in a team meeting. Maybe in a one-on-one. But when she reviewed her notes, she found nothing. No specific conversation, no documented observation, no agreed-upon next step.

Dana had been thinking the feedback. She had not been delivering it.

This is the most common failure in management, and it is not about courage. It is about systems. Most managers avoid performance conversations because they want to be fair and they fear being harsh. The irony is that avoiding clarity is rarely fair. Clarity, delivered early and often, is what gives someone a real chance to succeed.

The “I Thought They Knew” Gap

The gap between what a manager thinks they have communicated and what an employee has actually heard is where performance surprises live. Employee engagement research consistently shows that workers who receive frequent, specific feedback are more likely to feel their manager is invested in their success. The flipside: employees blindsided by negative reviews report sharp drops in trust, not just in the manager, but in the organization.

This gap has three common causes:

1. Hinting instead of stating. Saying “Let’s keep an eye on that” or “Something to think about” feels like feedback to the person saying it. To the recipient, it registers as a passing comment, if it registers at all.

2. Feedback without specifics. “You need to communicate better” gives someone nothing to act on. Compared to what standard? In which situations? Starting when?

3. No follow-up loop. Even clear feedback fades without a system to revisit it. If you name a gap once and never return to it, the message is that it was not important enough to track.

The Three-Level Feedback Script

Coaching research points to one principle above all: match your approach to the situation. Not every performance conversation requires the same tone. Here are scripts at three intensity levels. Use the one that fits the context, not the one that feels most comfortable.

Level 1: Soft (Early Signal)

Use this when you are noticing a pattern for the first time, or when the person is new and still calibrating to expectations.

“I want to flag something early because I’d rather we talk about it now than let it become a bigger issue. I’ve noticed [specific behavior] in [specific context]. The standard I’m looking for is [concrete description]. I’m not concerned yet. I just want to make sure we’re on the same page.”

When to use it: First occurrence. Early-career employees. Situations where the person may genuinely not know the expectation.

What good looks like: The person nods, asks a clarifying question, and you both agree on what “better” looks like. You write a two-line note and revisit it in two weeks.

Level 2: Standard (Clear Expectation)

Use this when a pattern has continued after an initial conversation, or when the gap is clear enough to name directly.

“I want to revisit something we talked about on [date]. I’ve continued to see [specific behavior], most recently in [specific instance]. The expectation is [standard], and right now there’s a gap between where you are and where I need you to be. Let’s talk about what’s getting in the way and agree on a plan to close that gap. I’d like to check back on this in [timeframe].”

When to use it: Second conversation about the same issue. Any situation where the expectation has been stated and the gap persists.

What good looks like: You and the employee co-create a short action plan. It has one or two specific changes, a timeline, and a follow-up date. You both leave knowing exactly what success looks like.

Level 3: Firm (Accountability Conversation)

Use this when previous conversations have not produced change, or when the performance gap is affecting the team.

“I want to be direct with you because I think it is the most respectful thing I can do. We’ve talked about [issue] on [date] and [date]. I have not seen the change we agreed on. Specifically, [concrete example from the past two weeks]. This is now affecting [team/project/outcome]. I need to see [specific change] by [date]. I want to support you in getting there, and I also need you to understand that this is not optional. What do you need from me to make this happen?”

When to use it: Third conversation. When previous agreements have not been honored. When the impact has expanded beyond the individual.

What good looks like: The conversation is uncomfortable but clear. The employee understands the stakes. You document the agreed-upon change and timeline, and you follow up exactly when you said you would.

Building the Continuous Feedback System

Scripts are useful, but they solve one conversation at a time. What prevents surprise reviews is a system that makes feedback continuous and trackable.

The Feedback Cadence

Weekly or biweekly one-on-ones: Every one-on-one should include at least one observation, positive or corrective. Not every session needs a hard conversation. But every session should include something specific: “I noticed you handled that client call well, particularly how you reframed the timeline question” is feedback, too.

Monthly development check-in: Once a month, dedicate 10 minutes of a one-on-one to the bigger picture. Where is this person relative to their growth goals? Is there a pattern forming, good or bad, that deserves a direct conversation?

Pre-review summary: Two weeks before any formal review, share a written summary of the themes you plan to discuss. This is not the review itself. It is a preview. If your employee reads it and is surprised by anything, your feedback system has a leak.

The Documentation Minimum

You do not need a complex tool. You need a running note for each direct report with three columns:

The pattern: observe, document, discuss, follow up. Four steps, repeated consistently, that eliminate the gap between “I thought they knew” and “nobody told me.”

Manager Mistakes to Watch For

These are not moral failures. They are patterns that form when nobody teaches you how to give feedback as a system, not just a skill.

Sandwiching. Wrapping critical feedback between two compliments teaches people to stop trusting your praise. Separate positive feedback from corrective feedback. Both deserve their own moment.

Waiting for certainty. If you wait until a pattern is undeniable, you have waited too long. Share the observation after two instances, not twelve. Early and provisional beats late and definitive.

Outsourcing to HR. Managers sometimes route feedback through HR because the conversation feels too hard. This almost always makes things worse. The employee hears it from someone they do not work with daily. Own the conversation. HR can coach you on how to have it, but you need to be the one in the room.

Confusing kindness with avoidance. Withholding feedback is not kind. It is comfortable for the manager and costly for the employee. Kindness is telling someone the truth early enough that they can do something about it.

Reflection Prompt

Before your next round of performance reviews, ask yourself:

If I handed my review to this person right now, with no conversation beforehand, would anything in it surprise them? If so, that is not a review problem. That is a feedback system problem, and it is mine to fix.

The No-Surprise Review Checklist

Use this before every formal performance review to confirm your feedback system has been working.

NO-SURPRISE REVIEW CHECKLIST

Employee: _______________
Review period: _______________
Manager: _______________

For each theme in the upcoming review, check all that apply:

[ ] I raised this topic in a one-on-one (date: ___)
[ ] I provided a specific example at the time
[ ] We agreed on a next step or expectation
[ ] I followed up on that agreement (date: ___)
[ ] The employee could articulate this feedback
    back to me in their own words

SCORING:
  5/5 checked = You are clear to include this in the review.
  3-4 checked = Include it, but acknowledge the gap in
                your own follow-through.
  0-2 checked = Do NOT put this in a formal review. Have
                the conversation first. The review can wait.

PRE-REVIEW PREVIEW:
[ ] I shared a written summary of review themes at
    least two weeks before the formal review
[ ] The employee confirmed no major surprises
[ ] Any new topics were discussed live before being
    documented

If any box above is unchecked, you have work to do
before the review meeting.

Run this checklist for every direct report, every review cycle. If you cannot check the boxes, the problem is not the review. The problem is the months that preceded it.

If you are building a feedback system for your management team (not just scripts, but the tracking, follow-through, and development rhythms that make reviews predictable), Kinetiq’s LEAD module was designed for exactly this. It is worth exploring if “no surprises” is the standard you want to set.