You asked your manager for headcount. They said it wasn't the right time.
You asked for budget for a tool that would save you fifteen hours a week. They said maybe next quarter.
You asked to lead the strategic project everyone's talking about. They said they'd think about it.
You walked out of those conversations slightly demoralised, slightly confused, and slightly less inclined to ask for anything for the next six months. You couldn't put your finger on why the answer was no. The request seemed reasonable. The case seemed obvious. And yet, here you are.
The reason is almost never what you think it is.
Where requests go wrong
Most professional requests fail before the meeting starts. They fail because the person making the request hasn't done one piece of mental work the senior person needed them to do.
Senior decision-makers don't process requests the way the person making them imagines. The person making the request is thinking about the problem from their own seat. What they need. Why it would help. How it would solve their current pain. That's a perfectly logical position to think from. It's just the wrong one.
The senior decision-maker is sitting in a different chair, and from that chair, your request looks completely different. They're balancing twelve to twenty open commitments. They're thinking about precedent (if I say yes to this, who else will ask?). They're thinking about risk (what happens if this goes wrong and someone asks me why I approved it?). They're thinking about timing (does this need to happen now, or can it wait three months?). They're thinking about politics (whose budget am I taking from, and what will that cost me later?).
None of this is in your request. None of it is your fault either. It just means that when your request lands on their desk in the form you've prepared it, they're being asked to do the thinking work themselves. Most of the time, they won't. They'll just say no, or "not yet", or "let me come back to you".
The mental shift
The change you need to make is to stop preparing requests from your own perspective and start preparing them from the seat of the person who has to approve them.
This sounds obvious. It is. But almost nobody does it, because doing it properly is harder than it looks.
It requires you to know what your decision-maker is actually worried about. Not in general. This quarter. This month. This week. It requires you to know what they've already said yes to, what they've recently said no to, and what's been hanging over their head that they haven't decided on yet.
If you don't know those things, your request is being made in the dark. You're hoping it lands well. The senior person is reading it through a filter you haven't even mapped.
The three questions before you ask
Before you make any significant request, write down the answers to three questions. If you can't answer all three, you're not ready to make the request.
One. What is the decision-maker's most pressing concern this quarter? Not what they say in town halls. What they're actually losing sleep about. The cost overrun. The departure of a key hire. The performance of a unit. The board conversation coming up.
Two. How does my request connect to that concern? If your request doesn't touch their pressing concern in some way, it's not going to feel urgent to them. It'll feel like an extra thing to think about. That's a no.
Three. What is the smallest version of this request that would get me 80 per cent of what I need? Because the smallest version is the one most likely to clear. Then the bigger version becomes a follow-up once you've built credibility on the smaller one.
I worked with a senior director last year who'd been asking her CFO for a £400k budget increase for two years running. Every year, no. We rebuilt the request as a £90k pilot tied to a specific KPI he'd publicly committed to. He approved it inside four days. Twelve months later, she had the full £400k, plus another £150k to extend it.
The £400k wasn't the wrong number. It was the wrong sequence.
What you stop doing
Three things to stop doing the moment you read this.
Stop building requests as comprehensive business cases. They feel safe to you. They feel like work to your decision-maker.
Stop framing the request in terms of what's fair or what you're owed. Fairness is irrelevant in a system optimising for risk and outcome. Bring fairness to your manager privately, but never make it the spine of an ask.
Stop asking before you've signalled. If your request is the first time your decision-maker hears about the topic, you've shortened the conversation to the binary "yes or no". The yes rarely happens cold.
"If you want a yes, make it easier to say yes than to say no." A line I picked up years ago from a Saudi finance director. It sounds obvious until you realise how often you've made the opposite true.
On Thursday, the seven-step structure I use with clients for any significant request. Used correctly, it lifts approval rates above 80 per cent. Used the way most people make requests, you're operating at maybe 30.
