New Manager Feedback Script Template for Underperformers: Amazon-Style

New Manager Feedback Script Template for Underperformers: Amazon-Style

TL;DR

The right script is not a morale speech; it is a clean record of the bar, the miss, the consequence, and the next checkpoint. In a Q3 debrief, the hiring manager did not want a softer tone; he wanted a dated correction tied to observable output, because intent never closed the gap. The problem is not candor, but vagueness: underperformers survive ambiguity, not a written standard with a deadline.

Who This Is For

This is for the new manager who inherited a weak performer, still has to ship with them, and cannot afford to turn every 1:1 into a vague coaching session. It fits the PM, tech lead, or functional manager who has feedback anxiety, a half-built paper trail, and a director asking whether the issue is skill, will, or fit. Not every low performer is a bad hire, but every low performer is a risk until you can show the bar, the miss, and the reset.

Why does an Amazon-style feedback script work on underperformers?

It works because it removes the manager’s mood from the conversation. In one calibration meeting, a manager tried to soften a miss by saying the employee “had a lot on their plate”; the room ignored it because the launch review showed the same error twice, both times after the expectation had already been clarified. The first counter-intuitive truth is that direct feedback is often kinder than delayed softness, because delay lets the person keep investing in a story the team has already stopped believing. Not a pep talk, but a standard. Not a personality diagnosis, but an observable gap. Once the conversation is written around facts, the underperformer cannot hide behind ambiguity, and the rest of the team stops guessing what the bar actually is.

The deeper psychology is simple: people adapt to the tolerance level they are shown. If a manager keeps talking in circles, the team learns that the real standard is negotiable. In Amazon-style rooms, the debate is rarely about whether the miss happened; it is about whether the manager had the nerve to name it early enough. That is why the script matters. It converts private frustration into public clarity, and public clarity is what keeps underperformance from becoming the new normal.

What should the first feedback conversation sound like?

It should sound like a reset, not a rescue. The opening needs to be direct enough that the employee cannot mistake it for casual coaching, but controlled enough that you do not turn it into a personal indictment. A useful opening line is: “I want to be direct. On the last two deliverables, the work missed the bar on quality and timing. The expectation is X, and the gap matters because it affects Y. I need a corrected version by next Wednesday.” That is not abrasive. It is specific. The problem is not tone, but sequence: standard first, evidence second, consequence third, support last.

If the employee pushes back, do not debate history. Use this line instead: “I am not arguing about your intent. I am describing the output against the bar.” That sentence changes the room immediately because it refuses the usual detour into feelings, effort, or busyness. In a debrief, I watched a manager lose 20 minutes explaining why the employee was “good in principle” before the room cut him off and asked whether the actual work met the standard. It did not. The first conversation is not where you prove you are a nice manager. It is where you prove you can hold a line without drifting into either cruelty or confusion.

A second script helps when you need to leave no ambiguity about next steps: “If you believe I am missing context, tell me now. If you agree the gap is real, I want your plan for fixing it in writing by 5 p.m. today.” That is the right pressure. Not more reassurance, but clearer ownership. Not a rescue, but a reset.

How do you separate a context gap from a real performance gap?

You separate them by whether the miss survives one explicit correction. The second counter-intuitive truth is that many “underperformers” are actually operating under missing context, but you do not diagnose that by sympathy; you diagnose it by the artifact. If the employee can restate the bar in plain language and still misses the next checkpoint, you are no longer dealing with context. If they cannot restate the bar after you have explained it twice, you were never managing performance alone; you were managing misunderstanding.

In one QBR prep, a manager called the issue “ownership” for six weeks. That was wrong. The real problem was that the employee had never been told what a good draft looked like, what tradeoffs were unacceptable, or what had to be true before sign-off. Once those three points were written down, the next draft changed. That is the distinction leaders miss: low context produces inconsistent output; low performance produces repeated misses after the context has been made explicit. Not more meetings, but a sharper definition of done. Not more encouragement, but a cleaner standard.

The useful test is brutally simple. Ask the employee to explain the bar back to you, then ask what they will do differently by Friday. If the answer is concrete, you may still have a coachable gap. If the answer is broad, vague, or aspirational, you are not looking at a temporary misunderstanding. You are looking at a manager who has allowed ambiguity to survive too long.

What do you say after the first warning?

