Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / The Silent Killer of High Performance Teams
Transcript
- Lucas: We spend a lot of time talking about managing difficult employees, but there is one archetype that trips up even the most seasoned leaders: the brilliant jerk. This isn't someone who is lazy or incompetent. In fact, they are often our highest producers. But their interpersonal conduct actively degrades the performance of everyone around them. Luna: Right, because if they hit all their numbers, it’s easy to rationalize the behavior as just 'how they are.' I’ve seen teams tolerate constant condescension from a top biller for years. Lucas: Exactly. And the cost isn't just morale; it's attrition. You lose your other high potentials because they don't want to work in a environment where competence is respected but humanity is ignored. Let's look at a concrete example from a software engineering team we analyzed recently. Luna: Was this a startup environment or something more established? Lucas: Mid-sized fintech firm, roughly four hundred employees. The engineer in question was writing code faster than anyone else, with fewer bugs than the average. But during sprint reviews, he would publicly dismantle his colleagues' contributions using sarcasm. He’d say things like 'Did you even try to think about this?' in front of the product manager and stakeholders. Luna: That kind of public shaming is instantly memorable. It creates a climate of fear rather than psychological safety. Lucas: Precisely. The manager initially tried to ignore it, thinking the engineer’s output justified the friction. But within six months, two senior developers left. Their exit interviews cited 'lack of respect' and 'constant humiliation' as primary drivers. The remaining team started covering for each other less, siloing their work to avoid interaction. Luna: So the brilliant jerk doesn't just hurt feelings; they actually reduce overall organizational throughput by killing collaboration. Lucas: That is the hidden metric. When people stop sharing knowledge because they are afraid of being mocked, innovation stalls. The manager finally sat down with the engineer, but here is where many leaders go wrong. They framed the feedback around the impact. Luna: Like saying 'your behavior is causing people to leave'? Lucas: Yes. And the engineer pushed back hard. He argued that he was just being direct, that he was saving time by pointing out errors immediately. He viewed the social friction as a feature, not a bug. He didn't see himself as the problem because he believed his technical value outweighed any interpersonal debt. Luna: That’s a classic defense mechanism. It shifts the blame to the sensitivity of the listeners rather than the actions of the actor. Lucas: It is. So the manager had to pivot the conversation. Instead of arguing about intent versus impact, he shifted to a specific behavioral contract. He stopped talking about 'being nice' and started talking about 'professional standards.' Luna: How did he define those standards without sounding vague or subjective? Lucas: He used recorded interactions. He pulled transcripts from code review comments and meeting notes. He showed the engineer exactly what he said, then asked him to imagine receiving that same comment from a junior developer. The goal wasn't to make him feel guilty, but to demonstrate a clear mismatch between his stated values and his actual conduct. Luna: Using data to illustrate behavior is much harder to argue with than a general complaint about attitude. Lucas: It removes the emotion from the initial critique. The manager presented three specific instances where the tone was dismissive. He then laid out the expectation: effective communication requires constructive language, regardless of the recipient's seniority. He made it clear that technical excellence does not grant immunity from basic professional norms. Luna: Did the engineer resist that framing too? Lucas: Initially. He called it 'political correctness.' But the manager held the line. He explained that in this company, collaboration is a core competency, not a soft skill. If you cannot collaborate effectively, your technical output is irrelevant to the broader team success. Luna: That’s a strong stance. It redefines what 'value' means in that organization. Lucas: It has to be. Otherwise, you are signaling that results justify any means. The manager gave the engineer a ninety-day improvement plan. It wasn't a threat of firing, but a clear roadmap. Every week, they reviewed specific interactions. If the tone improved, the plan moved forward. If not, separation was inevitable. Luna: And did it work? Did he change? Lucas: He changed. Not overnight, but within two weeks, he started pausing before speaking. He learned to phrase critiques as questions rather than statements. 'Have you considered...' instead of 'This is wrong.' It was a mechanical shift at first, but it stuck. By day ninety, the team atmosphere had noticeably lightened. Luna: It sounds like he needed to learn a new vocabulary for conflict. Most smart people assume their style is universal. Lucas: Exactly. They haven't been taught the nuance of professional diplomacy. As managers, we have to provide that training. We can't expect high performers to intuitively understand how their words land on others. We have to coach them through it. Luna: So the takeaway is that we need to treat emotional intelligence as a trainable skill, just like coding or sales. Lucas: Without a doubt. If we only correct lazy employees, we send a message that mediocrity is tolerated as long as it is polite. But we also can't let brilliance excuse brutality. The standard must be consistent across the board. Luna: It’s tough for managers who admire the talent. It feels like you are punishing success. Lucas: That is the hardest part. But staying silent is ultimately a failure of leadership. You are protecting the individual at the expense of the collective. And over time, the collective wins. The team falls apart, the projects fail, and the brilliant jerk leaves anyway, taking their reputation with them. Luna: Or worse, they leave for a competitor who has no standards, making you look like the bad guy by comparison. Lucas: Spot on. Integrity in management means holding everyone to the same bar. Technical skill gets you in the door, but character keeps you there. Luna: Before we wrap up, I want to pause for a moment about the show itself. Fexingo Business exists because listeners like you support us directly. Lucas: If this conversation helped you navigate a tricky team dynamic or refine your own approach to leadership, consider supporting the network. Your contribution keeps these episodes ad-free and ensures we can keep digging into these nuanced topics. Luna: You can find us at buy me a coffee dot com slash fexingo. It takes just a minute and it makes a real difference in keeping this content going. Lucas: Thank you for considering it. Now, let's circle back to that ninety-day plan. One thing managers often miss is the follow-through. Luna: Right, setting the goal is easy. Checking in weekly is the grind. Lucas: Exactly. The manager in our story didn't just set it and forget it. He checked in every Friday for fifteen minutes. He asked 'what worked this week?' and 'where did you slip up?' It kept the behavior top of mind. Luna: Consistency reinforces the new habit. Without those check-ins, the old patterns would have returned once the pressure lifted. Lucas: Absolutely. Behavior change requires repetition. Just like learning a new syntax in code, you practice until it becomes muscle memory. Luna: So for first-time managers, the lesson is clear: address the behavior early, use data, and stay consistent. Lucas: Yes. Don't wait for the next crisis to act. Address the small incivilities before they become structural damage to your team. Luna: Agreed. It’s better to have the uncomfortable conversation now than to manage the fallout later. Lucas: Think about the last time you felt disrespected by a colleague. Was it a major event, or a accumulation of small moments? Luna: Usually the small ones. A sigh here, a roll of the eyes there. It builds up until you just don't want to talk to them anymore. Lucas: That erosion of trust is slow but fatal. Managers need to be vigilant about those micro-interactions. They define the culture far more than mission statements do. Luna: It’s a reminder that leadership is mostly attention management. Where you focus your energy sets the tone. Lucas: Well said. Next time you spot that spark of disrespect, don't let it fizzle out. Address it. Protect the team.