Coaching an Underperforming Employee Back on Track

Most performance dips do not need a PIP. They need someone to name the problem specifically, find out what's actually behind it, and build a short, concrete plan to close it, before it hardens into something that does need a formal process. These are the principles that make that coaching phase actually work, rather than just being a softer word for the same conversation.

The principles

These aren't steps to complete in order - they're the things worth checking yourself against, before and during the work. Read them once, then keep this page open while you go.

1. Name the specific gap, not a general impression

   "Their performance has slipped" is a feeling, not something anyone can act on. The coaching only works once you can point to the exact behavior or output that changed, and state what it should look like instead.

   • Write one sentence describing the gap in terms of observable output or behavior, not character - "missed three of the last four sprint commitments" rather than "seems checked out."
   • Check that you can point to specific instances with dates, not a general sense built up over weeks. If you can't name three examples, you may not be ready to have this conversation yet.
   • Compare the gap against what was expected of the role, not against what the strongest person on the team is doing. The bar is the job, not their highest-performing peer.

2. Diagnose the cause before you prescribe anything

   A skill gap, a motivation problem, unclear expectations, a change in personal circumstances, and a mismatch between the person and the role can all produce the exact same symptom on the outside. Coaching aimed at the wrong cause wastes the runway you have before this needs to become formal.

   • Ask directly, early, and without accusation: "I've noticed X. What's going on from your side?" Most managers skip this and go straight to a fix, which means the fix is often aimed at the wrong problem.
   • Rule out whether the person actually knows what's expected of them. A surprising number of performance dips trace back to expectations that were never clearly stated, not to a drop in effort or capability.
   • Watch for whether this coincides with a change outside work. It doesn't excuse the performance gap, but it changes what kind of support actually helps versus what just adds pressure.
   • Notice if the gap is isolated to one area or spread across the role generally. A narrow gap usually points to a skill or knowledge issue; a broad one more often points to motivation, fit, or something personal.

3. Distinguish won't from can't

   Someone who can't yet do something needs training, practice, and time. Someone who won't do something they're capable of needs a different conversation about motivation, priorities, or whether this role still fits them. Coaching that treats a won't as a can't just produces more of the same slippage with extra steps.

   • Ask yourself honestly: if I watched them attempt this task right now with full effort, would they succeed? If genuinely unsure, that uncertainty is itself useful information.
   • For a can't, check whether they've actually had real instruction and practice, not just exposure. Having sat in on something twice is not the same as having been taught it.
   • For a won't, ask directly what's competing for their attention or effort, rather than assuming it's simply a bad attitude. The answer is sometimes a legitimate priority conflict you didn't know about.
   • Watch for a can't they're presenting as a won't out of pride, or the reverse. It happens more than either party usually admits.

4. Put a short written plan in place, even though it's not a PIP

   A verbal coaching conversation is easy for both sides to let fade once the discomfort passes. A short written plan, even an informal one, gives the improvement something concrete to be measured against and makes it much harder for either of you to later disagree about what was actually agreed.

   • Write down the specific gap, two or three concrete actions to close it, and a date to check back in - two to four weeks is usually the right window for a first check-in, not months out.
   • Make each action something you can actually observe, not an intention. "Will ask more questions in planning" is unverifiable; "will flag blockers in standup by day two of being stuck" is not.
   • Keep the tone genuinely developmental in how it's written, not punitive. The substance can still be direct. This document is meant to be a support, not a warning shot dressed up as one.
   • Decide together, where possible, rather than only handing it down. A plan the person had a hand in shaping tends to get followed with more ownership than one that was purely dictated.
   • Logging progress against each action somewhere, even a simple record like Perform Review's Achievement Log, makes the check-ins concrete instead of a rough memory of how things have been going.

5. Set a real check-in cadence, not a single distant deadline

   A plan with one review date two months out gives someone eight weeks to either fix things or quietly hope you forget. Short, regular check-ins catch a stall early enough to actually do something about it, instead of finding out everything at the deadline all at once.

   • Check in weekly or every two weeks, not just at the final review point. The whole value of catching this early is lost if you only look again at the end.
   • At each check-in, look at actual evidence against the specific actions from the plan, not a general "how's it going" that's easy to answer vaguely.
   • If there's real progress, say so specifically and say it early. People coasting on assumed failure often give up on effort that would have actually worked.
   • If there's no movement by the midpoint, don't wait for the final date to say something. Raise it as soon as you see it stalling, while there's still time left to react.

6. State what happens if it doesn't improve

   Coaching without a stated consequence can read as unlimited patience, and unlimited patience is not always the kindness it seems to be. It can leave someone unprepared for a formal process that then feels like it came out of nowhere, and it also isn't fair to a team quietly absorbing the gap.

   • Say plainly, once, what happens if the plan isn't met by the review date - typically that it moves to a formal PIP - without turning every subsequent conversation into a threat.
   • Confirm this matches what HR or your own manager would expect at this stage, so you're not promising a timeline or a consequence you can't actually follow through on.
   • Notice if you're avoiding saying this because it feels harsh. Most people can tell when a manager is being vague to spare themselves the discomfort, and it doesn't actually spare the employee anything.
   • If it does progress to a formal PIP later, make sure the informal plan and its documented check-ins are the foundation for it, not a separate process that starts from zero.

7. Protect your own consistency across the team

   An underperforming employee's teammates are usually already aware something is off, whether or not you've said anything to them directly. How evenly you apply this process, compared with how you've handled similar gaps before, is what determines whether the team reads this as fair management or as favoritism running in either direction.

   • Compare how you're handling this against how you've handled a similar gap with someone else recently. A material difference in patience or process is worth being able to explain to yourself, even if you never have to explain it to anyone else.
   • Keep specifics about the plan between you and the employee. The team doesn't need details, but an unexplained shift in how you're managing someone publicly invites speculation that helps no one.
   • If the underperformance is affecting teammates directly, such as missed handoffs, address the impact on them honestly without disclosing the coaching plan itself.

That's the whole playbook

None of this replaces judgement. It is the checklist for catching the moments where judgement quietly turns into habit, or into bias.