How to ask: the difference between a request and a demand

Most people learn to be polite long before they learn to ask. The two are not the same skill, and the gap shows up in a small, testable place: what happens if the other person says no.

A request is defined by the answer «no»

Marshall Rosenberg, who built Nonviolent Communication around this distinction, put the test simply: it is a request if a refusal is genuinely allowed. If «no» costs the other person your mood, your silence, or a reminder of what they owe you, what you made was a demand in polite clothing.

People hear this instantly, long before they could name it. That is why the same sentence — «could you look at this today?» — reads as an ask from one person and as pressure from another. The words are not carrying the difference; the history of what happens after «no» is.

The practical consequence is uncomfortable: you cannot fix your asking by improving the wording. You fix it by making refusals survivable, and then the wording matters.

Name the thing, not the mood

The most common failure of an ask is that it never contains the ask. «It would be nice if someone finally sorted out the kitchen» is a description of a feeling. The other person has to work out that a request happened, what exactly it is, and whether it is aimed at them.

A workable ask has three parts, and all three are short: what specifically, by when, and why it matters. «Can you take the kitchen tonight? I have a call at eight and won't get to it» is the whole thing.

Naming the reason is not justification, it is information. It lets the other person offer something better than what you asked for — which they can only do if they know what the ask is for.

The moment costs more than the phrasing

An ask arriving at a bad moment gets refused for reasons that have nothing to do with the ask. Someone halfway out the door, mid-task, or just home from a hard day is not evaluating your request; they are defending their remaining attention.

One sentence solves most of this: «is now a good time?» It sounds like a formality and works like a filter — it moves the refusal to a cheap place, before the ask, where saying «not now» costs nobody anything.

The same goes in the other direction. Asking at the last minute is not just inconvenient; it removes the other person's ability to plan, which is often the real thing they resent.

Refusal is data, not verdict

The hardest part of asking well is hearing «no» as information about capacity rather than about your worth. Most refusals are about time, energy or competing obligations, and almost none are about whether you deserved help.

Two habits make refusals cheap for everyone. Do not press after a clear no — pressing teaches people that refusing you takes three attempts, and they will start avoiding the conversation instead. And do not go quiet afterwards: silence after refusal is the most common way a demand reveals itself.

If a refusal genuinely leaves you stuck, that is a separate conversation about the problem, not a rerun of the same ask with more feeling.

Thanks that says what happened

«Thanks» is a formality. «Thanks — you saved me two hours, I was going to miss the deadline» is information: it tells the person what their effort actually did, which is the part they cannot see from where they stand.

This is not politeness theatre. People repeat what they can see the effect of, and effort that disappears without trace stops being offered. Specific thanks is the cheapest way to keep help available.

And say it to the person, not about them. Praise delivered behind someone's back is pleasant to overhear and useless as feedback.