Why You and Your Client Aren't Actually Disagreeing

The contract was clear. The scope was signed. The work was delivered on spec. The client was furious anyway, and after the third email exchange I realized we weren’t actually disagreeing about the deliverable - we were disagreeing about who had been wronged.

This is the thing Kurt Gray’s book Outraged helped me see, and it changed how I run almost every difficult client conversation since.

Gray is a moral psychologist whose research argues that our moral conflicts aren’t, as we usually assume, fights between different value systems. They’re fights about who got harmed and who did the harming. Two people in a moral conflict almost always agree on the abstract principle - harm is bad. They just disagree on the roles. Each side sees themselves as the victim and the other as the aggressor.

I want to walk through how this lens has rewired my reading of client conflicts and team disagreements, because once you see it, you can’t unsee it, and you start defusing fights that used to take days to resolve. This is a different toolkit from handling a genuinely bad client - that’s for when the harm really is one-sided. This is for the far more common case where it isn’t.

What we tell ourselves about disagreement

The story we usually tell about a client fight goes something like: the client doesn’t understand the work, or the client is being unreasonable, or we have different priorities. These framings make the conflict feel intractable, because they put the disagreement at the level of values or comprehension. If they don’t get it, what’s there to negotiate?

Gray’s research suggests this framing is almost always wrong. The actual structure of the conflict is: both parties feel they’ve been harmed. The freelancer feels harmed because the client is moving goalposts, withholding payment, or demanding rework. The client feels harmed because the freelancer is over-promising, under-delivering, or treating their business with insufficient care.

Neither side has a value disagreement. Both sides agree harm is bad. Both sides agree promises should be kept. They just disagree on the harm map - who hurt whom, in what order, with what intent.

This sounds like a small reframe. It’s not. It completely changes what you do next.

The example that broke this open for me

I had a project go sideways with a client about three years ago. Mid-project, they asked for changes that I considered scope creep. I pushed back. They escalated. By week five we were both writing the kind of polite-but-armored emails that mean a relationship is about to end.

I’d been reading Gray that month, and I tried the lens: what does this look like if we both think we’re the victim?

I’d been telling myself the story that the client was being unreasonable - that they were trying to extract free work, that they didn’t respect my expertise. Standard freelance grievance script.

Then I tried to write the story from their side. What would have to be true for them to see themselves as the wronged party? It took me about twenty minutes to construct, and once I did, it was uncomfortably plausible. From their angle, they had a deadline they hadn’t told me about. They’d been promised something in our discovery call that I had stopped delivering when scope tightened. They’d asked for changes that, to them, felt small - and watched me draw a hard line that, to them, felt arbitrary.

I wasn’t doing anything wrong. They weren’t doing anything wrong. We were both in a movie where we were the protagonist and the other person was the antagonist. That’s the Gray reading exactly.

I rewrote my next email starting with: “I think we’re both frustrated, and I want to understand what you needed from this that you’re not getting.” The thread, which had been ten messages deep into deteriorating, turned around in two replies. We ended up shipping a revised scope. I lost some hours. They paid in full. We still work together.

What “harm-perception” actually does to the conversation

When you treat a conflict as a values dispute, your goal becomes to win the argument. You marshal evidence. You restate the contract. You quote your own emails back. You are, technically, correct. You are also losing.

When you treat the conflict as a harm-perception mismatch, your goal becomes to map both perceived harms before anyone tries to solve anything. They feel hurt because X. I feel hurt because Y. Neither of us is faking. Now: what can we change about the situation?

This is not about being soft. It’s not about pretending you’re in the wrong when you’re not. It’s about understanding that the other person is operating from a felt sense of having been wronged that is just as real to them as yours is to you, and that you cannot resolve a fight where both parties feel victimized by treating it as a question of fact.

The version of this I learned from misreading the art of saying no without feeling like a monster is that you can hold a firm position and acknowledge the other person’s harm. They’re not the same gesture. Most freelancers conflate them. Saying “I understand this is frustrating for you, and the contract is what it is” is a much more powerful move than “the contract is what it is.”

Where this breaks down

I don’t want to oversell this. Gray’s framework isn’t a universal solvent.

Some clients are actually being unreasonable. Some people are operating in bad faith. The harm-perception model assumes both sides are genuinely experiencing a sense of being wronged, and a small percentage of conflicts are with people who are simulating that sense to gain an edge. Those people exist. You will meet them.

The lens doesn’t tell you how to resolve those cases - it only tells you whether you’re in one. The diagnostic is: when you make a good-faith attempt to acknowledge their perceived harm, does the temperature drop? In most cases, yes. In the bad-faith cases, the temperature stays high or goes up. That’s data. Use it.

The other limitation: the model is descriptive, not prescriptive. It tells you why fights happen. It doesn’t tell you what the right outcome is. Sometimes the right outcome is to fire the client. Sometimes it’s to refund them. Sometimes it’s to just absorb the loss and move on. Gray won’t tell you which. He’ll just help you see the actual shape of the conflict you’re in.

The translation to team disagreements

The same lens applies to disagreements within a team or with a collaborator. The pattern is almost identical:

A designer thinks the developer is being inflexible. The developer thinks the designer is being unrealistic. Both feel disrespected.
A founder thinks an early employee isn’t pulling weight. The employee thinks the founder is moving goalposts. Both feel exploited.
Two co-founders disagree about a strategic call. Both think the other is risking everything they’ve built. Both feel betrayed.

In every case, the surface argument is about strategy or execution. The actual argument is about who got hurt. The path forward is to name the harm map before re-litigating the surface decision.

I’m not going to claim this fixes every disagreement. Some are real and irreducible. But the share of fights that dissolve once you stop trying to win them is much higher than I would have guessed before I had this model.

Gray’s book isn’t a business book. It wasn’t written for client conflicts. But the deepest insights about how humans work tend to apply across domains, and Outraged is one of those books. If you spend any meaningful portion of your week trying to keep relationships from falling apart - and most freelancers do - the harm-perception lens is one of the highest-impact mental upgrades I know.

Next time a client email lands and you feel your stomach drop, before you respond, try this: write out, in one paragraph, what would have to be true for them to see themselves as the wronged party. If you can write that paragraph honestly, you’re already most of the way to a resolution. If you can’t, the conflict might be real, but at least you’ll know which kind.

That’s the most useful thing I learned from the book. The rest is implementation, and the implementation is mostly just being willing to ask before you defend.