Identifying Needs & Making Clear Requests

The third step: the need, the heart of NVC

For Rosenberg, every feeling is the messenger of a need — met or unmet. The feeling is the warning light; the need is the engine. Learning to move from feeling to need is the heart of the method.

Needs in NVC are universal: every human being shares the same broad families, regardless of culture. This universality is precious — it is on the ground of needs that two adversaries can finally meet, where on the ground of strategies they clash.

Behind every anger lies a precious need that wasn't heard. Anger isn't the problem: it's the finger pointing at the need.

Distinguishing need from strategy

The most common error: confusing the need (universal, abstract) with the strategy (concrete, tied to a specific person or means).

"I need you to be home before 7" is not a need, it's a strategy. The need behind it may be: connection, safety, sharing. A strategy is rigid and a source of conflict, whereas a need opens several possible strategies.

When a conflict seems unsolvable, it is almost always because two strategies are clashing. Going back to the needs often reveals they are compatible.

The fourth step: the request

Once observation, feeling and need are stated, the request remains. A good NVC request meets three criteria:

1. Concrete and positive: say what you want, not what you don't want. "Stop interrupting me" becomes "Would you be willing to let me finish my sentence?"
2. Doable now: a precise action, not an abstract wish. "Be more respectful" is unverifiable; "Can you lower your voice?" is doable.
3. Negotiable: it's a request, not a demand. If a "no" triggers punishment or blame, it was a disguised demand.

graph TD
    A[I make a request] --> B{The other says no}
    B -->|I welcome the no<br/>and listen for their need| C[It was a real request]
    B -->|I punish, insist,<br/>guilt-trip| D[It was a disguised demand]

The difference between a request and a demand reveals itself at the "no." A request welcomes refusal; a demand punishes it.

Connection request vs action request

Rosenberg distinguishes two types of request. The action request concerns a concrete behavior ("could you send me the file tonight?"). The connection request checks that connection and understanding are present before acting ("how do you react to what I just said?", "can you tell me back what you understood?"). Skipping the connection request often makes the action request fail.

The complete OFNR sentence

Let's assemble the four steps on a concrete work case — a colleague who changes your work without warning.

Don't say this: "You go ahead and change everything behind my back, it's unacceptable."

Say this (OFNR):

"When I saw that the presentation had been changed without you mentioning it (observation), I felt upset and worried (feeling), because I need to be kept informed about what affects my work (need). Could you let me know before the next change, with a quick message? (request)"

The structure need not be recited mechanically. With practice, it becomes a way of thinking: observe the facts, feel, identify the need, ask clearly.

OFNR summary table

Practical exercise

Take the sentence you worked on in chapters 1 and 2. Complete it:

1. Which universal need was your feeling signaling?
2. Formulate a request that is concrete, positive and negotiable.
3. Read the full OFNR sentence aloud. Does it sound like an invitation or a reproach?

Summary

The last two steps of NVC turn introspection into dialogue. The need is the cause of our feelings: universal, it offers common ground where strategies clash. The request must be concrete, positive, doable and above all negotiable — a poorly welcomed "no" reveals a disguised demand. Rosenberg distinguishes action requests from connection requests, the latter securing the bond before action. The complete OFNR sentence frames the four steps as an invitation rather than an attack. The next chapter is a quiz: check what you've learned before tackling empathic listening.