Asking for a Raise Without Turning It Into a Standoff
How to run a pay conversation as a problem you and your manager solve together, using three documented negotiation approaches from Fisher and Ury, Chris Voss, and Deepak Malhotra.
You have the number in your head. You also have the reasons: the project that shipped, the work you absorbed when someone left. And you have a calendar invite titled "quick chat?" that you keep not sending, because you can already hear how the first thirty seconds will go.
What are you actually negotiating?
Most advice treats the raise as a case to win. List your achievements, state a number, hold your nerve. That works when your manager is the sole decision maker with money to spend, which is rarer than it sounds.
More often your manager has to take your request upward, fit it inside a band, justify it against peers, and do all of it before a deadline you cannot see. Your case is not the only thing in play. Their ability to carry it is.
Ask a chatbot to "help me ask for a raise" and you get a confident script about your accomplishments. It leaves out the one thing that decides the outcome: what your manager needs in order to say yes, and what is stopping them.
How do three documented approaches handle it?
Roger Fisher and William Ury: argue from criteria, not from what you deserve
Fisher and Ury's Getting to Yes (1981) rests on four moves: separate the people from the problem, focus on interests rather than positions, invent options for mutual gain, and insist on objective criteria. The last one matters most here.
Applied: "I deserve more" is a position, and positions get met with positions. Market data for the role, the company's published band, and the scope you now cover are criteria your manager can check and defend upstairs. Ask which criteria the company uses for adjustments, then build your case on those.
"I want to ask for a raise. My role is [role], I have been in it [time], and my scope has grown in these ways: [list]. Help me identify three objective criteria my manager could verify, such as market ranges, internal level definitions, or documented scope changes. For each, tell me what evidence I would need to bring and where it could be weak."
Why it works: asking for checkable criteria, plus where each is weak, stops you walking in with evidence your manager can dismiss in one question.
Chris Voss: ask calibrated questions to find the real constraint
Voss's Never Split the Difference (2016, written with Tahl Raz) describes calibrated questions: open questions starting with "how" or "what" that invite the other person to explain their situation. His best-known example is "How am I supposed to do that?", a polite way of handing a problem back.
Applied: After stating your case, ask "What would need to be true for this to be approved?" or "How are adjustments like this usually decided here?" The answer tells you whether the barrier is budget, band, timing, or conviction, and each needs a different next step. Voss's examples come from crisis and commercial settings, so keep the tone collaborative; you will work with this person tomorrow.
"My manager's likely objections to a raise are: [list]. Draft five calibrated questions, each starting with "how" or "what," that help me learn which constraint is real: budget, pay band, timing, or doubt about my performance. Avoid questions that can be answered yes or no."
Why it works: open questions surface the actual barrier, which lets you answer it rather than rehearse a generic rebuttal.
Deepak Malhotra: look past the number to the whole package
Malhotra's Negotiating the Impossible (2016) argues that when talks stall you should understand why the other side is saying no rather than push harder. Negotiation Genius (2007), written with Max Bazerman, makes the case that deals with several issues create value because each side weighs the issues differently.
Applied: If base pay is genuinely stuck, the package is wider than base pay. Title, scope, a dated review, a development budget, or flexibility may cost your company little and be worth a lot to you. Know your priority order before you walk in.
Which approach suits which situation?
| Approach | From | When it fits | Watch out for |
|---|---|---|---|
| Objective criteria | Roger Fisher and William Ury, Getting to Yes | You have market data or clear scope growth and a manager who must justify the decision upward | Weak or cherry-picked data invites a quick dismissal |
| Calibrated questions | Chris Voss, Never Split the Difference | You do not yet know what is blocking the raise | Treating questions as a tactic rather than real curiosity reads as manipulation |
| Package thinking | Deepak Malhotra, Negotiating the Impossible, and Malhotra with Bazerman, Negotiation Genius | Base pay is capped but other terms are flexible | Trading away pay for a vague title with no scope behind it |
What if the answer is no, or not yet?
Fisher and Ury's best alternative to a negotiated agreement, usually shortened to BATNA, is what you will do if this conversation fails. It sets your real floor. If your alternative is a recruiter's pending offer, you know. If it is hoping, you also know, and your approach should reflect it.
Voss treats "no" as the start of the conversation rather than the end. Ask what would change it, then ask for a date: "If I deliver X by the end of next quarter, how would we revisit this?" A specific revisit point is worth more than a warm "let's keep talking."
"My manager said a raise is not possible right now because [reason]. Help me write two or three follow-up questions that establish what milestone or timing would change the answer, and draft a short email after the meeting that summarizes what was agreed, including any date."
Why it works: a written summary with a date turns a soft deferral into something your manager can be held to without confrontation.
What won't a framework fix?
None of these approaches creates budget, overrides a pay freeze, or changes the fact that some companies cap raises by policy. They improve how you prepare and how the conversation runs. They do not tell you what to accept, and this guide is not financial or career advice. Pay transparency rules and notice norms also vary by country, so check what applies where you work.
All four thinkers sit in the Negotiator category: Chris Voss, Deepak Malhotra, Roger Fisher, and William Ury. For the originals, see Getting to Yes, Never Split the Difference, and Negotiation Genius. To structure leverage, options, and concession order before you go in, Negotiation Prep is a $99 tool built for it.
All the copy-paste prompts from this guide, and the rest of the Situations series, live at /prompts too, free to copy without reading the guide first.
Frequently asked questions
Should I name a number first or let my manager name one?
Fisher and Ury's framework doesn't prescribe a side. It asks you to anchor on criteria both of you can check, such as market data and the company's own band for the role. If you have credible data, naming a range grounded in it is defensible. If you have none, asking how adjustments are decided first tells you what evidence your manager actually needs.
How is a calibrated question different from just asking nicely?
Chris Voss describes calibrated questions as open questions that start with "how" or "what" and hand the other person a problem to solve. "What would need to be true for this to happen?" asks your manager to describe the path. "Can you give me a raise?" asks for a yes or no, which is the easiest thing to refuse. Voss recommends asking questions you can actually use, so listen for the constraint behind the answer and respond to that, not to your script.
What if my manager says the budget is frozen?
Treat it as information, then ask what is not frozen. Malhotra and Bazerman's work on multi-issue negotiation suggests the package matters: title, scope, review date, development budget, and flexibility can matter to you in different proportions than they cost the company. Ask for a dated commitment on the pay question if the answer is truly not yet. Write down your priority order before the meeting so you can trade quickly, rather than agreeing to the first package offered.
Is it a bad idea to mention a competing offer?
Only if it is real and you would actually take it. Fisher and Ury define your best alternative to a negotiated agreement as the thing you will do if talks fail, and warn against bluffing about it. A bluff that gets called leaves you with a damaged relationship and no leverage. A real offer stated plainly is information, not a threat. If you are bluffing, your manager is likely to find out, and the cost to your credibility outlasts the negotiation.
Can AI write my raise request for me?
It can draft the case, pressure-test your evidence, and rehearse likely objections. It cannot know your manager's budget authority, the politics of your team, or what was said in the last compensation round. Use it to prepare questions and structure, then run the conversation yourself. A good prompt gives the assistant your evidence and asks it to argue the other side, which is where most preparation gaps show up.
How soon after a good review should I ask?
Documented negotiation advice is about preparation, not a calendar date. The strongest moment is usually when your evidence is fresh and your manager still has time to act inside the cycle that sets pay. Asking after budgets are locked gives them a reason to say no that has nothing to do with you. If you cannot influence the cycle, ask your manager when the next review point is and what they would need from you by then.
Written by Gareth Hoyle. Last updated 8 October 2026. Part of the authority.md guides library.
More guides.
Apologizing to a Customer When You Got It Wrong
How to write an apology a customer believes, using the Trust Triangle from Frances Frei and Anne Morriss, the Trust Equation from Maister, Green and Galford, and Robert Cialdini's commitment principle used ethically.
Running a Post-Mortem Without Blame That Still Changes Something
How to run a review after a failure that finds real causes without scapegoating anyone or letting accountability disappear, using Amy Edmondson, W. Edwards Deming, and Gene Kranz.
Client Scope Creep: Before, During, and After It Happens
How to stop a client's small extra requests from becoming unpaid work, using documented approaches from Blair Enns, William Ury, and Maister, Green and Galford's Trusted Advisor.