How does "Make requests specific, present-tense, and doable" work?

Vague requests put the burden of interpretation on the other person and create the conditions for disappointed expectations. "I need you to be more supportive" is a need statement, not a request — the other person cannot verify whether they’ve met it. "Would you be willing to put your phone away during dinner this week?" is specific, observable, and time-bounded. The precision matters because it allows for clear agreement or negotiation, and it makes it possible to check whether the request was met.

How does "Receive "no" without punishment or withdrawal" work?

If a "no" is followed by guilt-inducing silence, visible disappointment used as pressure, or overt criticism, the other person learns that your requests are demands with a polite surface. Over time, they stop saying no honestly — they comply without real consent, or they avoid you to avoid the request. Receiving "no" without punishing teaches people that their autonomy is real, which is what makes future requests genuinely safe to answer honestly.

How does "Connect empathically before making a request" work?

When someone is in an activated or distressed state, they cannot easily process a request — their attention is on the emotion, and the request lands as an interruption or a transaction. Offering empathy first — acknowledging what the person seems to be experiencing — signals that you are attuned before you ask something of them. This lowers defensive activation and makes genuine consideration of the request possible. The sequence matters: empathy first, request second.

Nonviolent Requests: How to Ask for What You Need Without Demanding

Q: How does "Test whether your request is actually a demand" work?

Demands communicate conditional regard: the message (stated or implied) is that a "no" will result in punishment, withdrawal, guilt, or judgment. People respond to perceived demands with compliance (which breeds resentment) or resistance (which escalates conflict) — rarely with the genuine, freely given cooperation that requests are meant to generate. The demand-request distinction matters because cooperation given under threat is qualitatively different from cooperation given freely: it doesn’t build trust and it doesn’t last when the threat is removed.

Q: How does "Distinguish connection requests from action requests" work?

Rosenberg distinguished two types of NVC requests: connection requests (asking someone to reflect back how you’re feeling, to be present with you) and action requests (asking someone to do or stop doing something). Conflating them is a common source of communication failure: people bring a connection need and get problem-solving, or bring an action request and get sympathy when they needed the thing done. Making the type of request explicit removes the misread.

Q: How does "Request that the other person reflect back what they heard" work?

Asking someone to reflect back what they heard from a request serves two functions: it checks comprehension (did the words mean the same thing to both people?) and it slows the conversation enough for genuine reception rather than reactive response. Communication failures — including requests that don’t get met — are often failures of comprehension rather than goodwill. The reflection test reveals these failures before they become conflicts.

What makes a request in Nonviolent Communication different from a demand, and why does it matter?

In Marshall Rosenberg’s NVC framework, a request differs from a demand in one critical way: a request is made with genuine willingness to hear "no." A demand masquerading as a request communicates that the other person’s autonomy is conditional — which triggers compliance or rebellion, not genuine cooperative response. Making true requests is among the most practically difficult NVC skills; most people discover they have been making demands when they notice how they feel when the answer is no.

Marshall Rosenberg identified the request as the fourth step in Nonviolent Communication (after observation, feeling, and need) — and noted that it is also the step most commonly done wrong. Most people make requests that are actually demands: the language is polite, but the underlying message is "comply or face consequences." The test is simple: how do you feel when the answer is no? If no is unacceptable, the request was a demand. The practices below cover how to make genuine requests — and what getting better at them requires.

Practices

Test whether your request is actually a demand

If "no" is not okay with you, you’re making a demand.

Make requests specific, present-tense, and doable

A genuine request names exactly what you’d like done, by when, in observable terms.

Distinguish connection requests from action requests

Sometimes you need empathy; sometimes you need someone to do something — these are different asks.

Receive "no" without punishment or withdrawal

The quality of your response to "no" is what teaches others whether your requests are genuine.

Connect empathically before making a request

A request made before connection has been established is often experienced as a demand.

Request that the other person reflect back what they heard

Ask for a reflection, not a response — it tells you whether communication actually happened.

Practice this with IX Coach

Reading about a practice changes nothing on its own. IX Coach turns these into a guided, adaptive routine — discerning where you are in real time and walking the practice with you, session after session.

Practice this with IX Coach

IX Coach: 7 days free, then $40/month (about $1.30/day).

Nonviolent Requests: How to Ask for What You Need Without Demanding

Practices

Test whether your request is actually a demand

Make requests specific, present-tense, and doable

Distinguish connection requests from action requests

Receive "no" without punishment or withdrawal

Connect empathically before making a request

Request that the other person reflect back what they heard

Practice this with IX Coach

Related