Directory · C
Not sure this is the right entry? Run the check · New here? Start with the premise
Conflict
2 min read · 392 words
Most arguments aren't about the thing being argued about. Each side is reacting to something underneath the stated position — and until that gets named, the positions don't move.
Is this you?
Check whatever lands. Nothing is sent anywhere.
Conflict is what happens when two operating systems produce incompatible output aimed at the same situation.
One system wants X. The other wants Y. Both are producing signals — anger, fear, status-defense, boundary-protection — and broadcasting behavioral output that the other system’s hardware is processing through its own filters. The complexity multiplies fast: two sets of signals, two sets of projections, two sets of defense protocols, all running simultaneously in real time.
The machinery’s default conflict response was built for conditions where conflict was physical and the resolution was dominance. The hardware mobilizes, the threat system escalates, the status circuit fights for position. This protocol was effective when the conflict was about territory or resources and the winner was determined by force. It is substantially less effective when the conflict is about whose version of the weekend plan gets implemented.
The first operational priority in conflict is to identify what each system is actually responding to. Not the stated positions — the underlying signals.
The stated position is: I want to go here, you want to go there. The underlying signal may be: my system is reading your inflexibility as a status move, and my status circuit is mobilizing in response. Or: my system is reading this disagreement as a threat to the bond, and my attachment alarm is firing. Or: my system is reading your dismissal of my preference as a repetition of a pattern that was installed long before you arrived.
When the underlying signals are addressed, the stated positions often become negotiable. When only the positions are addressed, the signals keep driving the escalation from below.
To de-escalate from the control room: slow the transmission rate. The conflict protocol’s default is fast exchange — rapid response, emotional broadcasting, each system reacting to the other’s last output before processing is complete. Slowing the rate — pausing before responding, letting the other system’s transmission arrive fully before generating output — gives the one at the controls time to identify what their system is actually producing versus what the situation actually requires.
This is not suppression. The signals are real. The anger may be warranted. The fear may be accurate. The practice is not removing the signal from the exchange. It is preventing the signal from running the exchange on autopilot.
What's actually being defended
The stated position is I want this, you want that. Underneath it there's a signal driving the intensity, and it's usually one of a small number: a status circuit reading the other person's inflexibility as a move; an attachment alarm reading the disagreement itself as a threat to the bond; or a much older pattern being triggered — your preference being dismissed in a way that was installed long before this person arrived.
Address only the positions and the signals keep driving escalation from underneath, which is why winning an argument so often changes nothing. Address the signals and the positions frequently turn out to be negotiable, sometimes immediately — it wasn't the weekend plan, it was whether your preference registered at all.
The default protocol doesn't help either. It was built for conflict that was physical and settled by dominance, so the machinery mobilises, the threat system escalates, and the status circuit fights for position. That's effective when the dispute is about territory. It's substantially less effective when the dispute is about whose version of Saturday happens.
Which makes the single most useful intervention a mechanical one: slow the transmission rate. The default is fast exchange — each side responding to the other's last output before processing has finished. Pausing before you respond, and letting what they said actually arrive, buys you the gap in which you can tell the difference between what your system is producing and what the situation requires. That isn't suppression. The anger may be warranted. It just shouldn't be driving.
What to actually say
Almost all of these work by slowing things down. Speed is what turns a disagreement into a fight, and nearly everyone regrets what they said at speed rather than what they said slowly.
- Slowing the rate
I want to get this right more than I want to get it over with. Can we go slower?
- Naming the signal under the position
I don't think this is really about the plan. I think it's that my preference didn't seem to register.
- When you're flooded
I'm too wound up to do this well. Give me twenty minutes and I'll come back — I'm not walking out on it.
- Checking you actually heard them
Let me say back what I think you mean, and you tell me what I've got wrong.
- When you're both right
I don't think either of us is wrong here. I think we want different things and neither of us has said so plainly.
- When they won't engage at all
I'd rather have this conversation badly than not have it. When are you willing to?
Say it back before you answer
One rule, used in one argument. It is unreasonably effective and it feels deeply unnatural the first few times.
Real questions
Why do we keep having the same argument?
Because the thing it's about isn't the thing it's about, so settling the contents never settles anything. Underneath a recurring fight there's usually a stable signal — not being taken seriously, feeling managed, a fear about where the relationship stands — and it attaches to whatever is available that week: the dishwasher, the money, the in-laws. That's why the specifics vary and the choreography doesn't. The recurrence is the diagnostic: identical shape, different contents, means the contents were never the subject.
How do I stay calm during an argument?
Mostly by not trying to perform calm inside the first surge, which isn't available, and by slowing the exchange rate instead. Pause before responding. Let what they said land completely before you generate anything. If you're genuinely flooded — heart going, vision narrowed, hearing almost nothing — say so and take twenty minutes, explicitly promising to come back, because a break without that promise reads as abandonment and escalates it. Most damage in arguments is done at speed, not at volume.
Why do I shut down or go blank during conflict?
Because freeze is one of the three standard responses and it isn't chosen — when a system is sufficiently overwhelmed it stops producing output rather than fighting or leaving. From the outside it reads as stonewalling, indifference, or refusing to engage, which usually makes the other person escalate, which deepens the freeze. Naming it changes that loop more than anything else: “I've gone blank, I'm not ignoring you, I need a few minutes.” The other person is almost always responding to a story about contempt that isn't true.
Is it bad to avoid conflict?
Avoiding a particular argument is often sensible. Avoiding conflict as a policy is expensive, and the bill arrives in a specific form: disagreements that never get raised don't disappear, they go under and accumulate as resentment, which is considerably harder to deal with than the original disagreement would have been. There's also a quieter cost — a relationship where nothing is ever contested is one where one person's preferences are silently winning, and usually both people can feel it even if neither names it.
How do I disagree without it turning into a fight?
Separate the disagreement from the verdict on the person, and be explicit that you're doing it. “I see this differently and I'm not saying you're being unreasonable” costs one sentence and removes most of what the other person's defence was mobilising against. Then be specific about what you want rather than what they're doing wrong. Most disagreements escalate at the point where a position turns into a characterisation — and that transition is usually audible, if you're listening for it.
What do I do when they refuse to discuss it?
Distinguish won't from can't, because they look identical and need opposite responses. Someone flooded or frozen genuinely cannot do it in that moment, and pressing makes it worse — what they need is a time, agreed, in the near future. Someone who systematically refuses every time is making a different move: declining to let anything be negotiated. That isn't a conversation problem and more conversation won't solve it. What's available there is deciding what you'll do, which is a boundary question rather than a conflict one.