We Fired Our Best Technician. The Team Got Better the Same Week.

We fired our best technician. The team got better the same week. I want you to read that line again. The next week. Not after a rough transition period where everybody had to adjust. If that sounds impossible to you, I understand, because I would not have believed it either until it happened in my own building.

Here is the math most owners get wrong when they think about a technician like this. You look at the tickets he closes, the clients who specifically ask for him, the way he can walk into a mess nobody else can untangle and have it fixed in twenty minutes. You add that up and you get a number that looks like value.

The tech who is quietly thinking about leaving because they cannot take one more meeting where this guy snaps at them in front of the client. The hours other people spend managing around his moods instead of managing their own workload. The way your best people start keeping their opinions to themselves because they have learned that disagreeing with him is not worth the fight. You will try to make it work again and again. Chat after chat about his or her behavior. That time will completely feel wasted after you eventually find that  resignation letter you did not see coming.

Think of this person in your organization.  If you run an MSP long enough you have probably had one. Let's call him James.

James was, by any technical measure, the best technician we had ever had. He could see three steps ahead of a problem while everyone else was still reading the ticket. Clients loved him when he was in front of them. He carried a level of trust in his own ability that, frankly, he had earned.

The problem was that James yelled. Not constantly, and not always at people directly, but often enough that everyone on the team knew what his bad moods sounded like and planned their day around avoiding them. He snapped at newer techs who asked what he considered obvious questions. He had a habit of taking over other people's tickets mid-resolution because he did not trust them to finish it right, then making sure everyone knew he had to step in.

We managed him the way most owners manage a technician like this, which is to say informally and mostly by hoping it would sort itself out. A quiet word here. A vague comment about tone in a one on one. Never anything written down, never anything that named specific behavior with specific consequences attached. We told ourselves we were giving him room because he was talented, and talent like his is hard to find. What we were doing was training everyone else on the team, including ourselves, to work around him instead of holding him to the standard we held everyone else to.

Here is the part that I think about most. We were afraid of what would happen if he left. Not afraid the way you are afraid of losing a good employee.

We had let ourselves believe, quietly and without ever saying it out loud, that the team could not function without him. That belief is exactly why we let the behavior go on as long as we did. It is a lot easier to tolerate a problem you think you cannot survive without than to actually deal with it.

James believed it too, and I think that made things worse. When someone knows they are considered irreplaceable, they stop feeling like they need to manage themselves. Why would you change your behavior for a team that has already told you, through its own inaction, that it cannot function without you?

It came to a head after a specific incident. He snapped at a newer tech in front of a client on a call, correcting them in a tone that had nothing to do with the technical content and everything to do with making sure everyone in the room knew who was really in charge.

It was not the first time something like this had happened, but it was the first time it happened in a room where the cost of ignoring it again was sitting right in front of us.

We made the decision to let him go. I will not pretend it was an easy call, or that we made it with total confidence. We did not know what would happen to our service delivery without him. We had spent so long believing he was the pin holding everything together that we had never actually tested whether that was true.

It was not true. He wasn't the pin holding everything together. He just believed he was, and he'd convinced us of it too.

Here is what actually happened in the days after. The team did not fall apart.

In fact, the opposite happened almost immediately. People who had been quietly avoiding certain kinds of tickets, or certain conversations, because they did not want James's opinion on it, started stepping up. A T2 who had been coasting in his shadow for over a year started taking on harder tickets without being asked. Meetings that used to be tense because everyone was managing his mood became meetings where people actually said what they thought. Escalations that used to route around James, because going to him directly was its own kind of risk, started routing to whoever was actually best suited to handle them.

Good people don't always quit loudly over a toxic coworker. Some just quietly stop growing. That is what had been happening to our team for longer than I want to admit, and none of us saw it clearly until the pressure was gone.

A couple of clients specifically asked about him and were disappointed to hear he was no longer with us. That is a real cost and I am not going to pretend otherwise. But every one of those clients stayed, and within a quarter the feedback we were getting on communication and follow through had actually improved, because the person handling their account was no longer someone who treated documentation and clear updates as beneath him.

The lesson is that no single person, no matter how good, should be load bearing for your entire operation. If your business genuinely cannot survive one person leaving, you do not have a team. You have a dependency, and dependencies eventually get called in, whether that person quits, gets hired away, or gets fired because you finally run out of room to keep tolerating the cost.

If you have a James on your team right now, and I suspect some of you reading this do, the first thing to do is not update your escalation matrix or start looking to replace him. The first thing to do is get honest with yourself about why you have let it go on this long. Usually it is because somewhere in the back of your mind you have decided the technical value outweighs the cultural cost, and you have never actually run the math on what the cultural cost is doing to the rest of your team's growth and retention.

I have run this business long enough to know that the technicians who make you feel like you cannot live without them are exactly the ones you need to be watching most closely. Not because talent is bad. Because unmanaged talent teaches everyone around it that the rules do not apply evenly, and that lesson costs you more than any one technician is worth.

We fired our best technician. The team got better the same week. If you are holding onto someone right now for the same reasons we held onto James, ask yourself honestly what you are actually protecting, and what it is quietly costing you to keep protecting it.

Frequently Asked Questions

How do you know if a toxic high performer is actually costing you more than they're worth?

Look at attrition and growth among the people around them, not just their own ticket numbers. If your other strong performers are staying quiet in meetings, avoiding certain tickets, or have stopped taking on new challenges, that is the real cost, and it usually is not showing up anywhere in your PSA.

Why do owners wait so long to address a toxic top performer?

Because it is easier to tolerate a problem you believe you cannot survive without than to test whether that belief is even true. Most owners have never actually run the experiment, so the fear stays bigger than the reality.

What should an owner do before deciding to let someone like this go?

Document specific behavior with specific examples, set a clear written standard for how people are expected to treat each other, and give one direct conversation with real consequences attached. If nothing changes after that, you already have the information you need.

Does losing a top technician always hurt client relationships?

Some short term friction is normal, especially with clients who had a personal relationship with that person. But if the rest of your team is executing well, most clients stay, and communication and follow through often improve once the account is handled by someone who treats the basics as part of the job.

How do you prevent this from happening again with your next high performer?

Build the standard into your field guide so it applies to everyone from day one, regardless of how talented they are. When the expectation is documented and consistent, you catch the behavior early instead of discovering it after two years of everyone quietly working around it.