How to Talk to an Underperforming Employee Before It Becomes a PIP

Published August 7, 2026

The signs are rarely dramatic at first. A deadline slips by a day, then two. A code review comes back with more back-and-forth than usual. Someone who used to jump into a thread now waits to be asked. None of it, on its own, is enough to say anything about, and most managers don't. That hesitation isn't wrong. Reacting to a single rough week is its own kind of mistake, one that teaches people to hide when they're struggling instead of asking for help.

The problem isn't the hesitation. It's what happens after the hesitation turns into a habit. Three weeks becomes six, six becomes a quarter, and somewhere in there the manager stops asking whether this is actually a pattern and starts quietly building a case, waiting to feel certain enough to say something. By the time they're certain, the gap between what's actually been said out loud and what's been building in private is wide enough that the first real conversation about it can only happen as something formal. HR gets looped in. A document gets drafted. And the employee, who never heard so much as an informal heads-up, understandably feels blindsided by a process that, from where they're standing, came out of nowhere.

That gap is avoidable. This is the conversation that's supposed to happen before any of that: informal, early, and specific enough to actually mean something.

The Gap Between a Bad Week and a Pattern

Every manager has, at some point, said something over one bad sprint and immediately regretted it. Reacting to noise instead of signal costs you something real: the person walks away treating every future rough patch as something to hide rather than something to mention, which is exactly the opposite of what you want.

The distinction that actually matters isn't severity, it's repetition. One missed deadline is a data point. The same kind of miss three times in six weeks, even if each instance felt minor and explainable on its own, is a pattern. The test worth applying before you say anything: can you name two or three specific instances, not a general sense that things feel off? If you can only describe a mood, you're not ready to have this conversation yet. If you can name a date, a ticket, a meeting, you probably are.

Why Waiting Costs More Than Saying It Early

Delay feels safe because nothing visibly happens while you wait. None of that is actually neutral. Every week you don't say anything is a week the employee doesn't know there's a concern to address, which means every week their sense of their own standing and your actual assessment of it drift a little further apart. When the conversation finally happens, you're not just delivering the original concern anymore, you're also explaining why you sat on it, and that second part is often what does the real damage to trust.

There's a second cost that's easy to miss: the longer you wait, the higher the stakes feel when you finally do say something, which makes the conversation harder to start, which makes you more likely to wait even longer. Saying it early, while it still feels like a minor thing worth mentioning, is what keeps this conversation small enough to actually have.

Naming It Without Making It Formal

The instinct once you decide to say something is to soften it until the actual point gets lost. Wrapping a real concern in three compliments and a joke about everyone having off weeks doesn't make the conversation kinder. It just makes it possible for the other person to walk away without having heard it at all.

Naming it plainly doesn't mean naming it harshly. It means saying, specifically and without hedging, what you've noticed. "The last three pull requests took twice as long to get through review as usual, and I want to understand what's going on" is a sentence someone can actually respond to. "Just wanted to check in and see how things are going" is not, because it gives them nowhere to go except a vague "fine."

Keep it private, keep it close to when you actually noticed the pattern, and say it as an observation you want to understand, not a verdict you've already reached.

What Happens After You Name It

The part managers plan for least is what to do with the answer. If you've correctly separated a pattern from a bad week, there's almost always a reason behind it, and it's rarely the first one you'd guess. Sometimes it's a skill gap. More often it's something more ordinary: an unclear handoff from another team, a scope that quietly grew without anyone renegotiating the deadline, or something happening outside work that has nothing to do with capability at all.

Whatever the answer is, take it at face value in the room. You don't have to accept it uncritically forever, you can weigh how much it actually explains later, on your own time. But treating an explanation as an excuse in the moment teaches someone to stop offering explanations at all, and then you've lost the one piece of information that would have told you what to actually do next.

When This Should Actually Become a PIP

Not every performance concern needs to end in a formal process, and it's worth being honest with yourself about when the line actually gets crossed. Informal is the right register when this is the first time you're naming the pattern, when there's a plausible, addressable reason behind it, and when both of you can agree on something concrete to check back on.

It usually needs to become formal when one of those stops being true: you've had this conversation before and the pattern didn't change, the explanation doesn't actually account for the gap, or there's a real team impact that can't wait out another quarter of "let's see." When that happens, the fact that you already had an honest, specific, informal conversation is what makes the formal one feel like a continuation instead of an ambush. The 1-on-1 Template for a Performance Improvement Plan (PIP) picks up exactly where this conversation leaves off.

Frequently Asked Questions

How is this different from just giving feedback in a normal 1-on-1?

Ordinary feedback usually addresses a single moment, a specific PR, a specific meeting. This conversation is different because it's naming a pattern across multiple instances and asking, out loud, whether it's something bigger. It needs its own moment, not a few sentences tacked onto the end of an unrelated check-in.

What if I'm wrong and it isn't actually a pattern?

That's a perfectly fine outcome, and framing the conversation as an observation you want to understand, rather than a conclusion you've already reached, makes it easy to be wrong without it costing you anything. Worst case, you've told someone you're paying attention, which is rarely unwelcome.

Do I need to involve HR for this conversation?

No. This conversation is specifically the informal step that happens before any formal process, and formal processes are usually where HR gets involved. If the pattern continues past this conversation, that's the point to loop in HR, not before.

What if they get defensive or upset?

That's a reasonable reaction to hearing something they didn't expect, and it doesn't mean you handled it wrong. Stay with the specific examples you came in with, resist the urge to soften your original point just to defuse the moment, and give them room to respond once the initial reaction has passed.

Related Guides

Fix your 1-on-1s today.

No credit card required. Free forever for up to 3 reports.
Or try the live demo without signing up.