Playbook

    How to Tell an Employee Their Work Isn't Good Enough: A 7-Step Structured Feedback Framework

    A four-sentence script, a reply for each of the eight things people most often say back, and the closing lines that make the change stick.

    The short version

    Say it in four sentences: what you saw, what it affected, what you need instead, and what's getting in the way.

    When they push back ("I had no idea", "that's not fair"), acknowledge it in a few words and come back to the one thing you need.

    End with an agreed change, a date to check in and a two-line written summary. Without those, nothing changes.

    The short answer: say it in four sentences

    You've noticed it for weeks. The work is late, or sloppy, or just not at the level the role needs, and you keep putting off the conversation because you don't want to crush them, sound harsh or hear "that's not fair." Here's how to say it, in four sentences:

    1. What you saw: "In the last three client reports, the ones due on the 3rd, 10th and 17th, each reached me one to two days late."

    2. What it affected: "Because of that, I had to push the client call twice and the design team couldn't start on time."

    3. What you need: "I need reports to reach me by noon the day before they're due."

    4. Their view, and the next step: "What's getting in the way, and what would help you hit that? Let's check in on Thursday after the next one."

    And when they say "I had no idea this was a problem"? "I hear that. I should have been clearer earlier. I'm being clear now: the reports need to be in by noon the day before."

    The rest of this page gives you a full example, a reply for each of the eight things people most often say back, and the closing lines that make the change stick.

    Check first: if the issue involves health, a disability, caring responsibilities or protected leave, talk to HR before the conversation.

    The structure above is a version of situation, behavior, impact, a long-established feedback model, with an ask added at the end. It works because each sentence does one job:

    What you saw is something a camera could have recorded. No labels like "careless" or "not committed."

    What it affected tells them why it matters, so it isn't just your preference.

    What you need is specific enough that you'll both know whether it happened.

    Asking their view turns a verdict into a conversation, and often tells you something you didn't know.

    Limitation: four sentences open the conversation; they don't finish it. The real work is in what they say next.

    A full example, line by line

    Here's how it sounds with someone who has missed client deadlines. You open: "I want to talk about the client reports. The last three reached me one to two days late. Because of that, I pushed the client call twice and design couldn't start on time. I need them by noon the day before. What's getting in the way?"

    They say: "Honestly, I didn't realize the day-before thing was a hard deadline."

    You say: "That's fair, and I should have been clearer. It is a hard deadline from now on. What would help you hit it?"

    They say: "The data from finance usually lands the morning of."

    You say: "Okay, that's useful. I'll ask finance to send it two days ahead. With that fixed, can you get me the report by noon the day before?"

    Notice what you didn't do: you didn't soften the message when they explained, and you didn't ignore a real obstacle either. You fixed the obstacle and restated the ask.

    What they'll say back, and what to say next

    Most advice stops at the opening line. Here are the eight replies you're most likely to hear, with wording for each.

    1. They say "I had no idea this was a problem" — You say "I hear that. I should have been clearer earlier. I'm being clear now: the reports need to be in by noon the day before." (Own your share without withdrawing the message. Avoid "well, it's not that bad.")

    2. They say "That's not fair, [teammate] is late too" — You say "I'm only talking about your work today. I'm looking at everyone's, and I'll speak to others if I need to." (Don't discuss anyone else.)

    3. They say "I'm overloaded. I've got twice the work" — You say "That could be part of it. Walk me through what's on your plate this week and let's work out what moves." (Treat it as information. If it's real, change the workload; if not, restate the standard.)

    4. They say "Nobody told me the deadline" — You say "Fair point. Let's look at how deadlines reach you. Going forward I'll put them in [place]. From now on it's noon the day before." (Fix the system if it's genuinely broken.)

    5. They say "I feel like I'm being singled out" — You say "I'm sorry it feels that way. This is about the three reports, and I'd be having the same conversation with anyone." (Don't over-apologize for the message.)

    6. Silence, looks down — You say "Take a moment. I'd like to hear what you're thinking." Then wait. (Don't fill the silence by softening.)

    7. Tears — You say "Let's pause for a couple of minutes." Then come back and restate the one thing you need. (Don't abandon the point.)

    8. They say "Are you going to fire me?" — You say "I'm not raising this to scare you. I'm raising it because I want it to improve. If it doesn't, we'll talk about what's next together, but I'm not there." (Say this only if it's true, and check with HR. No promises or threats you can't back.)

    If someone argues with every point, the move is the same each time: hear their view once, then return to the standard. "I've heard you. We see it differently, and I still need the reports by noon the day before."

    How to end the meeting so something changes

    Close with the agreement out loud: "So we're agreed: reports to me by noon the day before. We'll check in Thursday. I'll send you a two-line summary of what we said today so we both have the same version."

    Then send it the same day, by email or chat: "Thanks for talking today. As agreed: [what changes] by [when]. We'll check in on [day]. Shout if anything gets in the way before then."

    Why it works: a written summary removes any "I thought you meant…" later, and the check-in date makes it a plan rather than a lecture. You'll know it worked when they can repeat what changes and you have a date to look at it.

    Mistakes that make it worse

    Vague labels instead of what you saw:

    Instead of "You need to be more detail-oriented" say "The proposal went out with the wrong price on page 3 and the client caught it."

    Instead of "Your attitude in meetings is a problem" say "In Tuesday's meeting you interrupted Priya twice and she stopped contributing."

    Instead of "You always miss deadlines" say "The last three deadlines were missed by one to two days."

    The praise sandwich: Wrapping the problem between two compliments buries it. People remember the bread. If you want to recognize good work, do it separately and mean it.

    Saying it in a hallway, or three weeks late: Raise it privately and soon, ideally within days of the pattern becoming clear. The longer you wait, the more "why didn't you say something?" becomes a fair question.

    If you've been putting this off

    Say so. It takes the sting out of "nobody told me": "I should have raised this sooner, and that's on me. I'm raising it now because I want you to succeed here, and I can only help if I'm clear about it."

    If this isn't the first conversation about the issue, and you're moving toward a formal plan, see the PIP conversation playbook. To lay out the facts first, use the difficult conversation planner. New to managing? The 30-second feedback opener in leadership exercises for new managers is good warm-up practice.

    Practice it before the meeting

    On i-Grow.co you can rehearse exactly this meeting with an AI playing a team member who pushes back with "I had no idea", "that's not fair", or silence. You reply in your own words, then get a verdict on what you actually said: did you name the behavior, state the ask, and hold steady when they argued? Run it again until the first four sentences come out clean. For the broader method, see how to practice difficult conversations.

    Why trust this

    The proof is the product, not a logo wall

    This playbook draws on established feedback models and decades of management research.

    Who’s behind it

    iGrow is built by a sibling founding team: Pallavi, with over two decades of L&D and leadership development at Meta, Manulife, and EY, and Shantanu, a builder from Google, Salesforce, Walmart, and EY who shipped the product end to end.

    The framework isn’t ours to claim

    Every conversation is scored on the B.I.F.F. framework (Brief, Informative, Friendly, Firm), the response method developed by Bill Eddy of the High Conflict Institute — not a rubric we invented.

    See the actual output

    We don’t paste in testimonials we can’t verify. Instead, look at a real, scored report — no signup.

    See a sample report →

    Frequently asked questions

    How do I tell an employee their work isn't good enough without being harsh?

    Describe what you saw instead of labeling them, say what it affected, state exactly what you need, and ask what's getting in the way. Specific and calm reads as fair, not harsh.

    What should I say first?

    Start with the observable fact: "In the last three client reports, each reached me one to two days late." Skip the warm-up and the compliment sandwich.

    What if they get defensive or say it isn't fair?

    Hear their view once, then return to the standard: "I'm only talking about your work today." If they raise a real obstacle, fix it and restate the ask.

    How soon after the problem should I raise it?

    As soon as the pattern is clear, ideally within days. If you've waited, say so: "I should have raised this sooner, and that's on me."

    Do I need to document the conversation?

    Send a short written summary of what you agreed and when you'll check in. If it's becoming a formal process, see the PIP conversation playbook and involve HR.

    What if they cry?

    Offer a short pause, then come back and calmly restate the one thing you need. Don't drop the point.

    How do I know it worked?

    They can repeat what needs to change, and you have a date to check it. If neither is true, the conversation isn't finished.

    Can I rehearse this before I have it?

    Yes. On i-Grow.co an AI plays a team member who pushes back, you reply in your own words, and you get a verdict on what you actually said.