奇创岛

From «Nonviolent Communication: A Language of Life»

Design a Workplace Feedback NVC Plan

You'll choose a real workplace feedback challenge and use the four NVC components to design a judgment-free feedback plan that the other person can actually hear — covering what to say, how to say it, and a risk check.

Final work

A 'Workplace Feedback NVC Plan'

Estimated time

1–2 hr

Submitted

…

Your final work

Purpose:Design an actionable NVC approach for a high-stakes workplace feedback scenario, so the other person can truly take it in without triggering their defenses.

Parts:

  • A real workplace feedback challenge (scenario + recipient + current obstacles)
  • Jackal language diagnosis (what you used to say + why it backfired or why you held back)
  • NVC four-component breakdown (one sentence each for Observation / Feeling / Need / Request)
  • A complete NVC feedback script (words you can say out loud in your next conversation)
  • Pitfall warnings (the three risks most likely to slip your expression back into judgment)
  • Anticipated reactions from the other person + your response contingency plan
  • Validation metrics (how you will know this feedback created genuine connection)

Use cases:

  • · Delivering performance feedback or criticism to a direct report
  • · Expressing disagreement with a supervisor without triggering defensiveness
  • · Taking the initiative to establish connection in a cross-department conflict
  • · Preparing for a termination conversation or a major personnel decision
  • · Any workplace situation where 'saying it triggers pushback, not saying it feels suffocating'

Pick a topic

Pick the topic closest to you, or write a custom one when you submit.

Work / Project

Communication / Relationships

Tools you'll use from the book

Four-Question Observation Checker

Use a four-question method to test whether a sentence is an observation or a judgment: 'Is this something I actually saw or heard, or is this my interpretation of what happened?'

How to use it here:

After drafting the opening sentence of your feedback script, run the four-question scan: does it contain judgment words such as 'always,' 'never,' 'terrible,' or 'irresponsible'? If yes, replace them with fact-based descriptions that include specific times, locations, or frequencies.

Boundaries:

Observation doesn't mean emotional detachment. You can still include timestamps, data points, and specific behaviors when describing facts — don't make your statement so vague that the other person has no idea what you're referring to.

Feeling Vocabulary (Feelings vs. Thoughts)

Genuine feeling words (worried, disappointed, discouraged, anxious) vs. pseudo-feeling words ('I feel ignored,' 'I feel like you don\'t care' — these are actually judgments of the other person).

How to use it here:

In your NVC feeling sentence, replace any 'I feel like you...' expressions with words that point to your own internal emotional state, so the other person hears what's happening inside you — not an accusation about their behavior.

Boundaries:

A feeling sentence is not a performance of vulnerability. In workplace contexts, brief and precise feeling words ('I feel pressured,' 'I\'m a bit worried') are more effective than lengthy emotional descriptions.

Needs Inventory (Needs vs. Strategies)

Needs are universal human requirements (efficiency, transparency, respect, connection, security); strategies are specific ways of meeting those needs. Confusing the two makes the other person hear 'you must do exactly what I say.'

How to use it here:

Write down what you truly want at the Need level — not the specific action you want the other person to take (the Strategy level). State the Need first, then make the Request; the other person is significantly more likely to respond positively.

Boundaries:

The Need level is not a tool for lecturing. Saying 'I need to feel respected' is not putting a label on the other person — it's an honest expression of what you're experiencing.

Actionable Request Criteria (Requests vs. Demands)

A Request must meet three criteria: specific (the other person knows what to do), actionable (the other person is capable of doing it), and refusable (you can accept a 'no' from the other person).

How to use it here:

Check the final request sentence in your feedback script: does it specify a concrete action? Does it preserve the other person's freedom of choice? Avoid command language such as 'you should' or 'you must.'

Boundaries:

Leaving room for refusal doesn't mean you have no bottom line. If a 'no' from the other person is genuinely unacceptable (e.g., safety requirements, compliance obligations), this is not an NVC request but a notification — and it needs to be handled with a different framework.

Jackal–Giraffe Language Comparison Table

A hands-on tool that rewrites high-frequency workplace judgment sentences ('You\'re late again,' 'This proposal is terrible') into NVC expressions, line by line.

How to use it here:

After completing your first draft, go through it sentence by sentence: which are jackal sentences (judgment / blame / moralizing) and which are giraffe sentences (Observation + Feeling + Need + Request)? Practice rewriting every jackal sentence until you have a version you can actually say out loud.

Boundaries:

Rewriting is not softening or avoiding. The rewritten expression still needs to clearly communicate your core concern — 'NVC-ifying' a sentence must not leave the other person unaware of how serious the issue is.

Work rules

