Nonviolent communication at work: guide
NVC in 4 steps (Observation, Feeling, Need, Request) for managers. Defuse team tensions before they escalate — with scripts and real examples.
---Marshall Rosenberg's Nonviolent Communication (NVC) is one of the most powerful communication tools available to managers. Where instinct pushes us to judge, blame or demand, NVC offers a radically different path: observe, express feelings, identify needs and make a clear request.
Used in conflict mediation worldwide, this method has proven itself in contexts ranging from international diplomacy to software development teams. Studies show that NVC training reduces workplace conflicts by 40 to 60%.
This guide adapts NVC specifically to the managerial context, with concrete scripts you can use in your very next meeting.
What you will learn
- The 4 NVC steps (OFNR) applied to management
- 5 concrete managerial scripts using NVC
- Common mistakes that sabotage NVC attempts
- How to use NVC in written communication (email, Slack)
What is NVC and why does it work?
Marshall Rosenberg developed Nonviolent Communication in the 1960s, drawing on his work in clinical psychology and Gandhi's philosophy. His fundamental premise: all human actions are attempts to meet universal needs.
When a team member shows up late, they're not trying to disrespect you — they may be trying to meet a need for autonomy, rest or managing family obligations. When a manager raises their voice, they're probably trying to meet a need for reliability or recognition.
NVC works because it short-circuits the defence mechanism. When someone hears a judgment ("You're irresponsible"), the limbic brain activates and the person shuts down. When that same person hears an observation followed by a need ("When the report arrives after the deadline, I need to be able to count on timelines for planning"), the space for dialogue stays open.
The 4 OFNR Steps of NVC
Step 1: Observation (vs evaluation)
Definition: Describe the facts objectively, without judgment or interpretation.
Manager example:
- Observation: "You arrived at 9:30 for the last 3 team meetings scheduled at 9:00."
- Evaluation (avoid): "You're always late."
The word "always" is a red flag. Generalisations ("never", "always", "again") turn an observation into an accusation.
Common pitfall: Disguised judgments. "You didn't put in enough effort" looks like an observation but contains a judgment ("enough"). Prefer: "The report contained 3 pages instead of the 10 requested in the brief."
Step 2: Feeling (vs thought)
Definition: Express the emotional impact of the situation on you.
Manager example:
- Feeling: "I feel concerned."
- Thought disguised as feeling (avoid): "I feel like you don't care."
The test is simple: if you can replace "I feel that" with "I think that", it's a thought, not a feeling. Real feelings: worried, frustrated, disappointed, confused, relieved, enthusiastic, tense.
Common pitfall: Confusing "I feel [adjective]" with "I feel [judgment about the other person]". "I feel let down" is a feeling. "I feel ignored" is an interpretation of someone else's behaviour.
Step 3: Need (universal)
Definition: Identify the fundamental need behind your feeling.
Manager example:
- Need: "I need to be able to rely on the team's dependability."
- Strategy disguised as need (avoid): "I need you to use Jira."
Needs are universal: respect, autonomy, competence, collaboration, clarity, safety, trust, recognition, efficiency. Strategies are the specific means to meet those needs.
Common pitfall: Jumping straight from feeling to request. This is the step managers skip most often, but it's the one that creates connection. When you name a universal need, the other person can relate to it.
Step 4: Request (vs demand)
Definition: Make a concrete, doable, positive request.
Manager example:
- Request: "Would you be willing to send a message if you're going to be more than 5 minutes late?"
- Disguised demand (avoid): "Could you make more of an effort?"
A request accepts "no" — a demand doesn't. If refusal leads to punishment or withdrawal of goodwill, it was a demand.
Common pitfall: Vague requests. "Can you do better?" is not actionable. A good request answers: Who does what, by when and how?
5 Managerial NVC Scripts
Script 1: Giving difficult feedback on work quality
Situation: Sophie's report contains several factual errors and was sent to the client.
Traditional response: "Sophie, this report is sloppy. You should have proofread it. It's unacceptable to send this to a client."
NVC version: "Sophie, I found 4 factual errors in the report sent to the client on Tuesday (Observation). I feel concerned (Feeling) because I need our deliverables to reflect our level of expertise with clients (Need). Could we set up peer reviews before every client submission? (Request)"
Why it works: Sophie hears a concrete problem to solve, not an attack on her competence. She's more likely to engage with the solution.
Script 2: Addressing recurring lateness
Situation: Karim has been late to team meetings for the past 3 weeks.
Traditional response: "Karim, that's the third time. If this continues, there will be consequences."
NVC version: "Karim, I've noticed you arrived after the start of the last three team meetings (Observation). I feel uncomfortable (Feeling) because I need the team to start together so that decisions include everyone (Need). What would help you be there on time? Or would a different time slot work better for you? (Request)"
Why it works: The open question invites Karim to share the obstacles he's facing, rather than justify himself or get defensive.
Script 3: Mediating tension between two team members
Situation: Tension between Lina and Thomas over project responsibility allocation.
Traditional response: "You're adults, sort it out between yourselves. If you can't, I'll decide."
NVC version (in a mediation meeting): "I observe that you each have a different view of who's responsible for the technical side of the project (Observation). I sense tension between you and that concerns me (Feeling) because I need the team to work in a collaborative atmosphere (Need). I suggest each of you shares what's important to you in this allocation, without interruption. Lina, would you like to start? (Request)"
Why it works: You model NVC while structuring the exchange. The "without interruption" framework creates a safe space.
Script 4: Responding to pushback on a decision
Situation: The team challenges your decision to switch project management tools.
Traditional response: "The decision is made. Everyone adapts."
NVC version: "I hear that the tool change is meeting resistance from the team (Observation). I understand the frustration — changing habits takes energy (Feeling acknowledged). On my side, I need visibility into project progress and the current tool doesn't give me that (Need). I suggest we try the new tool for 2 weeks and then review together. If the pain points are too significant, we'll reassess. Does that work for you? (Request)"
Why it works: You acknowledge the resistance without giving in, explain your need and propose a reversible trial — which respects the team's need for autonomy.
Script 5: Asking for more commitment without being aggressive
Situation: Paul has been doing the bare minimum for the past few weeks.
Traditional response: "Paul, you need to step it up. This isn't enough."
NVC version: "Paul, I've noticed your contributions have been limited to assigned tasks over the past few weeks, whereas you used to regularly suggest improvements (Observation). I feel a bit worried (Feeling) because I need your expertise and creativity for the project to move forward well (Need). Has something changed for you? And how could I help you get back the momentum you had? (Request)"
Why it works: You open the door to honest dialogue. Perhaps Paul is overloaded, demotivated by a factor you're unaware of or going through personal difficulties.
Mistakes that sabotage NVC
NVC as manipulation
"I feel frustrated when you don't do what I ask." That's not NVC — it's guilt-tripping wrapped in NVC vocabulary. Authentic NVC seeks a solution that respects both parties' needs.
The "NVC robot"
Mechanically reciting "When you... I feel... because I need... could you..." in every interaction creates awkwardness. NVC is a thinking framework, not a script to recite. Make the vocabulary your own and adapt it to your style.
NVC only during conflicts
If you only bring out NVC when there's a problem, your team will associate it with "a criticism is coming". Use it daily, including for positive feedback: "When I see the quality of your presentation (O), I feel reassured (F) because I need to know the client is in good hands (N). Thank you (R)."
Skipping the needs step
Going straight from feeling to request ("I'm frustrated, can you do X?") sounds like an emotional order. The need is what gives meaning to the feeling and legitimacy to the request.
Using NVC to avoid setting boundaries
NVC doesn't mean tolerating everything. You can be firm AND empathetic: "Repeated delays impact client billing. I need deadlines to be met. If the workload is too heavy, let's redistribute — but the deliverable must go out on schedule."
NVC in written communication
Emails and Slack messages present a unique challenge: no tone of voice, no body language. Here's how to adapt NVC to writing.
Key principles
- Lead with observation: quote the specific message or event
- Name the feeling briefly (one sentence, not a paragraph)
- State the need
- End with a clear request + timeline
- Avoid emojis as emotional substitutes — they're ambiguous
Example: transforming a passive-aggressive email into NVC
Before: "As mentioned in my previous email (which went unanswered), I need the budget. Please send it as soon as possible."
After (NVC): "Hi Marie, I'm following up on my April 12th email about the forecast budget. I haven't received a response yet and the committee presentation is on Thursday. I'm a bit stressed about the timeline because I need those figures to finalise my presentation. Would it be possible to send them by Wednesday noon? If that's too tight, let me know and we'll find a solution. Thanks!"
Key takeaways
"NVC isn't about being 'nice' — it's about being honest AND empathetic at the same time."
- Observe without judging: the facts, nothing but the facts. Ban "always" and "never".
- Feelings, not thoughts: "I'm frustrated" yes, "I feel like you don't care" no.
- Name the need: this is the step that creates connection and understanding.
- Request, don't demand: a real request accepts refusal and opens negotiation.
- Practise daily: NVC isn't reserved for conflicts, it's a mode of communication.
Move from theory to practice
NVC is mastered through practice, not reading. On TrustLeader, you can practise nonviolent communication in realistic managerial conflict simulations, with detailed interactive system feedback on your use of the 4 OFNR steps.
Related articles: