Claude can just about pull these cartoons off, but it does make mistakes. I made at least twice as many mistakes prompting though.
That TLDR is great! I've read the NVC book through twice and taken half of an online audio course. I've also never directly benefitted from NVC communication suggestions because they're framed awkwardly.
Your distillation rings true, but I have not made it or heard it. Thank you.
I'd just add to your TLDR something like:
Make requests but don't pressure people to do things. Try to be clear about why you're asking them to do things.
You do cover this but your TLDR is missing it. There's probably a better formulation, that's just a first random stab. That part is the nonviolent part.
It's interesting to note that LW communication usually does seem to follow those NVC principles.
TL;DR: Making claims or demands about/into other people's internal states, rather than about your state or observable external states, predictably ties people in knots—instead: only make claims about your own experience or observables. This lets the other control the copy of them that's in the shared context.[1]
Non-Violent Communication rapidly grew into a world-spanning movement due to its remarkable ability to avert and dissolve conflict. The NVC book has a whole bunch of examples of communication procedures and practical tips. Here I'll try and convey the core insights more rapidly by focusing on the underlying principles I've extracted.[2]
Background models
People have self-models. People have models of other people. Conversations form shared context, which syncs with both of those. Some ways of conversing work better than others.
Syncing back an incorrect model from conversational context can disrupt or harm one's self-model, so dissonance between your self-model and others' models of you is a type of prediction error that hits particularly hard.
Common collision in conversational context (Cartoons start here[3])
Things can get messy from here! Bob and Alice are having a tug of war over a non-load-bearing part of the map–Bob's state–which is distracting them both from resolving the grievance.
This situation is often resolvable by sharing context if there's enough ambient trust, but it sometimes escalates in very harmful ways.
Just talking about yourself is good, actually
2x2 (Purpose x Domain)
NVC makes it harder to make and easier to spot conflict-inducing claims and demands. The core procedure can be summed up as "only use things from this 2x2":
Feelings
Internal emotional states and sensations we experience,
no interpretations of other's states[8]
Needs
Universal human requirements and ~terminal values,
no strategies to fulfil them[9]
Observations
Specific factual descriptions of reality all parties can verify,
no evaluation or generalizations[10]
Requests
Specific actions we ask of others, no vagueness or demands[11]
(you're probably going to want to check at lease some of those footnotes for examples)
We've not really covered the lower half yet, but it's pretty straightforward. Making claims or asks about things that are well specified[12] and verifiable by all parties[13] is a safe conversational move since these won't be factually contested.
Observables (Cartoons #2)
Summary (slightly spaced repetition)
To wrap up:
Try it out next time you have a doomy feeling about a conversation, and maybe report back how it goes in the comments :)
Appendix: Speculation on sometimes spectacular successes
People tell wild stories of using NVC to switch people aggressively threatening violence into a calm, reasonable mode, or other similarly dramatic effects.
I have a solid guess as to why this happens. Those people are strongly predicting a fight (and hence claims/demands pushed into their self-model). But then the NVC person massively errors the aggressor's prediction by doing a low probability action (communicating non-violently), and they're now out of distribution.
Confused, they look for signs of what kind of conversation they're in, and... there's a person being reasonable and empathetic in front of them? This brings up patterns in them usually associated with a calm and regulated nervous system. That must mean... they're in an open and respectful conversation??[16] OK, next token let's try going with that and see if it generates less surprisal.
And leaves you a line of retreat
Also: only make asks about observables or universal/terminal needs. This leaves them room to decide how (and whether) to change their internal state to fulfil your underlying request, rather than pre-defining how to get there.
yes i totally cheated and made the tl;dr
threefour paragraphs with footnotes.Usually it's taught through examples and somewhat more surface level rules than this guide will emphasise. I expect this form to generalize better for LWers.
thank/blame Claude for the diagrams
Professional example: Alice: "I feel disrespected in meetings when I'm interrupted" (interpretation of Bob's state as disrespectful)
Relationship example: "I feel abandoned when plans fall through" (interpretation of Bob's state as abandoning)
P: Bob was struggling to manage ADHD symptoms and was interrupting to make sure he understood key points before they slipped away.
R: Bob was dealing with a depressive episode and was afraid of being poor company.
Sometimes your self-model is incorrect and needs updating, but 'in the middle of resolving a different conflict' is rarely a good time for this kind of vulnerable process.
P: "I feel tense and my shoulders tighten when I'm interrupted during presentations" (NVC Feeling, subtype sensation)
R: "I feel a heaviness in my chest and tears welling up when plans are cancelled" (NVC Feeling, subtype sensation)
NVC True Feelings are internal emotional or sensory states:
NVC False Feelings import claims about things not actually part of your experience, like the other person's state or external things:
The key is that Feelings describe just your internal emotional and physical experience, while pseudo-feelings include claims on how others are treating you or what they're doing to you.
NVC Needs are ~terminal or human universal needs:
but not ways of fulfilling those needs as these build in a specific way of meeting the need (making a demand into the other's self-model, or an implicit ask for an action as if that's the only way to fulfil your need):
NVC Observations are specific, factual and measurable:
Judgments, evaluations, generalizations are not Observations:
NVC says Observations could be verified by a recording, they state what happened without adding meaning, labels, or patterns to it. This is sufficient but not always necessary, as for some people more subtle things might actually be observable and not under dispute.
NVC Requests are clear, actionable, and outcome focused:
But not unclear requests, as the status of unactionable/ill defined requests is often disputed, or demands, or asks of internal state, which don't let the receiver have sovereignty over how and whether the request is fulfilled, e.g.
A demand makes no allowance to not go along with the ask without rejecting the whole demand-statement, an ask explicitly leaves the option for the person to accept the ask-containing statement while turning down the desired outcome.
NVC also suggests using Positive (do) rather than Negative (don't) requests where possible; this seems helpful but is not always practical.
If a claim or the result of an ask is underspecified in ways that might cause divergence, that's an opening for conflict on whether those conditions are fulfilled. "Is Bob lazy?" Depends what you mean by lazy. Did Bob work less than 2 hours per day last week? That leaves less to the ear of a listener. Similarly, hyperbole like "Bob never works" causes failures, as the literal interpretation is ~always false, and that means you're always running on interpretations.
If a claim or the result of an ask is not observable by all parties, there is an opening for conflict on whether those things happened. Try and cash out your unobservables in observables. NVC says "things that a recording device would see", but this can be adapted to things which all parties genuinely see and don't dispute. Asking Bob to step up and do his share doesn't give clearly defined conditions on whether he's succeeded or not. It might or might not help, but it doesn't give the kind of clarity which will settle the matter and give your future selves criteria to check against.
P: Alice says she's doing most of the project work, while Bob says it's even.
R: Alice sees their different spending styles as signs they're growing incompatible, while Bob views it as a normal adjustment period.
P: Instead of debating unmeasurable effort, they can look at story points completed and logged hours from last sprint as observable markers of contribution.
R: They look at their joint savings and proportional spending over time to get ground truth on financial changes.
I'd bet at decent odds that this general effect (knocking people out of distribution, then confidently providing an alternate context) lets some people do things like
- SSC Book Review: The Electric Kool-Aid Acid Test