Manager Performance Plan Script -- How to Give Feedback That Actually Lands

Most managers avoid direct performance conversations. Instead they drop hints: "double check your work," "watch more closely," "can you redo this?" These indirect nudges feel safer, but they never fix the problem. The employee walks away without understanding the gap between what they are producing and what is expected.

@jobdoctortessa lays out a word-for-word script that replaces vague corrections with a structured conversation. The framework has four parts.

The Wrong Way

Passive, scattered comments that dance around the issue:

• "I need you to double check your work and make sure there are no errors."
• "Will you redo this document?"
• "Watch more closely in the future."

These tell the person something is off but give them nothing to act on. No specifics, no stakes, no path forward.

The Right Way -- The Script

The script follows a clear sequence: state the gap, show the evidence, explain the impact, then invite collaboration.

1. State What You Expected vs. What You Observed

"I've noticed that many of the finished work products you're turning in have more errors than I would expect to see. I would expect an error or two in formatting, for example, but in the past five assignments, I've noticed there are 20 or more errors."

Name the standard explicitly. Then name the shortfall with real numbers. No ambiguity.

2. Show Them What You Mean

"I want to review one of these with you to show you what I'm seeing."

Bring a concrete example. Walk through it together so the conversation stays grounded in facts, not feelings.

3. Identify the Consequences -- to Clients, Team, and Workload

"When you make these mistakes, it makes our department look unprofessional and leaves a bad impression for our clients. Also, because someone has to look over your work, it's creating a bigger workload for another team member. We're all prepared to help one another, but when it becomes a regular addition to somebody else's job, it doesn't create a positive work environment."

Connect the behavior to its downstream effects. This is not about making the person feel bad. It is about making the stakes visible so they understand why the change matters.

4. Ask, Don't Dictate

"Is there something going on I don't understand? What could prevent this from happening again? How can I help?"

End with three open questions. This shifts from correction to collaboration. It also surfaces context you might not have -- personal issues, unclear expectations, missing resources.

Key Takeaways

• Indirect hints about performance problems feel kind but are ineffective. They leave the employee guessing.
• Structure the conversation in four steps: state the gap with specifics, show a real example, explain the impact on clients and teammates, then ask how to solve it together.
• Use actual numbers ("20 or more errors in the past five assignments") instead of vague language ("your work needs improvement").
• Always close with open-ended questions. The goal is a two-way conversation, not a lecture.
• The framework works because it separates observation from judgment. You describe what you see, explain why it matters, and invite the person into the solution.