Defensiveness & Stonewalling antidotes
Take partial responsibility before responding; propose a timed break when one side withdraws.
John Gottman’s research identified four conversational patterns that predict relationship breakdown — criticism, contempt, defensiveness, and stonewalling — which he called the Four Horsemen. In work conversations, the two that derail professional exchanges most reliably are defensiveness and stonewalling. Each has a specific antidote that consistently interrupts the escalation cycle.
When to use Defensiveness & Stonewalling antidotes
Use the defensiveness antidote when you feel the urge to counter-attack or explain why the critique is wrong. Use the stonewalling antidote when one person has gone quiet and is clearly processing or withdrawing rather than engaging.
- When you receive feedback that feels unfair or exaggerated
- When someone on your team stops engaging in a hard conversation
- When a conversation is escalating into an exchange of grievances
- When your first response to criticism is "yes, but"
- When the other person is visibly overwhelmed or shutting down
How to use it
- Defensiveness antidote: find one true piece of the critique before you respond. Not the whole thing — one true piece. "You’re right that I didn’t flag the risk early enough" is a partial concession that acknowledges reality without accepting the whole accusation.
- State that piece clearly before you explain your side. Sequence matters: concede first, then respond. "I hear you, but here’s why you’re wrong" negates the concession.
- Stonewalling antidote: name the shutdown without escalating. "I notice we’ve both gone quiet — I think we need a short break. Can we come back to this in thirty minutes?"
- Propose a specific return time. "Let’s take a break" without a return is avoidance; "let’s come back at 4pm" is a pause.
- Use the break for genuine self-regulation, not to build your argument. Gottman’s research shows the purpose is to bring heart rate back to baseline.
Example
You never flag risks until they become problems. This is the third time.
- You’re right that I didn’t flag the dependency issue early enough on this one — I saw it later than I should have.
- The third time is fair to name. I want to understand whether there’s a pattern in how I’m reading risk, or whether these three were each different situations. Can we walk through them?
Common pitfalls
- The "yes, but" concession. "You’re right, but here’s why you’re wrong" is not a concession — it is defensiveness with an opening clause. The concession has to stand on its own.
- Proposing a break without a return time. Stonewalling without a scheduled return is avoidance. Name the time.
- Using the break to prepare arguments. The purpose of the pause is de-escalation, not strategizing. Come back calmer, not better-armed.
Where it comes from
Gottman & Levenson · Gottman & Silver (1999) · Gottman, Coan, Carrère & Swanson (1998)
In your next meeting
Kennan watches for the conversational pattern this framework addresses and surfaces a first-person line you can read off your HUD, in the same shape as the example above. Frameworks are receipts; the user-facing output is a sentence, not a citation.
Get this framework on your HUD, live.
Kennan is a real-time AI meeting assistant for Mac. When it ships, the assistant will surface a line in this exact shape, in the moment, in any meeting. Join the waitlist to get notified at launch.