Requests that come with their reason attached, stated plainly, win more agreement than the same request alone, and only a real reason carries the larger asks.
An example
Forty-two store managers at a home goods retailer were asked to run a full count of seasonal stock on a Sunday in late January, a day most had planned to close early. The first draft of the email from the regional director of store operations said only that counts were mandatory and due by six. She rewrote it. The new version explained that the chain had written off $3.8 million in seasonal stock the year before, that most of it had sat in back rooms nobody had counted, and that the Sunday counts would decide which items the buyers reordered for spring, and in what quantities, store by store. She asked managers to reply with any store that could not make the date. Forty of the forty-two counts came in on time, and the two late stores had asked for, and got, an extra day.
Why it works
Compliance rises when a request comes with its reason, so the request itself looks better. For a small favor almost any reason helps; for a larger one, people pay attention, and only a real, specific reason moves them. Saying why also signals respect and lets people judge the request on its merits. It depends on the reason being true, relevant, and stated plainly, and on the person asking being someone whose reasons have held up before.
The thinking behind it
Ellen J. Langer In The Mindlessness of Ostensibly Thoughtful Action: The Role of "Placebic" Information in Interpersonal Interaction (1978), Langer, Blank, and Chanowitz asked people at a copying machine to let someone go first. For a small request an empty reason worked almost as well as a real one; for a larger request only the real reason raised compliance. The study used one setting. It supports giving reasons, and it is why this page says the big asks need true ones.
When it fits
Any request that asks people to spend effort, time, or goodwill qualifies: a deadline, a change in routine, a favor across departments. It needs nothing but a true reason and the habit of stating it, and it matters most when you have little authority over the people you are asking.
How to use it well
Before you ask, write down why you need it, in one or two sentences a skeptic would accept.
- Make it specific: the number, the customer, the deadline it serves.
- Put the reason before or beside the request, never buried below it.
- For a big ask, give the real stakes and what the work will be used for.
- Say what happens if they cannot do it, and how to tell you.
Check the reason against what you know. A stated reason that later turns out to be thin costs you every request after it.
What it costs and where it backfires
Almost nothing, which is why people skip it. The risk is a weak reason given for a big request: people see through it, and the request looks worse than if you had given none. A reason that turns out to be false is a lie and will be remembered. Over time, a habit of giving real reasons builds a record that makes future requests easier to grant.
When it is used on you
Check whether the reason attached to a request actually supports the size of what is being asked. A small favor needs little justification; a large commitment needs a real one. Ask what the work will be used for and what happens if you say no, and decide on those answers.