Not the difficult one. Not the person who creates conflict or makes the office tense the moment they walk in. This is someone else entirely. This is the one everyone likes. The one who's friendly, easy to be around, and always has a reasonable explanation when something slips. The one who's busy all day but somehow never quite gets to the work that actually matters. The one who asks the same question for what feels like the fiftieth time, even though the process has been explained, documented, and walked through more than once. The one who keeps doing things their own way no matter how much coaching goes into it. The one who means well, genuinely, and that's exactly what makes this so hard.

By now you've probably pictured them. Not because you set out to, but because the red flags you'd been quietly waving away start lining up, and this isn't right, and it becomes hard not to see that the person you like, the person you'd been giving the benefit of the doubt to, is actually the person who isn't the right fit.

It's rarely one thing

These situations don't usually start with a dramatic failure. None of it looks like a crisis. It looks like a series of small, forgivable moments, and that's precisely the problem. They build slowly, almost invisibly, out of things we could act on but don't, because the person is nice and it feels wrong to make a big deal out of something small. The same question asked again. The same mistake repeated.

A process explained for the third or fourth time. Work handed back not quite right. Priorities misread. Time spent on busy work instead of what was actually needed. Simple problems escalated instead of solved.

On their own, none of these moments feel worth a serious conversation, not because they're too small to matter, but because raising them feels disproportionate against someone who's likeable and clearly trying. That's what makes the pattern so easy to miss, or so easy to excuse. If this same person were short with people, or hard to work with, or made the office feel tense, these exact same issues would have been called out months ago.

You're not dealing with one bad decision, you're dealing with an accumulation, and accumulations are much harder to point to than incidents. There's rarely a single moment you can put your finger on and say "that's when it went wrong." Instead there's just a slow, creeping sense that something isn't quite right.

There's another layer to this that makes it even trickier. Because this person is busy, genuinely busy, they often believe they're doing well. They're at their desk early, they answer messages quickly, they're never seen sitting idle. What they're not doing is the work that actually moves the needle, and that distinction is invisible to them. Busyness feels like performance from the inside. So when a leader does try to raise a concern, it lands as confusing rather than clarifying, because as far as the employee can tell, they've been working hard the whole time. That gap between how someone sees their own effort and how their output actually stacks up is a big part of why this is so hard to shift with a gentle nudge.

Everybody already knows

Here's the part most leaders don't say out loud: we usually know much earlier than we admit. Not months in. Not by the end of probation. Certainly not a year later when we're finally having the performance conversation.

There's often a point, sometimes within the first few weeks, where something doesn't quite sit right. Not because the person is doing anything terribly wrong. Not because they're difficult. Just a quiet sense that this role, this team, or this environment may not be bringing out the best in them.

And what happens next is very human. The leader hopes it will improve. They offer more training, more support, more time, another chance, another conversation that dances around the real issue instead of naming it. It comes from a good place. Nobody wants to be the person who gives up on someone too soon. But somewhere along the way, kindness quietly turns into delay, and delay starts to cost more than anyone realises.

Part of the reason this drags on comes down to something psychologists call the halo effect: we let one positive trait, like being likeable or hardworking, colour how we read everything else. The missed deadline becomes a workload problem. The repeated mistake becomes a training issue. The same question asked for the tenth time becomes a sign they're trying hard to get it right. The behaviour hasn't changed, only our interpretation of it. It's not the behaviour that's buying them time, it's the personality.

Most leaders don't do this consciously, but it happens more often than we'd like to admit. We spend so much time asking whether someone is a good person that we forget to ask whether they're actually a good fit for the role.

The team starts covering

While the leader is hoping things will turn around, something else is happening on the team. People start protecting their colleague, often without even noticing they're doing it. They answer the repeated questions. They quietly fix the mistakes. They double check the work before it goes anywhere important. They pick up the tasks that didn't get done. They fill the gaps, again and again, because the person is nice and nobody wants to be the one who makes a fuss.

The business keeps functioning, but only because everyone around this person is compensating for it. And over time, that compensation breeds something quieter than anger, more like resentment, and it's rarely directed at the employee. It's directed at leadership. The team starts wondering, sometimes out loud and sometimes just among themselves, why nobody is doing anything about it. They're not being unkind. They're just tired of holding something up that isn't being addressed.

When accountability finally shows up

Eventually, something forces the issue. A deadline missed at the wrong moment, a client complaint, a new leader who notices what's been quietly tolerated for too long. And when that accountability conversation finally happens, three very different reactions show up in the same room.

The employee is shocked, because in their mind nothing has really changed. They've rarely had a direct, honest conversation about where they stand, so from their perspective this feels sudden and unfair. If anything, they'd have told you they were doing a good job right up until that meeting, because they measure themselves by effort and activity, not by outcomes, and nobody had ever really shown them the difference. The team feels relief, because something is finally being said that they've been thinking for months. And the leader feels exhausted, carrying the quiet weight of having managed around this for a year or more without ever properly naming it.

Leaders can usually sense this shock coming before it happens. There's often a quiet dread attached to these conversations, a sense that whatever is said is going to land as a surprise no matter how it's delivered, because the softer conversations that came before it never really landed either. Those earlier chats about "let's tighten up on X" or "keep an eye on Y" were heard as passing feedback, not as warnings. They were too gentle to cut through someone's genuine belief that they were performing well, so they got filed away as minor and forgotten. That's often exactly why leaders keep circling back with more time and more chances. Somewhere they already sense that nothing has actually landed yet, and that the real conversation still hasn't happened.

