Nonviolent Communication

Thinking ToolsAny stepAlso known as NVC

Developed by Marshall B. Rosenberg (Nonviolent Communication: A Language of Compassion, 1999).

Structures a hard conversation in four parts, a plain observation, a feeling, the need beneath it, and a specific request, so it can be heard without defensiveness.

One complaint about missed standups, rebuilt in four parts

At each of the designer's turns, pick the line: the plain version of the part (an observation, a feeling, a need, a request) or the everyday version that carries blame inside it. The engineer's reply shows how each one lands. Illustrative.

Designer

Engineer

Designer

Engineer

Select a stage to read it, or play the sequence.Observation. The engineer has missed most standups this month, and the designer has been redoing work because of it. Pick how she starts.Pick a move to see the reply.Never? I was there Tuesday. And I have a lot going on.An evaluation: never and doesn't matter are verdicts, and he argues with them.That's true. It's been a bad stretch.An observation: a count he can check, so there is nothing to dispute.He agrees. With nothing to argue with, he accepts the fact.Feeling. Pick how she says what it does to her.Pick a move to see the reply.Anxious? I didn't realize it was hitting you like that.A feeling: it is hers, so he can hear it without defending himself.I'm not leaving you to do anything.A judgment wearing a feeling's clothes: I feel like you is an accusation.He listens. A feeling owned by the speaker is news to the listener, not an attack.Need. Pick how she names what she needs.Pick a move to see the reply.Standup at 9 is the worst time for me.A strategy, not a need: it names one way to get there, and he rejects the way.That makes sense. Two of those changes landed on days I skipped.A need: it says what matters, and leaves room for many ways to meet it.He connects it. He sees the link between his absences and her rework for the first time.Request. Pick how she asks.Pick a move to see the reply.Yes. And I'll come Mondays and Thursdays when the big ones go in.A request: specific, and refusable, so he says yes and adds to it.Fine. I'll be there.A demand: he complies, resentfully, and the 9 a.m. clash is still there.A better deal. She asked for one thing and got two: a note for every API change and two standups a week.

How well it lands0of 4

  1. Observation (Designer). The engineer has missed most standups this month, and the designer has been redoing work because of it. Pick how she starts.
    • You're never at standup. It's like the team doesn't matter to you. Never? I was there Tuesday. And I have a lot going on. An evaluation: never and doesn't matter are verdicts, and he argues with them.
    • You've missed four of the last six standups. That's true. It's been a bad stretch. An observation: a count he can check, so there is nothing to dispute.
  2. He agrees (Engineer). With nothing to argue with, he accepts the fact.
  3. Feeling (Designer). Pick how she says what it does to her.
    • I'm frustrated, and honestly a bit anxious about the launch. Anxious? I didn't realize it was hitting you like that. A feeling: it is hers, so he can hear it without defending himself.
    • I feel like you're leaving me to do your job. I'm not leaving you to do anything. A judgment wearing a feeling's clothes: I feel like you is an accusation.
  4. He listens (Engineer). A feeling owned by the speaker is news to the listener, not an attack.
  5. Need (Designer). Pick how she names what she needs.
    • I need you to come to standup. Standup at 9 is the worst time for me. A strategy, not a need: it names one way to get there, and he rejects the way.
    • I need to know about API changes before I build screens on them. That makes sense. Two of those changes landed on days I skipped. A need: it says what matters, and leaves room for many ways to meet it.
  6. He connects it (Engineer). He sees the link between his absences and her rework for the first time.
  7. Request (Designer). Pick how she asks.
    • Would you post a note in the channel on any day an API change merges? Yes. And I'll come Mondays and Thursdays when the big ones go in. A request: specific, and refusable, so he says yes and adds to it.
    • So from now on you have to be at every standup. Fine. I'll be there. A demand: he complies, resentfully, and the 9 a.m. clash is still there.
  8. A better deal (Engineer). She asked for one thing and got two: a note for every API change and two standups a week.

An example

A product designer at a software firm had rebuilt three sets of screens in a month because the backend had changed under her. The engineer behind the changes had missed most of the morning standups where they would have come up. Her first draft of a message to him read: you're never at standup, and it feels like the rest of us don't matter to you.

She rewrote it before sending. The new version counted the standups he had missed (four of six), said she was frustrated and anxious about the launch, named what she needed (to know about API changes before building screens on them), and asked one thing: a note in the team channel on any day a change merged. He wrote back that two of the changes had landed on days he skipped, that the 9 a.m. slot clashed with his deploy window, and that he would post the notes and come to the Monday and Thursday standups, when the larger changes went in.

Why it works

Most complaints carry a verdict about the other person inside them: never, always, careless, doesn't care. The listener hears the verdict, defends against it, and the actual problem goes unaddressed. The four parts separate what a complaint usually fuses together.

An observation gives the listener a fact to accept instead of a judgment to fight. A feeling owned by the speaker is information about her, not an accusation about him. The need is the most useful part: it names what matters without fixing the one way to get it, so the listener can offer ways the speaker had not thought of. A request that can be refused invites a real yes, where a demand only gets compliance. In the example, the need for warning about changes was met better by a channel note than by the standup she would have demanded.

The thinking behind it

Marshall B. Rosenberg Marshall B. Rosenberg, a psychologist and mediator, founded the Center for Nonviolent Communication in 1984 and set out the method in Nonviolent Communication: A Language of Compassion (1999). It has four components: an observation free of evaluation, the feeling it stirs, the need behind the feeling, and a concrete request that leaves room for a no. Studies of the method are few, small, and varied in what they measure, so its evidence base is weak; it is best treated as a practitioner's discipline.

How to run it

  1. Write the complaint as it is. Get the raw version down first, unedited, so you can see the verdicts hiding in it.
  2. Turn verdicts into observations. Replace never, always, and careless with what happened, counted or quoted.
  3. Name your feeling. Use a feeling word about yourself, and check that "I feel like you" has not crept in.
  4. Find the need under it. Ask what you need that the behavior is blocking, and keep it free of any one solution.
  5. Make one specific request. Ask for an action someone could do this week, phrased so that no is an allowed answer.
  6. Listen for theirs. Hear their reply as their feelings and needs, which is where the better option usually comes from.

Where it goes wrong

The vocabulary turns into a script. "When you miss standup, I feel sad, because I need connection" sounds therapeutic at work and invites eye-rolling. Use the four parts to think, then say it in ordinary language.

Feelings get faked. "I feel ignored" and "I feel disrespected" are judgments of the other person dressed as feelings, and they land as accusations. If the sentence says what the other person did, it is not a feeling.

The request is really a demand. If a no would lead to consequences, say so plainly and treat the talk as a negotiation or a performance conversation. Calling a requirement a request teaches the other person not to trust the next one.

When to use something else

  • DEAR MAN. When the job is one specific request of a boss or client, with a fallback ready to negotiate.
  • Crucial Conversations. When the stakes run high on both sides and the facts themselves are in dispute.
  • Difficult Conversations. When each side has its own story of what happened and the conversation has to sort out those stories first.

Where it sits in SOLVE eX

  • Any step: Tools that serve every step: habits of thought and checks on the thinking itself.

Go to the source

  • Nonviolent Communication: A Language of Compassion, PuddleDancer Press, first edition, 1999

Back to the catalog