Your work MUST include

  • Must include one real workplace feedback challenge (no fictional scenarios)
  • Must include a diagnosis of the original jackal language (what you used to say + why it would backfire)
  • Must fully break down the four NVC components (one sentence each for Observation / Feeling / Need / Request)
  • Must provide a complete, ready-to-say NVC feedback script
  • Must include at least three pitfall warnings (the risks most likely to slide the expression back into judgment)
  • Must include validation metrics (how to tell whether this feedback achieved genuine connection)
  • Must be clearly distinct from the 'script-rewrite route' in the same book: this work focuses on proactive design for a future scenario, not retrospective rewriting of a past conversation

Your work CANNOT just be

  • Do not simply list background knowledge of the four NVC components without anchoring them in a real scenario
  • Do not offer only tone-of-voice suggestions for 'speaking kindly' without breaking down the components
  • Do not write the Request as a non-refusable command ('You must submit by Friday' is not an NVC request)
  • Do not write the Feeling as an accusation toward the other person ('I feel like you don\'t care' is not a feeling statement)
  • Do not replace genuine NVC expression with workplace pleasantry filler ('Please understand my position' is empty language)
  • Do not equate 'a softer tone' with NVC — gentle wording that still contains judgment does not meet the standard

AI can help you here

Round 1: Help me choose a topic

When to use: You're not sure which workplace feedback scenario to choose, or you have your own scenario but aren't sure whether NVC is the right approach for it.

I'm working on the '{{Route name}}' project using *{{Book title}}*.

Based on my situation, please help me identify the one feedback scenario most suited for an NVC plan and explain why.

My situation:
[Describe your role, team size, and the communication difficulties or feedback challenges you've recently encountered]

Candidate topics (or my own scenario):
[Paste the topic list from the page, or describe your real scenario]

Please provide:
1. The most suitable topic (or confirmation of my custom scenario)
2. Why this scenario is well-suited for an NVC plan
3. What kind of work this topic can produce
4. Three questions I need to think through before starting

Yellow placeholders need you to fill in before using the AI.

AI can help you organize ideas, but cannot make final judgments for you. Don't let AI fabricate experiences, cases, or misleading content.

Round 2: Help me extract tools from the book

When to use: You've settled on your topic but aren't sure how to apply the four NVC components to this specific scenario, or what you've written still sounds like 'jackal language'.

My project is the '{{Route name}}' route from *{{Book title}}*.

My topic is:
{{Topic}}

Please help me break down this scenario using the four NVC components (Observation / Feeling / Need / Request) and point out the mistakes I'm most likely to make.

Requirements:
1. Provide example sentences for each of the four components tailored to my specific scenario (not generic templates)
2. Identify the judgment words most likely to sneak into my Observation
3. Identify expressions in the Feeling component most likely to become 'pseudo-feelings (judgments of the other person)'
4. Explain the difference between the Need layer and the Strategy layer in the context of my scenario
5. Clarify whether the Request leaves the other person room to say no

Please provide:
- Example sentences for each of the four components (specific to my topic)
- The three most common mistakes + how to avoid them
- A complete sample feedback script (for my reference and rewriting)

Yellow placeholders need you to fill in before using the AI.

AI can help you organize ideas, but cannot make final judgments for you. Don't let AI fabricate experiences, cases, or misleading content.

Round 3: Help me review my work

When to use: You've finished your first draft of the feedback plan and are ready to submit — and you want to confirm it genuinely meets NVC standards rather than being jackal language in a softer tone.

I'm submitting my Shufang Island project work.

Book: *{{Book title}}*
Project route: {{Route name}}
My topic: {{Topic}}

My draft:
{{Draft work}}

Please check each of the following criteria:
1. Does the Observation sentence still contain judgment words (always / never / terrible / irresponsible, etc.)?
2. Is the Feeling sentence a genuine emotion word, or a pseudo-feeling framed as 'I feel like you...'?
3. Does the Need layer distinguish between a Need and a Strategy ('I need efficiency' vs. 'I need you to submit by tomorrow')?
4. Is the Request specific, actionable, and does it leave the other person the right to say no?
5. Is the complete feedback script something that can be said out loud as natural speech, rather than a list of four components?
6. Are the pitfall warnings specific (not vague advice like 'watch your tone')?
7. Does the overall work represent proactive design for a future scenario (rather than a retrospective rewrite of a past event)?
8. Is it ready to submit?

Please provide:
- Overall assessment (one sentence)
- Item-by-item check result (pass / needs revision + reason)
- Required revisions (list original sentence → suggested rewrite)
- Optional enhancements
- Suggested complete feedback script after revisions

Yellow placeholders need you to fill in before using the AI.

AI can help you organize ideas, but cannot make final judgments for you. Don't let AI fabricate experiences, cases, or misleading content.

Submit my work