Most asks don't fail because the answer is no. They fail because they were never really an ask, they were a hint, and nobody noticed.
The request gets wrapped in so much hedging it stops sounding like a request. "I don't know if this makes sense, but maybe at some point we could look at possibly adding someone to the team" is not an ask anyone can act on. It's a thought your boss will nod at and forget by the next meeting.
"So the team's been really stretched lately, and I've noticed some things slipping, and I don't want to make a big deal out of it, but I was wondering if maybe down the line we might think about whether another person could help out at some point."
"I'd like to open a headcount request for one additional engineer on the team. Here's why: we've missed two deadlines in the last quarter because of capacity, not skill. I've attached the workload breakdown. Can we talk this week about whether that's something you can support?"
The second version isn't aggressive. It gives your boss something to say yes to, push back on with a real reason, or tell you what would need to be true first. All three beat the vague nod, because at least you know where you stand.
- Know the number or outcome you want, not a range you're hoping to negotiate up from.
- Have one piece of evidence ready, a missed deadline, a workload breakdown, a comparable data point, so the ask isn't just a feeling.
- Decide your fallback before you need it, so a "not right now" doesn't derail the conversation before you've heard the reasoning behind it.
- Time it on purpose. A crisis, a hallway, or the last five minutes of a 1:1 gets you a distracted answer. Giving your boss runway to actually think gets you a real one.
Who's on the other side of the ask changes what it needs to do. Here's how the same move plays out with an executive, with budget or headcount, and when the first answer doesn't come.
"I'd like your approval to add one contractor to the migration project for six weeks, at roughly $18k. Without it, we're on track to miss the Q3 deadline you flagged as a priority. With it, we hit that date with margin."
Have your fallback ready before you walk in. "If the full budget isn't available, would a smaller three week pilot work?" gives them a path to a partial yes instead of forcing an all or nothing decision on the spot.
Ask yourself the question they're actually going to ask you: what does this cost us if the answer is no? Then bring a specific, measurable case instead of a feeling.
"We're missing [specific capability], and it's costing us [specific, measurable thing]. If a full hire isn't possible this cycle, I'd take a contractor for the next two quarters while we build the case for permanent headcount."
A good follow-up doesn't apologize for existing and doesn't scold. It restates the ask, adds what's new since you first asked, and makes it easy to act on right now.
"Sorry to bug you again, I know you're busy, just wanted to circle back whenever you get a chance."
"Just following up on this, as I mentioned last week."
"Following up on the budget sign-off from Tuesday, I need it by end of day tomorrow to keep the vendor contract on schedule. Let me know if you need anything else from me to make the call."
Every version of this ask works the same way underneath: say it plainly, back it with one real piece of evidence, and know what you'll say next before you need to say it. Stop hinting. Ask.