The problem
The hard conversation ended. It went badly, or it went fine, or you're honestly not sure — and now you do what most people do, which is nothing. You move on. Maybe you replay the worst moment a few times in the shower, feel bad, and let it fade. And then the next conflict arrives and you run the exact same pattern, because nothing in between actually changed.
That's the gap. The people who get genuinely good at conflict aren't more naturally calm or articulate. They do one thing the rest of us skip: they reflect, with structure, after each significant dispute. Not rumination — review. The conversation becomes a rep, and reps compound.
Four questions are the whole practice.
The mechanism
Conflict competency is an iterative process — a skill built through deliberate reflection, not a fixed trait you either have or don't. The vehicle is a conflict journal: after a significant dispute, you document the physiological triggers you felt, analyze the gap between the message you intended and the impact you actually had, and identify the cognitive biases that shaped the outcome.
The structure is four questions, and each maps to a framework you can act on. Question 1 — the trigger and the SCARF domain: what set you off, and was it a threat to Status, Certainty, Autonomy, Relatedness, or Fairness? Naming the domain tells you what you're sensitive to. Question 2 — the nervous-system state: did you go ventral vagal (stayed regulated), sympathetic (fight or flight), or dorsal vagal (shut down)? This builds your interoceptive awareness of your own hijack. Question 3 — the cognitive bias: what distortion — fundamental attribution error, confirmation bias — bent your read of the other person? Question 4 — the redo: if you could run it again with one framework from your toolkit, which would you pick, and what exactly would you say differently?
Done repeatedly, this is how the abstract goal — "be better at conflict" — becomes a concrete, compounding practice. You can't improve a pattern you never examine.
The operating system
Five steps. The four questions, plus the discipline that makes them count.
Do it soon, while it's fresh
After any significant conflict, sit down within a day and run the review while the details are still accurate. Wait too long and memory smooths it into a story that flatters you. The raw, slightly uncomfortable version is the one with the lessons in it.
Q1 — Name the trigger and the SCARF domain
What specifically set you off — a word, a tone, a topic — and which social threat did it hit: Status, Certainty, Autonomy, Relatedness, or Fairness? Over several entries, a pattern emerges: you'll find one or two domains you're repeatedly sensitive to. That's gold for spotting the hijack earlier next time.
Q2 & Q3 — Name the state and the bias
Which nervous-system state did you go into — regulated, fight/flight, or shutdown? And which cognitive bias likely distorted your read of the other person? Naming both builds the two core meta-skills: reading your own physiology, and catching your own distortions in the act.
Q4 — Script the redo
If you could run it again with one framework from your toolkit — amygdala-hijack interrupt, SBI feedback, the SCARF audit, a tactical pause — which would you choose, and what exactly would you say? Writing the specific words is what installs them, so they're available the next time the situation repeats.
Keep the journal — let it compound
One reflection is useful; the practice is in the accumulation. Keep the entries together and revisit them. Over months you'll watch your triggers become visible, your hijacks shorten, and your framework choices sharpen — the slow, real transformation into someone others feel safe disagreeing with.
The printable: the conflict journal
Print it. Run the four questions after every significant conflict.