All three reactions make complete sense. But the real issue was never that final conversation. The real issue is everything that didn't get said clearly enough, early enough, in the months before it.

Probation isn't a trap, it's a test in both directions

This is where I think we need to rethink how we talk about probation. It's not a mechanism for catching people out, and it shouldn't feel like one. It's a genuine, mutual assessment period, and it runs both ways.

The employee is quietly assessing the role, the leadership, the culture, whether this business is actually what it looked like from the outside. And the employer is assessing capability, values, behaviour, whether this person fits the team and can do what the role actually requires. That's not a harsh process, it's a sensible one.

It's also worth being honest about what work actually is. It's a relationship as much as it's a fee for service, and like any relationship, both sides have to be reasonably aligned or it doesn't hold. That doesn't mean everyone working for you has to be brilliant every single day.

We're human, and an off week or a rough patch isn't a performance issue, it's just life. But there's a real difference between someone who's consistently good, who does the job they were hired to do, and someone who isn't meeting even a minimum standard on an ongoing basis. Treating the second as though it's the same as the first, out of kindness or hope, is usually where the real trouble starts.

Not every role suits every person, and that's not a failure on anyone's part. I've watched people struggle in one workplace and genuinely thrive somewhere else, doing similar work, just in a different environment with different expectations and different support. A mismatch isn't a verdict on someone's character or worth. It's just a mismatch, and the sooner it's named, the less damage it does to everyone involved.

One of the reasons leaders struggle with these decisions is because they unconsciously turn a fit decision into a character judgement. If I decide this person isn't right for the role, am I saying they're not good enough? Am I saying I've failed them? Am I saying they're a bad employee? Usually none of those things are true. We're simply acknowledging that the role, the person and the business aren't aligning in the way everyone hoped they would.

The cost hiding in plain sight

We're used to hearing "toxic employee" and picturing someone unpleasant, someone who creates conflict on purpose, someone everyone is relieved to see go. That's not this. But the cost this creates can end up looking remarkably similar.

Turnover is often the first casualty, and rarely the one you'd expect. It's usually not the underperforming employee who leaves. It's the people around them, the ones who've spent months quietly covering, fixing, and filling gaps for someone they genuinely like. Liking someone and resenting the situation aren't contradictory, and good people can hold both at once for a surprisingly long time before they decide it's easier to leave than to keep absorbing the extra load.

And that resentment doesn't stay contained to one relationship. It spreads into how the team talks about leadership, how much effort they're willing to put in when they sense the effort isn't being matched, whether they trust that performance is actually being noticed and managed fairly. None of that requires a difficult personality to set it off. A team culture can turn toxic without a single toxic person in the room, purely because something everyone can see isn't being addressed. That's the part that catches leaders off guard. They were watching for conflict, for someone difficult, for the obvious warning signs, and missed that the erosion was coming from somewhere much quieter.

Avoiding the conversation isn't kindness

This, for me, is the heart of it. Most leaders who let this drag on aren't being lazy or careless. They're trying to be compassionate. They want to give someone a fair go, every possible chance, the benefit of the doubt. It comes from a good instinct.

But avoiding an honest conversation isn't actually kind, even when it feels like it in the moment. Sometimes the kindest thing you can offer someone is clarity, plain and direct, delivered with care. Sometimes the kindest thing is admitting that a role simply isn't bringing out someone's strengths, and that this isn't their fault. Sometimes the kindest thing is refusing to keep pretending that more time will fix something that was never really about time in the first place. It was about fit.

Have the conversation sooner

This isn't about avoiding hard decisions. If anything, it's the opposite. The point is that finding out sooner whether someone can be coached, whether they can genuinely improve, whether they can fit the team and the business, is better for everyone involved. If they can, you've saved months of quiet frustration and given them a real shot at getting there. If they can't, you owe it to them, to the team, and to the business to make that decision early, before it drags out for years, before the team has absorbed the cost of it for too long, before it does more damage than it needs to.

Having it sooner doesn't mean having it harshly. It means naming what you're seeing while it's still specific, rather than waiting until it's become a feeling you can't quite pin down. It means talking about the gap between effort and outcome directly, rather than hoping someone reads between the lines of a gentler comment. It means being clear about what needs to change and by when, rather than leaving the conversation open-ended so it's easy for both of you to quietly let it slide. None of that requires being unkind. It just requires being honest earlier than feels comfortable, which is usually a few conversations before it starts feeling urgent.

The employee nobody wants to fire is usually not a bad employee at all. Far more often, they're a good person who's ended up in the wrong role, the wrong environment, or a position that no longer matches what they're capable of or willing to do. Sometimes that's simply life. A role can be more demanding, more stressful, or take more out of someone than they're actually willing to give, and that's not a failure, it's part of how people evolve. What someone was willing to give at one stage of life isn't always what they're willing to give at another, and that's not a character flaw either, it's just being human.

The real cost isn't the eventual difficult conversation. It's everything that builds up in the months or years before it, while the employee is left confused about where they stand, the team grows quietly frustrated picking up the slack, and the leader carries a weight that honest, early conversations could have lifted long before it became this heavy.