Why It's So Tiring to Mediate Between Two People Who Are Both ''Right

You’re on the third video call about this. The same two faces are in the same two boxes on your screen. One person, let’s call her Anya, is leaning into her camera, tense. “I’ve delivered exactly what was in the brief, on time.” She’s right. You’ve seen the brief and the delivery schedule. In the other box, Ben looks at the ceiling, exasperated. “But it’s not usable. It doesn’t solve the client’s actual problem.” He’s also right. You’ve seen the panicked emails from the client. Your jaw is tight because you’re about to say something like, “Okay, let’s find a path forward,” for the tenth time, a phrase that has already proven useless. You stop yourself. You find yourself searching for things like "how to mediate when both sides have a point" and closing the tab before you find anything useful.

The exhaustion you feel isn’t just from a long meeting. It’s the specific, draining weight of trying to reconcile two valid but incompatible truths. This isn’t a simple misunderstanding or a clash of personalities. It’s a structural paradox, and you’re standing in the middle of it. The fatigue comes from trying to solve a logic problem as if it were an emotional one. You’re trying to find a collaborative solution to a situation where the underlying system has demanded two mutually exclusive outcomes. You’re not just managing people; you’re absorbing the contradictions of the entire system.

What’s Actually Going On Here

This kind of conflict is a symptom of a deeper issue: a “competing goods” problem embedded in the structure of the work. The organisation wants two different things at the same time, and has made different people responsible for each. It wants to be fast and perfect. It wants to innovate and maintain stability. It wants to increase sales volume and improve the quality of each delivery. Anya and Ben haven’t failed; they have succeeded in opposite directions.

Imagine a Head of Sales who is bonused on closing new contracts, and a Head of Implementation who is bonused on customer retention and system stability. The salesperson, doing their job correctly, promises a new client a highly customised feature with a tight deadline. The implementation lead, also doing their job correctly, looks at the request and says, “No. That will break the system for three of our biggest existing clients and take my team offline for a month.”

Both are acting rationally. Both are right. But they have been placed in a structure where one’s success is the other’s failure. The conflict that lands on your desk isn’t about their inability to communicate; it’s the inevitable result of the organisation asking for two things at once without providing a clear rule for what to do when they conflict. The argument feels personal and bitter because the negative impact is real. To Ben, Anya’s promise feels reckless. To Anya, Ben’s refusal feels like deliberate obstruction. They start to assume the worst about each other’s motives because the system has made them adversaries.

What People Usually Try (and Why It Backfires)

When you’re caught in the middle, the impulse is to reduce the tension. Unfortunately, the most common moves only make the underlying problem worse.

• The “Find the Common Ground” Appeal. You say: “Look, we all want what’s best for the client, right?” This backfires because they do agree on the abstract goal. The problem is they define “what’s best” in completely opposite ways. For one, it means speed and responsiveness. For the other, it means quality and reliability. Pointing to a shared value they already hold just makes them feel misunderstood.

• The “Let’s Just Stick to the Facts” Request. You say: “Can we put feelings aside and just look at the data?” This backfires because each person has their own set of facts. Anya has the signed contract and the project timeline. Ben has the bug reports and the server load charts. Presenting “the facts” doesn’t create clarity; it just gives them more ammunition to prove that their version of reality is the correct one.

• The “Split the Difference” Compromise. You say: “What if you deliver a simplified version of the feature two weeks late?” This often backfires by creating a solution that satisfies no one. The client doesn’t get what they were sold, and the system still takes on a feature that wasn’t properly planned. It’s a lose-lose that papers over the structural crack without fixing it, ensuring the same conflict will happen again next quarter.

• The “We’re All on the Same Team” Reminder. You say: “We need to remember we’re one team here.” This backfires because it’s a platitude that ignores the reality of their situation. They are on the same team, but the team has given them conflicting jobs. It comes across as a subtle accusation that they are the problem, when they are simply executing the contradictory instructions they were given.

What Shifts When You See It Clearly

The moment you correctly identify the situation as a structural paradox and not a personality conflict, the pressure on you changes. Your job is no longer to be a referee between two unreasonable people. Your job is to be a diagnostician for a flawed system.

This shift is a profound relief. The exhaustion lessens because you stop blaming yourself for failing to find a magic phrase that will make everyone get along. You are not a bad mediator; you are a competent professional trying to resolve an impossible equation. The shame of “I can’t handle my people” evaporates.

You stop trying to fix them and start trying to clarify the problem. Your focus moves from their tone and their history with each other to the operational reality. You are no longer trying to answer “Who is more right?” You are now asking, “Which of these two valid priorities, speed or stability, acquisition or retention, takes precedence in this specific instance?” You stop absorbing the conflict and start exposing the decision the organisation has been avoiding.

What This Looks Like in Practice

When you see the structural paradox, your language and your actions change. You move from placating to clarifying. These aren’t scripts, but illustrations of how a shift in perception changes your behaviour.

• Name the paradox out loud. Instead of trying to smooth it over, articulate the contradiction clearly. Say, “It sounds like we are being asked to deliver on a client promise by Friday, and we are also being asked to protect the stability of the platform for all our other clients. From where we stand today, it seems we can’t do both. Is that correct?” This stops the personal attacks and forces everyone to look at the real trade-off.

• Translate abstract values into concrete operations. When someone says, “We need to be more client-centric,” ask for specifics. “When you say ‘client-centric’ in relation to this decision, what’s the one thing you would see us do differently right now? Do you mean we should ship this feature, even with the bugs, or do you mean we should protect their long-term experience by delaying the launch?”

• Escalate the choice, not the complaint. Your goal is not to complain to leadership that “Anya and Ben are fighting again.” It is to present the clear, unavoidable business decision that needs to be made. Frame it as a strategic choice: “We have a conflict between two valid priorities. Option A prioritises new business growth but carries a risk of X. Option B prioritises current customer stability but carries a risk of Y. We need guidance on which risk the business is more willing to take right now.”

• Introduce time and conditions. Break the false binary of “always fast” versus “always perfect.” Ask, “For this project, which is the priority? Is it possible to be fast now and fix the stability issues in Q3? Or do we need to be stable now and accept a slower sales cycle? What would have to be true for us to do one over the other?”