How to Use This Book
Each chapter follows the same structure as the other books in this series, so once you're familiar with it, you can move through the book efficiently or jump directly to the chapter you need most.
Every chapter opens with a real-world scenario and a negotiation dialogue — read these first, even if you're tempted to skip to the expressions lists. The language means more once you've seen it used under real pressure, with a real outcome at stake.
You'll then find key vocabulary, useful expressions (organized by what you want to do, not by grammar), language patterns, and a communication strategy section explaining the thinking behind the language. Each chapter also flags a common mistake, offers Say This, Not That comparisons, and closes with practice exercises, a role-play, and a Kognixr Challenge — a more demanding, realistic task.
You don't need to complete every exercise type in every chapter to benefit from it. If you're short on time, prioritize the dialogue, the Useful Expressions, and the Role-Play — that combination gives you the fastest route to real spoken confidence at the negotiating table.
The Reference Section at the back is designed to be used long after you've finished the book — as a quick lookup the night before a real negotiation.
Introduction
Most professionals who pick up this book can already hold a conversation in English. That's not the problem this book solves.
The problem is more specific. You understand what's being proposed. You know your numbers, your constraints, your priorities. But the moment a negotiation actually starts — the moment someone pushes back, goes quiet, or asks for something you weren't expecting — the English that would let you respond with the same precision you'd use in your own language doesn't quite arrive. You soften a firm position into something that sounds like it might move. You accept a first offer because rejecting it felt more aggressive than you meant it to be. You agree to "look into it" when what you actually meant was no.
None of that is a knowledge problem. It's a language-under-pressure problem, and it's exactly what this book is built to address.
Negotiation, in most professional lives, doesn't look like the dramatic, table-thumping version people imagine. It looks like a procurement manager asking a supplier for a better rate. A consultant explaining to a client why the scope they're asking for needs a different budget. A project manager and a department head working out who gets a shared analyst next week. A hiring manager and a candidate landing on a start date and a number. These conversations happen constantly, and they are almost always conducted in the same register as any other professional conversation — measured, specific, and largely free of drama. The skill isn't performing confidence. It's having the right sentence ready at the right moment.
This book follows two recurring settings. The first is Norhaven Logistics, the company introduced in Professional English for Meetings — you'll recognize Amara Osei, Priya Raghavan, Tom Bricknell, Karel, David, and Mireille, now negotiating internally over resources, deadlines, and responsibilities. The second is external: Norhaven's dealings with Halvorsen Retail Group, a client renegotiating its service contract, and Draycott Freight Solutions, a supplier Norhaven depends on for regional trucking capacity. Between the two, you'll see negotiation from every angle a working professional is likely to face it — as the person asking, the person being asked, and the person in the middle.
You don't need a background in negotiation theory to use this book, and you won't find much of it here. What you'll find is language: how to open a negotiation without sounding either weak or combative, how to ask the questions that reveal what the other side actually needs, how to make a proposal that invites a response instead of a flat no, how to hold a position firmly without damaging a relationship you'll need again next quarter, and how to close a deal so that everyone in the room agrees on what was actually agreed.
The Learning Framework
Throughout this book, you'll notice the same five-part rhythm running underneath almost every chapter and every negotiation: Prepare → Open → Explore → Bargain → Close.
You prepare — deciding what you actually need, what you'd like, and what you can live without, before anyone else's position has had the chance to shape yours. You open — setting a tone that's collaborative without giving away your position before you've even sat down. You explore — asking the questions that surface the other side's real constraints, which are usually different from their opening statement. You bargain — proposing, countering, conceding deliberately, and holding firm where it genuinely matters. And you close — confirming exactly what was agreed, in language specific enough that nobody can misremember it later.
This isn't a script to recite. It's a shape. Once you can see it, you'll start noticing it in negotiations you're already having — including ones you didn't realize were negotiations at all.
CH. 01 |
Understanding Professional Negotiations
Most people picture negotiation as something that happens across a table, with two sides and a clear finish line. In professional life, it's usually quieter than that — a scope question in a Slack thread, a scheduling conflict between two teams, a supplier asking for a rate review. This chapter is about learning to recognize a negotiation when you're actually in one, so you can respond to it deliberately instead of by accident.
LEARNING OBJECTIVES By the end of this chapter, you will be able to: ✓ recognize everyday workplace situations that are actually negotiations ✓ distinguish negotiating from simply refusing or simply agreeing ✓ name what you need clearly, without either demanding or apologizing ✓ approach a negotiation as a shared problem to solve, not a contest to win |
◆ Real-World Scenario
Priya Raghavan has been at Norhaven Logistics for over a year now — confident enough these days that new colleagues assume she's been there much longer. On Tuesday morning, Amara Osei stops by her desk with what sounds, at first, like a simple request.
◆ Negotiation Dialogue
Amara Priya, have you got a minute? I want to bring you onto the Halvorsen account. Elena Marsh — their procurement director — wants a Norhaven analyst on the weekly call starting next week.
Priya That sounds great, actually. I've wanted more client-facing work. What would it involve?
Amara Weekly call, plus you'd own the reporting pack they get every Friday.
Priya Okay — and this is on top of the Draycott renewal work, or instead of it?
Amara On top of, at least for now.
Priya I think I can make that work, but I want to flag something before I say yes. The Draycott renewal is already taking more of my week than it was supposed to — probably six or seven hours, not the three we scoped.
Amara I didn't realize it had grown that much.
Priya It has. So if I take on Halvorsen as well, something has to give somewhere — either I get some support on Draycott, or the Halvorsen reporting pack needs to be lighter than what you're describing.
Amara That's fair. What would "lighter" look like?
Priya Honestly, the two-page summary version, not the full pack, at least until I've got Draycott back down to its scoped hours.
Amara I can sell that to Elena. Let's do that for the first month and revisit.
Priya That works for me.
◆ Understand the Communication
Nothing about this conversation looks like a formal negotiation — no offer, no counteroffer, no handshake. But look again at what actually happens. Amara arrives with a request that has an implicit assumption built into it: that Priya has the capacity to simply add this to her week. Priya doesn't refuse, and she doesn't simply absorb it either. She does something more useful: she names the real constraint ("six or seven hours, not the three we scoped") and then proposes two possible ways to resolve it, before Amara has to guess what she wants.
This is the core move this whole book is built around. A negotiation doesn't require two sides staking out opposing positions from the start. It requires one side noticing that a request has a cost, and saying so specifically enough that a solution becomes possible. Priya's line — "something has to give somewhere" — does a lot of work in five words: it's honest, it's not accusatory, and it hands Amara a real decision instead of a vague complaint.
Notice, too, that Priya doesn't open with an apology or a justification for having limits in the first place. She states the fact (the hours), states the consequence (something has to give), and offers two concrete options. That sequence — fact, consequence, options — is one you'll see again throughout this book.
◆ Key Vocabulary
TERM | MEANING | EXAMPLE |
flag (something) | to raise an issue so it's noticed before it becomes a problem | "I want to flag something before I say yes." |
something has to give | one constraint must be relaxed if another is to be met | "If I take this on too, something has to give somewhere." |
scoped (hours/work) | originally agreed or planned | "It's taking more time than the three hours we scoped." |
capacity | the amount of time or resource available to take on work | "I don't have the capacity to add this right now." |
on top of | in addition to (an existing workload) | "Is this on top of the Draycott work, or instead of it?" |
sell (an idea) to someone | to persuade a third party to accept a proposal | "I can sell that to Elena." |
revisit | to return to and reconsider a decision later | "Let's do the lighter version for a month and revisit." |
push back | to resist or question a request or proposal | "I didn't want to push back right away, so I asked a question first." |
◆ Useful Expressions
Recognizing you're being asked for something that has a cost
• "Before I say yes, I want to flag something." • "Can I just check what this would actually involve?" • "Is this in addition to what I'm already doing, or in place of it?"
Naming a constraint without refusing outright
• "I think I can make that work, but..." • "That's possible, with one condition." • "Something would have to give if I take this on as well."
Turning a refusal into a proposal
• "Rather than saying no, can I suggest an alternative?" • "What if we approached it differently?"
◆ Language Patterns
Professional negotiation English relies heavily on structures that state a fact and a consequence together, without either apologizing for the fact or exaggerating the consequence:
1. It's taking + [more/less] + than + [expected] — "It's taking more time than we scoped."
2. If + [action], then + [consequence] — "If I take this on too, something has to give."
3. That's possible, + [condition] — "That's possible, as long as we can push the deadline."
These patterns work because they're neutral. They describe a situation rather than assigning blame, which keeps the conversation focused on solving a problem rather than defending a position.
COMMUNICATION STRATEGY Treat every request with a hidden cost as an invitation to negotiate — not an instruction to comply. Many professionals, especially early in their careers or working in a second language, hear a request from a manager or client and process it as an instruction rather than a starting point. But most workplace requests are opening positions, whether the person making them realizes it or not. Amara's request to Priya wasn't a fixed instruction — it was one possible version of a plan, offered before either of them knew what it would actually cost. Treating it as negotiable, respectfully and specifically, is what let a workable version emerge. |
COMMON MISTAKE Saying yes immediately to avoid seeming difficult. Many learners, uncomfortable with the discomfort of raising a constraint, agree to requests they haven't actually thought through — then either struggle silently to deliver, or quietly do a worse job on something else to compensate. Neither outcome serves anyone, including the person who made the original request. Better approach: A brief pause before agreeing — "Let me just think through what that would involve" — is almost always well received, and it buys you the two seconds you need to notice a real constraint before you commit to ignoring it. |
◆ Say This, Not That
Less effective: "Sure, no problem, I'll figure it out." (said while privately certain it will require unpaid overtime and a dropped deadline elsewhere)
More effective: "I can take this on, but I want to flag that something else will need to shift — can we talk through what?"
◆ Practice
Exercise 1 — Recognition
Read each situation and decide: is this actually a negotiation, even though it might not look like one?
a. A colleague asks if you can "just quickly" review a document that turns out to be forty pages long.