You say less than you think, and you write more than you speak. The follow-up conversation is not a second chance to persuade anyone; it is a checkpoint that records whether the person can convert the reset into behavior. A clean script is: “Last week we agreed on X. Since then, I saw the same miss on Monday and again on Thursday. That means the gap is still open. Starting now, I need A, B, and C by Friday at 3 p.m. If that does not happen, I will escalate this to a formal performance conversation.” That is the correct shape. Clear, dated, and unsentimental.

The third counter-intuitive truth is that the follow-up is not about being harsher; it is about being more exact. Managers often think the second conversation needs more emotion to signal seriousness. It does not. It needs a tighter record because the real audience is not only the employee. It is the director, the HR partner, and eventually the room that has to decide whether the manager handled the gap with discipline. In a promo committee prep, the most dangerous phrase was “we’re still working on it.” Everyone translated that as “there is no actual decision.” The same logic applies here. If the next date passes and the standard is still missed, the organization reads that as the real bar.

If the employee gets defensive, keep the line short: “I am not debating the past. I am tracking the next observable output.” If they ask whether they are in trouble, answer plainly: “You are in a performance conversation, and the outcome depends on what happens next.” That is not cruel. It is honest enough to be useful.

When do you stop coaching and start documenting?

You start documenting the moment the same miss survives a reset and a deadline. That is the line. Before that, you are coaching. After that, you are creating a record that can survive memory, politics, and future disagreement. The fourth counter-intuitive truth is that documentation is not bureaucracy; it is how you prevent the story from being rewritten later. In Amazon-style rooms, soft recollection is not evidence. A dated note with the bar, the gap, and the next expectation is evidence.

This is also where new managers make the worst mistake. They keep calling a documented pattern “development” because they want to preserve the relationship. That is the wrong trade. Not empathy, but enforcement. Not saving face, but preserving truth. If the employee improves in one dimension but keeps missing the core standard, do not call it progress; call it mixed. If the same defect reappears after a dated reset, stop narrating it as potential. Potential is not a substitute for output.

The manager’s job at this stage is to make the record boring and undeniable. Write what happened, when it happened, what the standard was, and what will happen if the gap remains open. That discipline matters because when the debrief comes, nobody cares how thoughtful the conversation felt. They care whether the facts were clean enough that the decision could be defended.

Preparation Checklist

• Write the bar in one sentence before the meeting. If you cannot say what “good” looks like without qualifiers, you are not ready to give feedback.
• Pull three concrete examples of the miss. One vague complaint turns into a debate; three dated examples turn into a pattern.
• Draft the opening line and rehearse it out loud. The script should name the gap, the impact, and the next checkpoint without drifting into apology.
• Decide the consequence before you speak. If the deadline passes, know whether the next step is another reset, a formal plan, or escalation.
• Work through a structured preparation system (the PM Interview Playbook covers performance calibration, feedback docs, and debrief examples that map cleanly to this kind of conversation).
• Write the follow-up note immediately after the conversation. If you wait a day, the story gets softer than the facts.
• Prepare one sentence for pushback: “I am not debating your intent; I am tracking the output against the bar.”

Mistakes to Avoid

• Leading with sympathy instead of the bar. BAD: “I know you’ve had a rough stretch, so let’s just see how the next few weeks go.” GOOD: “The bar on quality is X, your last two deliverables missed it in the same way, and I need a corrected version by Thursday.”
• Making the conversation vague and time-free. BAD: “Let’s stay in touch and see how things develop.” GOOD: “We will meet every Tuesday for two weeks, and on the second Friday I will decide whether the gap is closed.”
• Turning feedback into a personality verdict. BAD: “You’re not senior enough for this role.” GOOD: “This quarter, your output did not show the judgment the role requires; here are the three observable misses.”

FAQ

1. Should I say “underperforming” directly? Yes, if the miss is obvious and documented. Euphemisms usually protect the manager’s discomfort, not the employee’s future. If the bar is real, name the bar.

1. What if the person is new and still missing context? Then say that explicitly and give one clean reset. If the same miss repeats after the bar is explained in plain language, stop calling it onboarding.

1. Do I need HR before the first conversation? No, not for the first direct reset. Bring HR in when the issue becomes formal, repeated, policy-sensitive, or linked to any risk that needs process discipline.