Plain, specific requests for a budget, a role, or support succeed more often than the people making them expect, because colleagues agree more readily than requesters predict.
An example
For two years, the director of sales at a resort hotel had hinted that the property needed a dedicated group-sales manager for corporate retreats. She mentioned it in budget meetings, attached a slide to quarterly reviews, and once raised it with the regional vice president in a hallway. Nothing came of it, and she concluded the answer was no. In his first week, a new general manager asked her what she needed most. She said it plainly: one group-sales manager at a salary of $78,000, and the authority to discount retreat packages by up to fifteen percent. She added the four retreats lost the year before to competitors with dedicated staff. He approved the hire on the spot and the discount authority after checking with finance. When she later mentioned the earlier hints, he said nobody had ever put the request to him.
Why it works
A plain request gives the other person something clear to say yes to, which makes agreeing easier. Hints and suggestions leave the listener unsure what is being asked and make it easy to defer; a direct request with a specific amount and a reason costs them little to grant if they are inclined to. People also tend to underestimate how willing others are to agree to direct requests, so many never ask at all. The request still has to be reasonable, specific, and backed by a reason, and made to someone who can grant it.
The thinking behind it
Francis J. Flynn If You Need Help, Just Ask: Underestimating Compliance with Direct Requests for Help (2008), by Flynn and Lake, found in campus and field studies that people asking for help overestimated by about half how many people they would need to approach before someone agreed. Askers underestimated the social pressure others feel to say yes, and direct requests worked better than indirect ones. Two years of hints are the indirect form; one plain request is the direct one.
Jeffrey Pfeffer Power: Why Some People Have It and Others Don't (2010) advises standing out, including by asking powerful people for help and advice, as part of building a personal power base. The book is written for a general business audience. Its relevance here is that asking is a move many managers avoid, and a plain request to the person who can grant it is one of the cheapest ways to get what a plan needs.
When it fits
Almost any situation where you need a resource, a role, or support from someone with the authority to give it will do. It needs a specific request, a reason the other person can accept, and the standing to ask. Try it especially when you have been hinting and assuming the answer is no.
How to use it well
Most of the work is preparation; the ask itself is short.
- Decide exactly what you want: the amount, the role, the authority, the date.
- Find the person who can say yes and ask them directly. A deputy or a committee will refer it upward.
- Say it in one or two sentences, with the reason and the evidence that matters most to them.
- Stop talking and wait for the answer.
- If the answer is no, ask what would make it yes, or when to ask again.
For many people, the hardest part is making the request at all.
What it costs and where it backfires
A direct request can be refused, and a refusal on record is harder to revisit than a hint that went nowhere. Asking too often, or for too much, wears out goodwill. Some bosses and some company cultures read directness as pushiness, so match the register to the setting. Directness has no dirty form of its own, though it can be paired with one: an ask backed by an implied threat, or by figures you have shaded, stops being a request.
When it is used on you
Asked plainly for something, answer plainly: yes, no, or what it would take. A clear no serves both of you better than a vague maybe. If direct requests make you uncomfortable, separate the discomfort from the merits and judge the request as you would one that arrived in writing.