Nonviolent Communication: four steps for difficult conversations
Some conversations go wrong in the very first sentence. You never deliver on time triggers defensiveness before the actual issue has even landed, and the rest of the meeting is about who is wrong instead of how to solve the problem.
The psychologist Marshall Rosenberg spent his career on the question of how to deliver difficult messages without triggering exactly that reaction. His method, Nonviolent Communication, sometimes called giraffe language, is described in the book Nonviolent Communication: A Language of Life. Today the method is used in everything from mediation and healthcare to leadership and project work.
What does the research say?
Rosenberg's core insight is that difficult messages are usually packaged as judgments of the other person: you are careless, you don't care. Judgments are heard as attacks, and attacks are met with defense or counterattack. The content of the message, the thing that actually needs solving, gets lost in the fight over who is right.
As an alternative, Rosenberg describes four steps. First an observation: what has concretely happened, without evaluation. The report came in three days after the deadline twice this month, instead of you are unreliable. Then a feeling: how it affects me. I feel stressed. Next, the need behind the feeling: I need to be able to stand behind our dates in front of the steering group. Finally a request, concrete and doable: could we check in two days before the next deadline?
The difference from softening the message matters. Nonviolent Communication is not about being vague or conflict-averse; it is about being direct on the substance while making clear that it is about the behavior and the need, not the other person's character. Rosenberg's experience from mediating everything from family disputes to armed conflicts was that people can hear almost any message, as long as it is delivered without accusation.
What does this mean for you as a project manager?
Use the structure when you need to address underperformance. Prepare the four steps in writing before the conversation: which observation, which feeling or consequence, which need, which request. The mere exercise of separating observation from judgment usually reveals how much interpretation has crept into your picture.
Listen with the same model. When a team member or client is upset, look for the need behind the words. This project is chaos can mean I need to know what applies to my part. Responding to the need instead of the tone turns many conversations around.
Be precise about the request. Many difficult conversations end unresolved: both sides have had their say, nothing has been agreed. Close with a concrete, doable request and a question about whether it works for the other person. That turns the conversation into an agreement instead of a discharge, and it gives you both something shared to follow up on next time you meet.
How to practice this
The four steps are easy to understand and hard to use when your pulse rises, which is exactly why they need to be practiced in advance. In Project-simulator you can practice delivering difficult messages to AI counterparts who react the way people do, and get feedback on how you phrased things, based on your own words. Try it free for a week and test the four steps in a conversation where nothing is at stake.
In Project-simulator you practice these conversations against an AI counterpart and get feedback grounded in research like this.
Try free for 7 days