Get 1 month of Premium free

Use the code at checkout

00Days
00Hours
00Mins
00Secs
Claim 1 month free

BlogTeam Management

How to Handle an Underperforming Team Member

Diagnose before you act: underperformance is usually a clarity, capability, capacity, or motivation problem, and each needs a different response. Name the gap specifically, agree what good looks like and by when, then check in weekly. Most cases resolve. The ones that do not should not be a surprise to either person.

Diagnose before you act

The mistake is treating underperformance as one thing. It is usually one of four, and the right response is different in each case.

The real problemWhat it looks likeWhat actually helps
ClarityThey are working hard on the wrong thingsRestate the outcome and priorities explicitly
CapabilityThey understand the goal but cannot execute it yetTraining, pairing, or a smaller scope
CapacityQuality drops as volume risesRemove work, or fix the process creating it
MotivationCapable, was fine before, has disengagedA direct conversation about what changed

Check the manager-side causes first

Before concluding it is the person, check whether the expectation was ever stated, whether the role changed without being redefined, and whether they have had feedback in the last three months. These account for a surprising share of cases and are the cheapest to fix.

Clarity problems are the most common and the most often misread as attitude. Someone delivering the wrong thing consistently and confidently is almost never being difficult, they are working from a different understanding of the job than you are.

The conversation

Private, direct, and early. The most damaging version of this conversation is the one that happens six months late, because by then the person has had months of believing things were fine.

  1. Name the gap with examples

    Two or three specific instances, not a general impression. "The last three reports went out after the deadline, and two had figures that had to be corrected."

    General statements about performance cannot be acted on and cannot be fairly argued with. Specifics can be both.

    Two or three examples
  2. Ask what is going on, and mean it

    Then be quiet long enough for a real answer. Illness, a situation at home, a tool that has been broken for a month, an instruction from someone else that contradicts yours.

    This question resolves a meaningful number of cases outright, and skipping it is how managers end up managing a problem that was never the one they thought.

    Ask once, then wait
  3. State what good looks like

    Concretely and measurably where possible. "Reports out by Thursday midday, figures checked against the source before sending."

    If you cannot state the standard clearly, you cannot fairly hold anyone to it, and the conversation should pause until you can.

    Measurable where possible
  4. Agree the timeframe and the check-ins

    A defined period, usually four to eight weeks, with a short weekly review. Write down what was agreed and send it to them the same day.

    The written record protects both of you. It also stops the standard drifting, which is what happens when this is left as a verbal understanding.

    Written, same day

Giving a real chance

A real chance has three components, and most attempts are missing at least one.

Regular contact. Weekly, short, focused on the specific gap. Setting a target and then reviewing it in eight weeks is not support, it is an exam.

Something removed. If someone is failing at their current workload, adding an improvement plan on top of it makes success less likely. Take something off the list.

An honest statement of the stakes. People deserve to know whether this is a work-on-it conversation or a this-needs-to-change conversation. Being vague to soften it is the single most common regret managers report afterwards, because the person genuinely did not realise.

Deciding it is not working

At the end of the agreed period, there are three honest outcomes: fixed, improving with a clear trajectory, or not working.

The middle one deserves more time, once. The third one deserves a decision.

What makes this fair is that nothing about it is a surprise. If you have had weekly conversations against a written standard, the person already knows where they stand, and the final conversation confirms something they have seen coming. The version that is genuinely cruel is the one that arrives out of nowhere after months of silence.

Get proper employment advice for your jurisdiction before anything that ends someone's employment. The process and notice requirements vary considerably, and getting the substance right does not protect you from getting the procedure wrong.

What the rest of the team sees

The thing managers underestimate: everyone already knows.

If someone is not delivering, the people picking up the slack are aware of it, and they are watching what happens. Unaddressed underperformance is read as either an absence of standards or a lack of nerve, and it costs you with the people who are performing well.

You do not discuss the conversation with anyone else, and you should not. But the team will notice that the work started arriving on time, or that a change happened. Both are better signals than a situation that never resolves.

Frequently asked questions

How long should I give someone to improve?
Long enough to show a trend, which for most roles is four to eight weeks. Shorter than that and you are measuring noise. Much longer and it becomes indefinite, which is unfair to the person because it never resolves.
Should I put someone on a formal performance plan?
In a small company, a written agreement between the two of you usually does the same work with less fear attached. What matters is that it is specific and written down, not that it carries a formal name. Take employment advice before anything that could end in dismissal.
What if the person disagrees that there is a problem?
That is usually a sign the standard was never made explicit. Move the conversation to specific examples and to what you expected instead. If they still disagree after seeing specifics, you at least both know the disagreement is real rather than a misunderstanding.
Is it my fault if someone underperforms?
Often partly, and it costs nothing to check. Unclear expectations, a role that changed without being redefined, missing context, and no feedback for months are all manager-side causes, and all of them are cheaper to fix than a replacement hire.
How do I handle it if the person is well liked?
The same way, and privately. Being liked is not a reason to avoid the conversation, and colleagues generally know before you do. What damages a team is not addressing underperformance, it is watching it be ignored.
Danish Khan

Danish Khan

CEO & Founder, Siela

Danish Khan is the CEO and founder of Siela, an AI-native workspace where teams and AI agents run CRM, meetings, tasks, and daily work together on one shared context layer.

Connect on LinkedIn

Published