Thursday, 6:40 p.m. Your colleague sends over their part of the report at the last minute, for the third time in two weeks, and the client is expecting everything first thing tomorrow. You type in Slack: "As usual, huh." The reply comes back sharp, and the next morning's meeting is ice cold. That evening you get home exhausted and your partner greets you with "you're always working late." You snap back, and the night is gone. You set out to fix two problems and ended up with four. Nonviolent communication was made for moments exactly like these.
The judgment that sneaks into every sentence
Marshall B. Rosenberg was a clinical psychologist who spent his life mediating conflicts in families, schools and companies. In his book Nonviolent Communication he starts from a simple observation: when we have to say something difficult, we almost always mix up what happened with our judgment of the person who did it.
"You're always late." "You never listen." "All you think about is work." These aren't facts, they're verdicts. And the person on the receiving end doesn't hear the problem, they hear the criticism. From there they have two options: defend themselves or hit back. Either way, the thing you actually wanted to talk about disappears.
Rosenberg recalls reading a remark by the Indian philosopher J. Krishnamurti: observing without evaluating is the highest form of human intelligence. His first thought was "What nonsense!" A moment later he realized that was an evaluation too.
The book has an example that's hard not to smile at. Brought in to resolve a conflict at an elementary school, Rosenberg asked the teachers what the principal was doing that bothered them so much. "He has a big mouth!" said the first. "He talks too much," added the second. Neither of them was describing anything he actually did. Things only got useful once they wrote down specific behavior: in staff meetings, the principal told stories about his childhood and the war, and the meetings sometimes ran twenty minutes over.
Nonviolent communication in four steps
Rosenberg's method has four parts. First you say what you observe, without judging. Then how you feel. Then what you need. Finally, what you're asking for, in concrete terms.
The example in the book comes from home. Instead of telling her teenage son he's a slob, a mother says: "Felix, when I see two balls of dirty socks under the coffee table and another three next to the TV, I feel irritated, because I need more order in the rooms we share. Would you be willing to put your socks in your room or in the washing machine?"
Now take it back to Thursday. Instead of "As usual, huh," you could tell your colleague: "On Tuesday and today, your part came in after 6. I felt under pressure, because I need a few hours to review everything before it goes to the client. Could you send it to me by 3?" Same situation. But this time they have something to respond to, not something to defend themselves against.
Behind every judgment is a need
The most eye-opening idea in the book is this one: the judgments we make about other people are distorted ways of expressing our own unmet needs. When someone says "you never understand me," what they're really saying is that they need to be understood. And when someone says "you've been working late every night this week, you love your work more than you love me," what they're saying is that they need closeness.
The trouble is that when a need comes out as an accusation, the need doesn't land. Only the accusation does. And anyone who feels accused spends all their energy defending themselves instead of meeting you halfway.
It works the other way, too. The next time someone tells you "you're always on your phone," try asking yourself what need is behind it, instead of reaching for a comeback.
Requests, not demands
The last step looks like the easiest, and it's where most people slip up. The first mistake is asking for what you don't want instead of what you do. Rosenberg tells the story of a woman who asked her husband not to spend so much time at work. Three weeks later he announced he'd signed up for a golf tournament. She'd told him what she didn't want, but not what she wanted: at least one evening a week at home with her and the kids.
The second mistake is turning a request into a demand. How do you tell the difference? Watch what you do when the other person says no. If you respond with criticism or a guilt trip, it was a demand dressed up as a request. And when people hear a demand, they see only two options: give in or push back. Neither one does the relationship any good.
It pairs well with Alfred Adler's idea of the separation of tasks: asking clearly is up to you, but how the other person responds is up to them.
The conversation you keep putting off, written today
Pick one conversation you've been avoiding: with a colleague, your boss, your partner, a client. Before you have it, write it out in four lines.
- What I observe: one specific fact, with days and numbers, and no "always" or "never."
- How I feel: one word. Worried, under pressure, disappointed, tired.
- What I need: time, clarity, respect, closeness.
- What I'm asking for: one concrete thing the other person can do, phrased in the positive.
Read them out loud. If there's still a judgment in any line, rewrite it. Then have the conversation. It won't be perfect, but it'll be a lot better than "As usual, huh."
Is there a conversation you'd like to handle differently?
Tell me about the situation and let's start working on the way you communicate.