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

A client comes in flattened by a conflict they keep being asked to settle. Two of their people, two direct reports, two department heads, two committee members, are at war, and your client sits in the middle of every meeting. One says the work was delivered on time, exactly to brief. True. The other says the work is unusable because it does not solve the actual problem. Also true. Your client has run the same meeting three times, said “let’s find a path forward” until the phrase went dead in their mouth, and arrived in your office convinced they are a bad manager. They are not. They are standing inside a structural paradox and trying to feel their way out of it, and the clinical move is to get them to stop mediating and start diagnosing.

Why the exhaustion is the diagnostic

The drain is not coming from the length of the meetings. It is coming from a specific impossibility: your client is being asked to reconcile two truths that the situation has made mutually exclusive. This is not a misunderstanding between two difficult people. It is a contradiction built into the structure of the work, and your client has been cast as the person who absorbs it.

The fatigue has a precise source. Your client is treating a logic problem as if it were an emotional one. The system above them has demanded two outcomes that cannot both happen, then handed the collision down to a meeting room and expected rapport to dissolve it. Rapport cannot dissolve it. So your client leaves each session of theirs more depleted than the last, because effort spent in the wrong register produces nothing, and produces it tiringly.

When a client reports this flavor of exhaustion, the mild kind that comes from reasonable people behaving reasonably, treat it as data. It is usually pointing at a competing-goods problem the organization has refused to name.

What the conflict is actually made of

The two people your client is refereeing have not failed. They have succeeded in opposite directions. The organization wants to be fast and to be perfect. It wants to innovate and to stay stable. It wants more volume and higher quality per unit. It has made different people responsible for each half of the contradiction, bonused them accordingly, and then acted surprised when they collided.

Give your client a clean version of the mechanism so they can see their own case inside it. A head of sales is paid to close new contracts. A head of implementation is paid for retention and system stability. The salesperson, doing the job correctly, promises a new client a custom feature on a tight deadline. The implementation lead, doing the job correctly, says no, that will break the platform for three existing clients and take the team offline for a month. Both are right. One’s success is built to be the other’s failure.

This is the part your client most needs to hear. The conflict that lands on their desk is not a communication problem. It is the predictable result of an organization asking for two things at once and providing no rule for what to do when those things conflict. The bitterness is real because the harm is real. To one person, the promise looks reckless. To the other, the refusal looks like sabotage. They have started assuming the worst about each other’s motives, because the structure made them adversaries before either of them said a word.

The moves your client has already tried

Your client has been reaching for the standard de-escalation moves, and each one has deepened the hole. Walk through them, because your client believes these were good instincts and needs to understand why they failed.

Finding the common ground. Your client says some version of “we all want what’s best for the client here.” It fails because the two people already agree on the abstract goal. They define “best” in opposite ways, one as speed, the other as reliability. Pointing at a shared value they both already hold tells them their manager has not understood the actual problem.

Sticking to the facts. Your client says “let’s put feelings aside and look at the data.” It fails because each person owns a different, accurate set of facts. One has the signed contract and the timeline. The other has the bug reports and the server-load charts. The facts do not converge. They become ammunition.

Splitting the difference. Your client proposes a stripped-down version, two weeks late. It fails by satisfying no one. The customer does not get what was sold, and the platform still absorbs an unplanned feature. The structural crack gets papered over, which guarantees the same fight returns next quarter.

The same-team reminder. Your client says “we need to remember we’re one team.” It fails because it is a platitude that denies the reality in the room. They are one team. The team has handed them conflicting jobs. So the reminder lands as a quiet accusation that they are the problem, when all they did was execute contradictory instructions.

The thread running through all four: your client is trying to make a structural contradiction disappear with interpersonal warmth. The contradiction does not care about warmth.

The shift to coach

The move is not a better phrase. It is a change of position, and it lifts the weight off your client the moment they make it. Your client has been operating as a referee between two unreasonable people. You are reframing the job. Your client is a diagnostician for a flawed system.

This reframe is a relief, and you can say so plainly. Your client stops hunting for the magic sentence that makes everyone get along, because no such sentence exists, and the absence of it was never their failure. The shame of “I cannot handle my people” has nowhere left to stand once the problem is correctly located above them.

The focus moves with the position. Your client stops working on the two people, their tone, their history, the way they look at each other, and starts working on the operational reality. The question is no longer “who is more right.” It becomes “which of these two valid priorities takes precedence in this specific instance, and who has the authority to say so.” Your client stops absorbing the conflict and starts surfacing the decision the organization has been avoiding.

Language that fits the new position

Give your client these as illustrations of the new stance, to hear the shape of it, rather than lines to recite. Each one does the same job: it exposes the structural choice instead of smoothing the personal friction.

Name the paradox out loud. Rather than smoothing it over, your client states the contradiction cleanly. “We are being asked to deliver on a client promise by Friday, and we are also being asked to protect the platform for all our other clients. As things stand today, we cannot do both. Is that a fair description?” This ends the personal attacks by putting the real trade-off on the table where everyone can see it.

Translate abstract values into concrete operations. When someone says “we need to be more client-centric,” your client asks for the specific action. “When you say client-centric about this decision, what is the one thing you would have us do differently right now? Ship the feature with the bugs, or protect their long-term experience by delaying?” Abstract values hide the choice. Operations expose it.

Escalate the decision rather than the complaint. Your client’s job is not to tell leadership that the two people are fighting again. It is to hand leadership the unavoidable choice. “We have two valid priorities in conflict. Option A protects new-business growth and risks X. Option B protects existing-customer stability and risks Y. We need a ruling on which risk the business is willing to carry right now.” A complaint keeps the conflict at your client’s level. A decision moves it up to where the authority actually sits.

Introduce time and conditions. Your client breaks the false binary of always-fast against always-perfect. “For this project, which comes first? Can we be fast now and fix stability in Q3, or do we need stability now and a slower sales cycle? What would have to be true to choose one over the other?” The binary is what traps everyone. Time and conditions give the trade-off somewhere to move.

What to listen for in the next session

Notice where your client is standing when they report back. If they describe themselves as having presented a decision and stepped back, they held the diagnostician position. If they are flattened again and describing a fourth meeting that went in circles, they climbed back into the referee chair somewhere during the week, and the two truths are still grinding against each other on their desk.

Listen for the language shift. A client who has made the turn stops saying “I cannot get them to agree” and starts saying “this is a call leadership has been ducking.” That sentence is the pattern becoming visible to the person living inside it. It counts as movement even when the underlying conflict has not resolved, because resolution was never your client’s to deliver.

Watch for the report that “nothing got fixed.” That judgment is the referee reasserting its claim. For your client, a week in which they refused to absorb the contradiction and instead named the decision out loud is a week that did its job, whatever leadership chose to do with it.

When the structural frame is the wrong one

Sometimes the conflict is interpersonal after all. Two people with a genuine history of contempt will use any structural ambiguity as cover for a fight they wanted anyway. The tell is whether the heat drops once the trade-off is named and a decision is made. A structural conflict cools when the system finally rules. A personal one keeps burning after the operational question has been settled, because the operational question was never what it was about. Take the second case as its own piece of work.

And some of these conflicts sit on top of something in your client that the work has to reach first. A client who cannot stop refereeing even after they understand the frame, who keeps climbing back into the middle, is usually getting something from the position. Indispensability. The avoidance of a decision they do not want to be blamed for. The old family role of the one who holds everyone together. That belongs in individual work before the meeting room can change. Most of the time it does not come to that. Most of the time your client is a capable person who was handed an impossible equation and told to solve it with their personality, and the most useful thing you can do is hand the equation back to the system that wrote it.