I don't believe in "performance management" as most managers practise it. I believe in diagnosis. Give me an underperforming team member and the first thing I want to know isn't how bad it is — it's why. Skill gap, unclear brief, or motivation problem: those are three completely different fixes wearing the same disguise, and most managers reach for the same blunt tool regardless. That's the mistake. Not the person — the diagnosis.
Poor performance is a system to repair, not a character flaw to punish — that's the reframe I use with every client. An unclear brief, a missing skill, a feedback loop that never closes the loop — fix the structure and the performance usually follows. Discipline the person instead, and you don't fix the structure. You just lose the person, and the structure breaks the next one too.
How do you coach poor performance as a manager?
Coach poor performance by working through a sequence, in this order: diagnose the real cause, set clear and measurable expectations together, give regular feedback paired with genuine recognition, offer targeted development, and build the supportive conditions in which someone can actually improve. The order is not decoration — it's the whole method. Skip the diagnosis and jump to a development plan and you'll train a skill the person already has. Jump to feedback before you've set expectations and you're giving someone notes on a performance they were never told they were meant to give. The five strategies below walk through that sequence, in the order I actually use it with clients — not the order that makes a tidy listicle.
How I actually diagnose underperformance
- The Brief Test: Ask the person, alone, to describe what "good" looks like in their own words. If their answer doesn't match yours, you have a clarity problem, not a performance problem — and no amount of coaching fixes a target nobody can see.
- The Repeat Test: Has this exact failure happened before, to this exact person, in this exact context? If yes, it's a skill gap or a broken process. If it's new and situational, it's more likely motivation, capacity, or something happening outside work.
- The Energy Test: Watch how they talk about the work, not just the output. Frustration and effort with poor results usually means a skill or resource gap. Flatness and disengagement usually means motivation — and no training course touches that.
- The Feedback-Loop Test: Ask when they last received specific, timely feedback on this exact task. If the honest answer is "months ago" or "never," the system failed before the person did — fix the loop before you fix the individual.
- The Manager-Mirror Test: Before assigning cause, ask what you did or didn't do — brief clearly, check in, remove blockers. Most managers skip this step because it's uncomfortable. It's usually the most diagnostic one.
Poor performance inside a team doesn't just dent one person's output — left alone it drags down morale, slows the whole group, and quietly recalibrates what "acceptable" means for everyone watching. That's why speed matters here almost as much as method. A structural problem you catch in week two is a conversation. The same problem left until the annual review is a resignation, or a termination, or both.
It's tempting to reach for punishment or a quiet exit plan the moment performance dips — it feels decisive, and it feels like accountability. It's neither. It's the fastest way to lose a person you could have kept, and to leave the actual cause — the brief, the skill gap, the broken feedback loop — sitting there ready to catch the next person too. A proper leadership capability lens gives you the diagnosis before you reach for a remedy. Here are the five moves I actually use, and the order I use them in.
1. Conduct a Leadership Capability Assessment
Everything downstream depends on getting this diagnosis right, which is why I put it first and refuse to skip it, even under pressure to "just deal with it" quickly. A leadership capability assessment is my structured way of separating skill gap from motivation problem from unclear expectations, by looking directly at leadership skills, decision-making patterns, and behaviours under pressure, rather than guessing from the outside. Managers who skip this step tend to default to their own explanation — usually the one that requires the least of them — and that's exactly the bias a structured assessment exists to correct.
Benefits of Leadership Capability Assessment
Identifying Skills Gaps: An assessment surfaces exactly where someone lacks a necessary skill, so training or mentorship is targeted rather than generic and hopeful.
Understanding Motivation Issues: A proper assessment separates "can't" from "won't" — and those two get completely different interventions from me, never the same one.
Personalising Development Plans: Once you know the actual cause, the development plan writes itself. Guess the cause, and the plan is just activity dressed up as strategy.
A well-executed leadership capability assessment gives you the tools to address performance strategically, at the root, instead of managing the visible symptom on repeat.
2. Establish Clear Goals and Expectations
I'd guess — from pattern, not from a stat I can cite — that unclear expectations account for more "performance problems" than actual skill or will problems combined. When someone doesn't know precisely what good looks like, their performance drifts, and it's unfair to call that drift a personal failing. Set goals that are clear, measurable, and genuinely achievable, and tie them back to why the role exists, not just what the org chart says it should produce — that's the difference between a target someone owns and a target someone tolerates, and it's what I mean when I talk about core leadership capability in practice rather than in theory.
How to Set Clear Goals
SMART Goals: Specific, measurable, achievable, relevant, time-bound — not because the acronym is clever, but because vague goals are where accountability goes to die.
Frequent Check-Ins: I don't wait for the annual review to find out something's off. Neither should you. Short, regular check-ins catch drift while it's still cheap to correct.
Collaborative Goal-Setting: Goals someone helped write get defended. Goals someone was handed get tolerated, at best, and quietly resented at worst.
Clarity isn't just an efficiency tool. It's what lets someone actually own their work instead of managing your expectations of them — which is a completely different, and much more draining, job.
3. Provide Consistent Feedback and Recognition
Save feedback for the review cycle and you've made it an event instead of a habit — and events feel like verdicts, which is exactly what makes people defensive instead of receptive. I want feedback to be so routine it stops feeling like a big deal at all. That's what actually builds trust between a manager and a team — not the annual form, the weekly habit. Feedback needs to be specific and tied to behaviour or outcome, never to character. "You missed the deadline because the brief changed twice" is feedback. "You're not reliable" is a verdict, and verdicts don't change behaviour — they just make people stop telling you the truth.
The Importance of Recognition
Encouraging Positive Behaviours: Naming a small win out loud, specifically, does more for the next attempt than a generic "great job" ever will.
Improving Morale: Recognition that's specific reads as attention. Recognition that's generic reads as a script — and people can tell the difference instantly.
Developing Trust: The teams that come to me with problems early, before they're crises, are always the ones where feedback flows constantly in both directions, not just downward at review time.
Get the feedback rhythm right and recognition stops being a separate task on your list — it becomes a by-product of paying proper attention to the work.
4. Offer Tailored Development Opportunities
Once the diagnosis says "skill gap," development is the fix — but only if it's aimed at the actual gap, not the nearest training catalogue entry. Generic leadership courses handed out as a blanket response to underperformance are, frankly, a waste of budget and a signal to the person that you didn't bother to find out what they actually needed. Match the intervention to the diagnosis, every time, or don't bother.
Ways to Offer Development Opportunities
Leadership Coaching: One-to-one coaching works because it's built around the individual's actual gap, not a syllabus written for a room of strangers.
Job Rotation: Sometimes the fastest way to build a missing skill is to put someone in a different role within the business where they're forced to use it, not told about it in a workshop.
Training and Certifications: Useful, but only after diagnosis — training thrown at a motivation problem doesn't just fail to fix it, it can make the person feel more managed and less trusted.
Tailored development is slower to set up than a generic course and faster to actually work. That trade-off is worth making almost every time.
5. Foster a Collaborative and Supportive Environment
The environment someone performs in is not a soft add-on to the other four strategies — it's the substrate all of them either take root in or die in. A brilliant development plan handed to someone on a team that punishes mistakes in public will not survive contact with that culture. Fix the individual all you like; if the environment stays hostile, the recovery won't stick. That's why I always look at team dynamics alongside individual coaching, and it's also why I push clients to address ethical challenges in the workplace directly — fairness and psychological safety aren't nice-to-haves, they're the conditions performance recovery actually depends on.
Tips for Fostering a Collaborative Environment
Team Building Activities: Less about the activity itself, more about giving people a low-stakes reason to trust each other before a high-stakes moment demands it.
Open Communication: If concerns only surface in exit interviews, communication was never actually open — it just felt that way from your side of the desk.
Supportive Leadership: Being approachable isn't a personality trait you either have or don't. It's a set of behaviours — responding well to bad news is the one that matters most.
A genuinely collaborative environment is what turns a one-off coaching win into a durable change in how someone performs, month after month, not just in the weeks you're watching closely.
The distinction I want you to take from this
If you remember one thing from this article, make it this: performance management and performance coaching are not two words for the same activity. Performance management asks "how do I document this so I'm covered if it comes to an exit?" Performance coaching asks "what's actually broken, and how do I fix that?" Those two questions produce completely different conversations, completely different plans, and completely different outcomes — and most organisations default to the first one while telling themselves they're doing the second.
I'll go further: the managers who get the best results from underperforming team members are not the ones with the most patience, or the most empathy, or even the most technical skill at giving feedback. They're the ones who resist the urge to act before they've diagnosed. That patience at the front end — the two or three conversations spent genuinely working out whether this is a skill gap, a motivation issue, or a clarity failure — is what makes everything after it land. Skip it, and even a technically well-delivered feedback conversation is aimed at the wrong target.
This is also why I'm sceptical of any "5-step performance improvement process" that starts with the goal-setting step. Goals set before diagnosis are goals set blind — you might get lucky and land on the right fix anyway, but you're gambling with someone's role, and often their confidence, on a guess. Diagnose first. Always. It's the one step in this sequence I will not let a client skip, no matter how much time pressure they're under.
Coaching beats discipline because it treats the cause instead of managing the symptom. That's not a motivational line — it's the mechanism. Fix the structure — the brief, the skill, the feedback loop — and the person you almost lost becomes one of your strongest performers, because you were the manager who actually worked out what was wrong instead of the one who simply decided who was to blame. That's the whole distinction. Everything else in this article is method.
Further reading: The Silent Killer of Growth