The work comes back late, or wrong, or both. You've fixed it yourself more than once. You've mentioned it in a 1-1, gently, and nothing changed. Now you're carrying their gaps, the team has noticed, and you're starting to dread the conversation you know you have to have.
Most managers wait too long with underperformance, and usually for decent reasons. They don't want to be harsh, they're not sure the person really knows, or they hope it will sort itself out. It rarely does. This guide covers how to work out what's actually wrong, how to prepare for the conversation and run it, how to set a plan that's fair to both of you, and how to decide when you've done enough.
First, name it to yourself
Underperformance is easier to live with than to name. The first step is to write down, for yourself only, exactly what's falling short. Stick to facts:
- The work: which deliverables, what was wrong with them, and how often.
- The behaviour: missed deadlines, slow replies, errors that keep coming back.
- The dates: when it started, and the last three or four examples.
Don't write "lazy", "not committed" or "bad attitude". Those are labels, and the person will argue with a label. They can't argue with "the client report was due on the 3rd and arrived on the 9th, with the totals wrong".
If you struggle to list specific examples, you may not have a performance problem yet. You may have a feeling. Watch closely for two weeks, and keep notes as you go.
Is it ability, will, or something else?
Before you decide what to do, decide what kind of problem you're looking at. The Ability vs. Will card in The Leader's Toolkit asks one question: is this person struggling because they can't do it, or because they won't? Coaching a skill problem and coaching a will problem aren't the same job. (We go deeper on this in our performance management framework.)
| If it looks like... | It's probably... | What usually helps |
|---|---|---|
| Effort is there, results aren't. Asks for help, still gets it wrong | Ability: missing skill, knowledge or practice | Training, pairing, smaller steps, clearer examples |
| Knows how, does it when watched, slips when not | Will: motivation, engagement, or a choice | A direct conversation about the standard and the consequences |
| Was fine six months ago, then dropped | Something changed: workload, role, health, life outside work | Ask first. Then adjust what you can |
| Thinks they're doing great | Unclear expectations, or feedback that never landed | Spell out what good looks like, with examples |
Be honest about the last two rows, because they're often about you as much as them. If you've never written down what "good" looks like for this role, start with the Setting Expectations card. People can't hit a target they can't see.
Before the conversation: prepare on paper
The most useful work happens before you walk into the room. The Dealing with an Underperformer Blueprint in The Leader's Toolkit is built for this step. It asks you to write down three things before you speak:
- Who is not meeting the standard, and what exactly is falling short. Your facts from above.
- What conversation you'll have, and what support or consequence you'll make clear. Write your opening line, and what "better" would look like.
- What happens next, and by when. Decide this before you go in, not in the moment.
Write the opening sentence out and say it aloud once. The opening is where most managers soften the message until it means nothing. Something like:
"I want to talk about the quality of the weekly reports. The last four have needed significant rework, and I need that to change. I'd like to understand what's getting in the way, and agree a plan."
That's clear, specific and not an attack. It also makes it obvious this isn't a casual chat.
During the conversation: say it once, then listen
Book 30 minutes in private. Don't do this at the end of a routine 1-1 or in a corridor. A structure that works:
- State the issue plainly with your opening line and two or three examples.
- Ask, then actually listen. "How do you see it?" or "What's getting in the way?" This is where you find out whether it's ability, will or something else. Sometimes you'll hear about an unclear brief, a workload nobody noticed, or a problem at home.
- Agree what "good" looks like. Be concrete: "Reports go out by Thursday at noon, totals checked against the dashboard, no more than one round of edits."
- Agree the support. Training, a weekly check-in, pairing with a colleague, removing another task so they have room.
- Set a review date, usually two to four weeks out, and put it in both calendars.
Don't bring a script into the room and read from it. Do the thinking beforehand, so in the meeting you can listen properly. The Feedback card is the one to prepare with, and its main point is the one most of us need: waiting rarely makes it kinder. For more on the conversation itself, including what to do when someone gets defensive, see our guide on how to give difficult feedback to an employee.
If they think they're doing well
This is one of the most common versions of the problem. A widely shared r/managers thread asks how to handle an underperforming employee who believes they're excelling: feedback never seemed to land, and coaching made them defensive.
When someone genuinely believes they're doing well, the gap is usually in one of three places:
- The standard was never explicit. They're measuring themselves against what they think the job is.
- The feedback was too soft. "Maybe double-check the numbers next time" sounds optional.
- They compare themselves to the wrong people, or to how they used to perform.
Don't argue about their self-assessment. Show the gap instead: put the standard and the last few pieces of work side by side. "Here's what we agreed good looks like. Here are the last four reports. Where do you think they land?" It's much harder to stay defensive when the evidence is on the table and you're asking, not telling.
After the conversation: follow up in writing, then coach
The same day, send a short note summarising what you agreed: the issue, what good looks like, the support you'll provide and the review date. It isn't a legal document. It makes sure you both heard the same thing, and it gives you a record if things don't improve.
Then keep the review date, and use your regular 1-1s in between to check progress. The Coaching card helps here. Ask what's working, what's still getting in the way, and what they'll do differently next week. Notice improvement out loud, specifically and quickly. People working through a performance issue often feel watched, and recognising progress is what makes it stick.
Protect the rest of the team
One r/managers post put the trap well: the writer spent months rewriting a struggling report's work and shielding him, only for two top performers, who'd been quietly absorbing his backlog, to resign in the same week. Their conclusion was that they'd confused endless leniency with empathy.
While you work on one person's performance:
- Stop quietly redistributing their work. If others are covering, the team already knows, and they're watching what you do.
- Don't rewrite their output yourself. It hides the problem from everyone, including them.
- Check in with the people closest to the gap. You don't need to share details, just that you're aware and acting.
Being supportive and being clear aren't opposites. The kindest thing for the struggling person and the team is the same: a clear standard, real support and a decision on a fixed date.
When it doesn't improve: the formal route
If the review date comes and nothing has changed, move to a formal plan. A Performance Improvement Plan shouldn't be the first time someone hears they're falling short. If you've done the steps above, it won't be.
The Performance Improvement Plan card sets out what a fair plan needs:
- The gap in plain language, with the examples you've already discussed.
- What better looks like, and by when. Specific enough that you'd both agree whether it happened.
- The support you'll provide.
- Review points and the consequence if the standard isn't met.
Bring HR in before the plan, not after. Our guide to putting someone on a PIP for the first time walks through it step by step.
A PIP isn't automatically a formality on the way out. One r/managers user came back to say they'd passed their PIP, after most replies to their first post had told them the decision was already made. A plan that's specific and properly supported gives people a real chance.
Situations you'll recognise
These threads in r/managers inspired this guide. The replies are worth reading in full:
- "I've tried extra 1-1s, clearer expectations and pairing, and progress is slow" (r/managers). You've done the support. What's missing is the review date and a clear "what happens next". Go back to the Blueprint and decide it.
- The underperformer your own boss hired (r/managers). The writer described documenting one-on-ones and involving HR early, over several months. When the person who hired them is above you, evidence and process matter even more than usual.
- The first-time manager who "protected" a poor performer (r/managers). Their advice to other new managers: give the feedback, rate the performance honestly and document it, because delaying only makes it harder.
- The employee who'd rather go on a PIP than change how they work (r/managers). When someone turns down the support you offer, that's useful information about will, not ability.
Mistakes that make it worse
- Hinting instead of saying it. "Maybe have another look at this" isn't feedback. The person can't act on what they don't hear.
- Saving it for the annual review. By then it's months of evidence they've never seen, and it feels like an ambush.
- Fixing the work yourself. It solves today and guarantees tomorrow.
- Skipping the "why". If you never find out whether it's ability or will, you'll keep applying the wrong fix.
- No date. Without a review date, the conversation becomes a one-off, and both of you know it.
The cards for this situation
These cards from The Leader's Toolkit cover the whole process. Use them to prepare before the conversation and to follow up after it:
- Dealing with an Underperformer (Blueprint): name the gap, write your opening line and decide what happens next.
- Ability vs. Will: work out whether to train, coach, change the work or make a clearer decision.
- Setting Expectations: spell out what good looks like, so nobody's guessing.
- Feedback: prepare the conversation you've been putting off.
- Coaching and 1-1s: follow up week by week.
- Performance Improvement Plan: the formal route, done fairly.
The Leader's Toolkit has 52 tools on 54 cards for situations like this one, and over 6,000 copies have been sold.
Frequently asked questions
How do you deal with an underperforming employee?
Write down the specific gap with examples, work out whether it's a skill problem or a motivation problem, then have a private, direct conversation: state the issue, listen, agree what good looks like and the support you'll give, and set a review date two to four weeks out. Follow up in writing the same day.
What do you say to an underperforming employee?
Open with the specific issue and its impact, not a label. For example: "The last four reports have needed significant rework, and I need that to change. I'd like to understand what's getting in the way." Then ask for their view and listen before agreeing a plan.
How long should you give an underperforming employee to improve?
Set a first review two to four weeks after the conversation, with weekly check-ins. If there's no meaningful change by then, move to a formal plan with clear review points. The right timeline depends on the role and the size of the gap, so check your company's process with HR.
When should you put an employee on a PIP?
When you've already given clear feedback, agreed what good looks like, offered support and reviewed progress, and the gap remains. A PIP should never be the first time someone hears they're falling short.
How do I handle an underperformer who thinks they're doing a great job?
Don't argue about their self-assessment. Put the agreed standard and their recent work side by side, and ask where they think it lands. If the standard was never written down, start there.