Guide

What to do if your boss says no

The short answer

Find out which no it is before you react to it.

A flat, permanent no is rare for a well-made case. What people usually hear, and then file in their head as rejection, is one of three much softer things:

  • Not this cycle. A timing answer. The case is fine; the window is shut.
  • Not at that number. A pricing answer. They've accepted the argument and are negotiating.
  • Not my call. An authority answer, and often the real one. Your manager agrees and can't deliver it alone.

Those need three different responses, and none of them is the one most people give, which is to say "that's fine, I understand" and quietly start resenting the job.

What you do in the ninety seconds after hearing no matters more than anything you said before it. Ask which of the three you've got, agree a date, and get it in writing.

In the room: ask, don't argue

The instinct is to defend the case again, louder. Don't. If the argument was going to land on volume it would have landed already, and re-arguing turns a colleague into an opponent.

Ask instead. Three questions, in this order:

  1. "Is it the case, the timing, or the number?" This is the whole game. You cannot respond usefully until you know which one you're dealing with, and most managers will tell you straightforwardly if you ask plainly.
  2. "What would have to be true for this to be a yes?" It moves the conversation from a verdict to a set of conditions, and conditions can be met.
  3. "Who else would need to agree, and when do they decide?" This surfaces whether your manager is your approver or your advocate — which changes everything about what you do next.

Then stop and let them answer. You're collecting information, not winning.

A first answer is not the last word.

The four answers and what each means

"Not this cycle." The commonest, and usually true. Budget and headcount get decided in windows, and outside the window your manager genuinely has nothing to spend. Your response is a date: when does the next window open, and what do you need to have done by then? Agree to revisit at a specific point and the answer converts from a refusal into a schedule.

"Not at that number." This is not a rejection. It's an opening offer, and it means the underlying case has been accepted — nobody negotiates the price of something they don't want. Don't split the difference on the spot. Ask what number they think is defensible and what evidence would support yours, then take it away and come back.

"Not my call." The most important one to hear correctly, because it isn't a no at all — it's a request for help. Your manager is now your advocate rather than your approver, and their problem is that they have to win an argument upstairs with whatever you've given them. So ask what they need: what does their boss respond to, what's the format, what's the timeline, and what can you write that they can forward? Everything in the method is built for this case.

"You're not there yet." A performance answer, and the only one that's genuinely about you. It's also the one most worth pinning down, because it is otherwise infinitely extensible. Ask what "there" is, specifically, in terms of scope and outcomes rather than qualities. "More leadership" is not an answer you can act on. "Owning the vendor relationship end to end, through one full renewal" is.

Get the conditions in writing

Whatever you hear, send a short note the same day setting out what you understood.

Not as a challenge — as a record. Thanks for the conversation. To make sure I've got it right: the case makes sense, the constraint is the current budget cycle, and we'll pick this up in January against these two things. Have I understood that correctly?

This does the same work the original written follow-up did. It puts the conditions somewhere they can be forwarded, it makes them concrete enough to be held to, and it quietly signals that you are treating this as an ongoing process rather than a closed question. It also protects you against the commonest failure here, which is not refusal but drift — a manager who meant it at the time, and a January where nobody remembers what was agreed.

The next three months

If you got a condition, work on the condition — visibly. The point is not just to meet it but to be seen meeting it, because the person deciding in January will be reconstructing the last few months from memory.

If you got a timing answer, use the gap. It is genuinely easier to make this case the second time: you already have the analysis, your manager has already heard the argument once, and the objection you got last time is a thing you can now answer preemptively.

And keep the document current. Proposals decay — the opportunity you identified gets taken by someone else, the problem you offered to solve gets solved. Revisit it before you revisit the conversation.

When no really does mean no

Sometimes it does, and there's no benefit in pretending otherwise.

The signals are fairly clear. A manager who won't name any condition under which the answer changes. A second cycle passing with the same explanation as the first. Agreement in the room that never survives contact with anyone else. Or a straightforward statement that the band is the band and the role has no route above it.

That's real information, and it's worth what the whole exercise cost you. You now know something about your employer you didn't know before, and you know it while you still have the analysis, the evidence and the written case — which is most of the preparation for looking elsewhere.

The work isn't wasted. It transfers.

Decide all this in advance

The reason to read this before the conversation rather than after is that your judgment will be worse afterward than it is now.

Work out while you're calm: which of those answers could you live with? What would you need to hear in order to stay? What do you want to revisit in three months, and what would have to be true by then? Deciding in advance is what stops you either capitulating in the room or overreacting that evening — the two failure modes, and both expensive.

Questions

Should I ask why I was turned down?

Yes, immediately and plainly, but ask which kind of no it is rather than for a justification. "Is it the case, the timing or the number?" gets you something actionable. "Why not?" invites a defense of the decision, which makes it harder to revisit.

How long should I wait before asking again?

Tie it to the organization's cycle rather than a fixed interval, and agree the date in the room. If a specific condition was named, the answer is when that condition is met, which may be sooner.

Is it worth accepting a title change without more money?

Sometimes, if the title genuinely reflects larger scope and your employer's bands are attached to titles — you've moved the ceiling you'll be arguing under next time, and made the role more portable. It's a bad deal if it's only a label, or if it arrives with more work and an indefinite promise.

Should I threaten to leave?

No. It works occasionally and it permanently changes how you're read, from someone building a case to someone applying pressure. If you'd genuinely leave, that's a real decision worth making properly rather than a lever to pull in a difficult meeting.

What if my manager just keeps avoiding the conversation?

Treat avoidance as the answer it is, and make it harder by moving to writing and naming dates. A proposal with a specific requested response date is much harder to let drift than a standing request to talk. If two of those pass without a substantive reply, you've learned what you needed to know. ---


Ready to do it properly?

The free course helps you build the case, decide the number, and work out in advance what you'll do with each kind of answer. About fifteen minutes, nothing to buy, and nothing you write ever leaves your browser.

Start the free course →

Embed this calculator

Paste this into any page. Free to embed — please keep the link.

Who wrote this

Rob Barnett. I've run product and research teams, which means I've been on both sides of this conversation — making the case for my own role, and sitting across from people making theirs.