Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / The Silent Cost of Unmanaged Conflict
Transcript
- Lucas: We spend a lot of time talking about what employees ask for: raises, promotions, autonomy. But there is a much quieter, more expensive thing that teams deal with every single day, and it has nothing to do with compensation. It is the cost of unmanaged conflict. Luna: Right, because we tend to think of conflict as these explosive, dramatic moments where two people are yelling in a conference room. But the real damage happens in the quiet spaces between those moments. Lucas: Exactly. I want to talk about what organizational psychologists call relational friction. It is not the big fight. It is the thirty seconds you hesitate before answering an email from a colleague because you know they will misinterpret your tone. It is the extra ten minutes you spend rewriting a project brief because you do not trust the other department to get it right without hand-holding. When you add all those micro-interactions up, research suggests teams can lose anywhere from fifteen to twenty percent of their productive capacity just navigating interpersonal static. Luna: That number feels incredibly high, but when I look at my own network, it tracks. People are not quitting jobs solely because of the boss anymore; they are burning out from the constant background noise of trying to manage relationships they never agreed to navigate. Lucas: And here is the trap for new managers. You see a team that is technically hitting its targets, so you assume everything is fine. But if you dig into the calendar invites and the Slack logs, you realize they are operating in silos of mutual suspicion. They are doing their jobs, but they are paying a massive emotional tax to do them. The question is, how do you fix that without forcing fake positivity? Luna: Because if you try to force it, you just get resentment. People can smell insincerity from a mile away. So what is the actual mechanism for addressing this? Is it a structured intervention or something more organic? Lucas: It starts with recognizing that conflict is data. Most managers treat it like a malfunction. But if two senior engineers are constantly clashing over code architecture, that is not just drama. That is a signal that they have different mental models for how the product should be built, and neither feels safe enough to articulate why. The friction is the symptom. The diagnosis is a lack of shared context. Luna: So instead of asking them to shake hands, you ask them to show their work. You make the implicit explicit. That shifts the conversation from personality to process. Lucas: Precisely. And this brings me to the three-step protocol I use with clients who come in saying their team is toxic. Step one is naming the pattern without assigning blame. You do not say, John and Jane hate each other. You say, I am noticing that decisions involving both your teams take twice as long as expected. Let us look at the bottleneck. Step two is mapping the interests, not the positions. What does each person actually need to feel secure in their role? Step three is creating a temporary operating agreement. A simple document that says, for the next three weeks, we communicate only through this channel, and we assume positive intent until proven otherwise. Luna: I love the temporary part. Making it time-bound reduces the pressure. It turns a personality clash into a short-term experiment rather than a permanent character judgment. Lucas: It works because it gives people an exit ramp from their defensive postures. Nobody wants to be the difficult person forever. But once you set a structure, you have to maintain it. That leads us to the elephant in the room. How do we even fund the time it takes to have these hard conversations? Because let us be honest, most managers are drowning in their own workload. Luna: It is the classic paradox. You have to stop working to fix the way the team works, which means you have less time to work. It feels like a losing bet until you realize the alternative is slower, messier work forever. Lucas: Right. And speaking of resources, before we go deeper into the tactical side of running those interventions, I want to pause for a second on how this show actually exists. We do not have advertisers pushing products onto your feed. We are funded entirely by listeners who believe in independent business journalism. If we have helped you think through a career move or a leadership challenge recently, a small monthly contribution through buy me a coffee dot com slash fexingo keeps the lights on and allows us to keep digging into these nuanced topics without corporate interference. It is the only reason we can cover this stuff with depth. Luna: Yeah, it really is. Knowing that our community supports this directly lets us spend hours researching things like the economics of workplace friction instead of just skimming the surface. It makes a tangible difference in the quality of the analysis. Lucas: Appreciate it. Now, back to the protocol. Once you have named the pattern and mapped the interests, you hit step three: the operating agreement. But here is where most managers fail. They write the agreement and then forget about it. They think signing a piece of paper solves the human psychology problem. It does not. Luna: Of course not. Habits die hard. If two people are used to sending passive-aggressive emails, telling them to switch to a formal request form is just going to annoy them until they revert to old ways. How do you enforce it without becoming a micromanager? Lucas: You do not enforce it. You model it. And you create feedback loops. In the first two weeks of the agreement, you hold a five-minute check-in at the start of every team meeting. Just five minutes. You ask, did the new communication rule help? Did it slow us down? Did it make things clearer? By making it a public, low-stakes review, you remove the shame. If someone slips up, you point to the agreement, not the person. You say, Hey, remember our pact on direct messages? Let us move this to the shared doc. It depersonalizes the correction. Luna: That is such a subtle shift. You are treating the behavior as a system error, not a moral failing. It protects the relationship while still holding the standard. It feels much safer for the employee to admit they slipped up when you frame it as a system glitch. Lucas: Exactly. And over time, those five-minute check-ins disappear because the new behavior becomes the default. You are essentially retraining the team's neural pathways for collaboration. But there is a catch. This only works if the manager is willing to be vulnerable first. You cannot demand psychological safety from your team if you are hiding your own mistakes. Luna: That is the hardest part. Admitting you do not know something, or that you messed up a directive, sets the permission structure for everyone else. It signals that perfection is not the goal, clarity is. Lucas: Yes. And this ties back to that initial stat about the twenty percent loss in productivity. When a manager admits fault, they are effectively refunding that tax to the team. They are giving energy back. Conversely, when a manager hides behind authority, they are extracting more tax. The ledger always balances eventually. Luna: So the ROI of vulnerability is actually measurable in saved hours. That is a compelling argument for leaders who are skeptical of soft skills. They might respect the efficiency angle more than the empathy angle. Lucas: Absolutely. Efficiency is the language of business. Empathy is the language of humans. The best managers speak both fluently. But let us talk about the edge case. What happens when the conflict is not just friction, but active malice? When one person is genuinely trying to undermine another? Luna: Right, because the operating agreement assumes good faith. If someone is weaponizing the process, the whole framework collapses. How do you distinguish between clumsy collaboration and toxic sabotage? Lucas: You look at the pattern over time, not the isolated incident. Friction is usually situational. Sabotage is strategic. If Person A consistently misses deadlines that block Person B, or if they spread misinformation in group chats, that is not a misunderstanding. That is a choice. And in that case, the three-step protocol changes. You skip the interest mapping and go straight to documentation and consequences. Luna: So the tool changes based on the intent. Good faith gets coaching. Bad faith gets discipline. It is important managers don't confuse the two, or they end up enabling the toxic person under the guise of mediation. Lucas: Spot on. Mediation requires two willing participants. If one is unwilling, you are not mediating. You are managing risk. And that risk includes the potential departure of your high performers. Nothing drives a star employee away faster than watching a mediocre colleague get rewarded for bad behavior because the manager is too afraid of confrontation. Luna: That is the silent killer of retention. Not the salary, but the injustice. If I see that my effort is being punished by the chaos created by someone else, I leave. Even if I like my job, I will not stay in a broken system. Lucas: So the manager's job is to protect the ecosystem. You are the gardener. You prune the dead branches so the healthy plants can grow. It is not always pleasant work. It involves uncomfortable conversations and sometimes letting people go. But it is necessary maintenance. Luna: Gardening is a great metaphor because it implies regularity. You do not just wait for the weeds to choke the garden. You go out every week and pull them. Consistency is key. Lucas: Consistency builds trust. When your team knows you will address issues fairly and promptly, they stop worrying about politics. They start focusing on the work. That is the ultimate goal. Reducing the cognitive load of social navigation so people can actually do their jobs. Luna: It reminds me of the concept of transaction costs in economics. If every exchange within the company is expensive in terms of time and emotion, the whole organization becomes inefficient. Lowering those internal transaction costs is a huge competitive advantage. Lucas: That is a brilliant way to put it. Internal transaction costs. Most companies ignore this metric, but it is probably the biggest drag on innovation. You cannot innovate if everyone is exhausted from defending themselves. Luna: So for the listeners who are first-time managers, the takeaway is not to avoid conflict. It is to become comfortable with the mechanics of it. Treat it like a skill to be practiced, not a crisis to be survived. Lucas: Practice the naming. Practice the mapping. Practice the agreement. And remember that your primary asset is not your technical expertise. It is the clarity of the environment you create around you. Luna: Clarity over complexity. Always. Thanks for walking through this, Lucas. It is a lot to unpack, but definitely worth the effort. Lucas: Always, Luna. Next week, we are looking at how to delegate authority without losing control, which is the next logical step after you have fixed the team dynamics. Until then, watch for the friction.