Day 55 · 2026.07.14

The Leadership Dimension of Negotiation: From Fighting Over the Pie to Growing It Together

Topic: Negotiation as a Leadership Skill·4 Principles
"Don't bargain over positions. When negotiators bargain over positions, they tend to lock themselves into those positions." — Roger Fisher & William Ury, Getting to Yes
This issue's proposition: As a tech leader, you negotiate every week — over headcount, priorities, setting a report's pay, deadlines with a PM. Most people treat negotiation as "who's tougher," and end up either burning the relationship or caving resentfully. The real work is: move your attention from "positions" to "interests," let a strong BATNA hold up your footing, sequence your moves in a multiparty game, and read what goes unsaid in cross-cultural talks. This issue's four principles — principled negotiation, BATNA, multiparty negotiation, cross-cultural negotiation — turn negotiation from a dark art into executable preparation.
PRINCIPLE 01

Principled Negotiation: Hard on the Problem, Soft on the Person Separate Positions from Interests

interestspositionswin-win
A position is "what I want"; an interest is "why I want it." Deadlock over positions and the pie is fixed — you can only take more or less; step back to interests and there's often a third way to slice it. Before negotiating, ask "why" three times to surface the real need beneath the waterline, then design an option that satisfies both sides' interests.
"The most powerful interests are basic human needs: security, economic well-being, a sense of belonging, recognition, and control over one's life. Reconcile interests, not positions." — Fisher & Ury, Getting to Yes, Ch.3
Situation: You and another EM are fighting over a single headcount slot. You want it, so does he, and you're stuck with neither yielding.
✗ Positions collide

"We need this headcount more — our backlog is longer than yours."
Him: "What we ship next quarter is more critical."
—Both are defending positions; it escalates to the boss, gets decided by power rather than reason, and the loser holds a grudge.

✓ Step back to interests

"Let's not fight over who gets the head. You want the person to hit next quarter's delivery, right? I want it because a system with no owner is leaking. What if the senior slot goes to you for the delivery, and the mid-level you free up transfers over to take on my maintenance work?"

—Two positions both "wanting the same head" sit atop two non-conflicting interests: "hit delivery" and "cover maintenance." Only by opening up interests can you see the swap.

  • What is my position? What real interest (the "why") sits behind it? Write at least 3.
  • I know the other side's position, but do I actually know their interests — or am I just assuming?
  • Have I prepared at least one "grow the pie" option (both interests met), not just "split the pie"?
  • If talks break down, can I appeal to an objective standard (market rate, company policy, precedent) rather than volume?
  • Softness in the wrong place. "Soft on the person" means no personal attacks, not conceding on the option; where you should hold firm on the substance, hold firm — conflate the two and you're just a pushover.
  • Assuming interests conflict. In most deadlocks the interests aren't fully opposed — you didn't ask, so you defaulted to zero-sum.
  • Showing your hand too early. Leading with a position ("I want this number") locks in the interest and blocks the path to a third option.
Female Leader's Note Research (Linda Babcock, Women Don't Ask) shows women initiate negotiations far less often than men, and are more likely to be rated "unlikable" when advocating for themselves. A practical hedge: frame the negotiation as for the team / the shared goal rather than purely for yourself — "this headcount removes a single point of failure on the whole line" is harder to label as aggressive than "I want it," and it matches the "talk interests" essence of principled negotiation.
Exercise: Pick a negotiation you're stuck on (resources, priorities). Write two columns: each side's "positions" and "interests." Look at the interests column — is there one that could produce a win-win swap?
Reflection: Last time talks broke down, was it a real conflict of interest, or were we both just locked into positions and never stepped back?
PRINCIPLE 02

BATNA: Your Footing Comes Not from Bluster but from the Ability to Walk Your Power Is Your Best Alternative

alternativewalk-awayleverage
BATNA = your best route out if the deal fails. Your real power at the table equals your ability to stand up and go pursue that route — not how much you want the deal, but how much you don't need it. To boost bargaining power, don't bluff — improve your BATNA; and estimate the other side's BATNA accurately, so you know where their bottom line sits.
"The reason you negotiate is to produce something better than the results you can obtain without negotiating. The better your BATNA, the greater your power." — Fisher & Ury, Getting to Yes, Ch.6
ZOPA · Deal Zone Your floor (your BATNA) Their floor (their BATNA) Your ask → ← Their ask Floors overlap → a deal zone exists; no overlap → talking is futile, go execute your BATNA
Situation: A core engineer comes to talk a raise, hinting "they're paying more outside." You want to keep them, but budget is tight.
✗ Just holding a position

"The company's comp system is what it is; nothing I can do." — You gave up your own BATNA (internal leveling, equity, project leadership) and never tested how hard their BATNA really is (a real offer or a bluff). They feel brushed off and leave a few weeks later.

✓ Read both BATNAs

"I really want to keep you, let's be straight. Cash I genuinely can't move much this year; but what I can move: tech lead on the next big project, pushing this leveling round through, an extra refresher grant. That offer outside — beyond the money, what does it solve for you that we don't?"

—Don't stonewall with "nothing I can do"; lay out the chips you can move, while probing what they truly want (the non-cash factors in their BATNA).

  • Before the table, have I written down my BATNA explicitly? (What exactly I'll do if it fails.)
  • Is my BATNA improvable? Did I spend effort making it stronger beforehand (a second offer, one more ally)?
  • Have I estimated their BATNA? Is walking away costly or cheap for them? That decides how long they can hold.
  • Is my reservation point set in advance, or does it drift with the emotion in the room?
  • Mistaking wanting for power. How much you need the deal is precisely your weakness. The more you need it, the more you quietly fortify your BATNA beforehand.
  • The bluffed fake BATNA. Invent a route out that doesn't exist, and the moment it's called ("go ahead then"), credibility and leverage collapse together.
  • Leaving the other side no exit. Corner them into "walking is better" and the deal is over — leave a space where "closing beats walking, just a bit."
Exercise: For a live negotiation, write your BATNA and reservation point in one sentence each. Then spend 10 minutes on: is there one action that would strengthen that route out before talks open?
Reflection: Last time I conceded, was it because the option was truly better, or because I wanted the deal too much and my BATNA was too weak?
PRINCIPLE 03

Multiparty Negotiation: The Winner Isn't the Strongest, It's the One Who Sequenced Right Coalitions and Sequencing

coalitionsequencingtalk privately first
Two-party negotiation is about strength; multiparty is about structure. In a game of three or more, who you talk to first, whom you ally with, and in what order you persuade often decides the outcome more than the proposal itself. Don't pull everyone into one big meeting to lay it all out — align one by one privately, build the winning coalition, then enter the formal room to "confirm" what's already agreed.
"In multiparty negotiations, the sequence in which you approach the other parties can be decisive. Build a winning coalition one conversation at a time before you ever enter the room." — James Sebenius, 3-D Negotiation (HBS)
Situation: You want to push a unified service framework across 4 teams. Some support it, some fear migration cost, and one influential staff engineer is undecided.
✗ All-in at the big meeting

You pull an 8-person meeting and drop the proposal: "Take a look — any objections?" — Opponents coalesce on the spot, and one "I have concerns" from the staff engineer tips the room toward wait-and-see. You're forced onto defense and the proposal stalls. Public settings are where positions are hardest to change.

✓ Sequence, build coalition

Step 1: meet the most likely supporter with weight first, get their backing.
Step 2: armed with "someone already supports this," meet the influential staff privately — hear the concerns first, reshape the proposal to catch them, turning the hardest vote to neutral.
Step 3: talk to the migration-cost-fearing teams one by one, with a transition plan.
Finally hold the formal meeting — most have privately nodded, so it's confirmation, not persuasion.

  • Have I counted the "real decision stakeholders" — including those with no formal veto but who set the tone?
  • Who are my natural allies (win first), key swing votes (focus here), hard opponents (last, or route around)?
  • Have I designed the sequence — who, once won, snowballs into helping me win the next?
  • Before the formal meeting, have I finished all the private talks, so the meeting only "confirms"?
  • Faith in "public debate reveals truth." In public, people defend positions for face; changes of mind almost all happen in private one-on-ones.
  • Sequencing on a whim. Going to the hardest person first lets them set the tone before you have allies, and everything after gets dragged their way.
  • Ignoring the hidden veto. The person off the decision list but able to quietly resist afterward — leave them out and the proposal passes but never lands.
Female Leader's Note The private coalition-building play is especially critical for women often excluded from informal networks (drinks, the "boys' club") — precisely because you may not get the information edge of those informal channels, you must do one-on-one pre-alignment deliberately and structurally, building the coalition in visible pre-meeting conversations rather than waiting on a dinner you may not be invited to.
Exercise: For the next cross-team decision you're pushing, draw a stakeholder map: mark ally / swing / opponent, and write your contact sequence (who first, who later, why).
Reflection: That cross-team proposal that stalled — was the proposal not good enough, or did I leave the persuasion for the one meeting least suited to persuading?
PRINCIPLE 04

Cross-Cultural Negotiation: Read the Half That Goes Unsaid Read What Isn't Said

high/low contextrelationship-firsttrust
The same "this is a bit difficult" might mean "let's find a way" on a US team and flatly "no" on a Japanese one. The biggest trap in cross-cultural negotiation isn't language — it's taking a "yes" at face value and missing a polite "no." First figure out, in the other culture, how trust is built, how dissent is expressed, and who makes the call — then talk substance.
"In low-context cultures, good communication is precise and explicit. In high-context cultures, communication is layered—much is communicated through context and left unsaid." — Erin Meyer, The Culture Map, Ch.1
Situation: You (low-context style) negotiate the scope of a joint project with a high-context, high-power-distance team, and they nod "no problem" throughout.
✗ Taking it literally

You: "Scope and deadline OK for everyone?" Them (in front of their boss): "OK, no problem." — You record it as a commitment in the notes. Two weeks later at delivery you find they thought it unrealistic all along, just couldn't push back in public, and now you're seen as "inconsiderate."

✓ Leave dissent a back door

"Calling it on the spot isn't easy. Don't answer now — go over it privately with your team, which parts feel tight, which need reordering, and send me directly tomorrow." Then follow up one-on-one: "In your experience, what's the least realistic piece in here?" — swapping the difficulty of "saying no in public" for the ease of "telling the truth in private."

  • Is the other culture high- or low-context? Should I listen literally, or read between the lines?
  • Do they "build relationship then do business" or "do business, relationship follows"? Have I left time to build relationship?
  • Is the real decision-maker at the table? Or do they have to go back and consult a level not present?
  • Do they express dissent directly or indirectly? Have I given them a private channel that doesn't require public pushback?
  • Treating your own comm habits as universal. You think "direct" is efficient; they may find it offensive. You think "indirect" is smooth; they may find it insincere.
  • Misreading the nod. In many cultures a nod means "I'm listening," not "I agree." Don't mistake courtesy for commitment.
  • Stereotype instead of observation. The Culture Map describes probabilistic tendencies, not labels for individuals — ultimately you still watch how this particular person reacts.
Exercise: Recall a recent cross-cultural/cross-team exchange where a remark you later realized you'd misread. Write the literal meaning vs. the real meaning, and how you could have probed to confirm.
Reflection: My quietest cross-cultural team member — do they really have no opinion, or have I not given them a channel that doesn't require public pushback?

Going Deeper

"Principled negotiation, win-win" sounds ideal — but what if the other side just wants to steamroll you zero-sum and won't reason?
This is exactly where Getting to Yes was criticized as "naive," and the authors answered it in the sequel Getting Past No: win-win is the default strategy, not an unconditional faith. When they steamroll, your guardrail is BATNA — a route out strong enough that you needn't accept a bad deal. The move: don't get dragged into a position war; reframe their attack as a problem to solve ("you're holding hard on this — what are you worried about?"), while making clear your ability to walk. Win-win is the hand you extend; a strong BATNA is the card up your sleeve. You need both.
Can internal negotiation (colleagues, reports) and external (vendors, candidates) use the same playbook?
Same framework, different weights; the core difference is "will this relationship still exist tomorrow." External one-shot deals let you press BATNA harder and squeeze the deal zone; internally the other side is your peer next week, so winning the round and losing the relationship is a net loss — "soft on the person" doubles in weight, and you actively help them save face before their team, or they can't explain it back home and will quietly resist. Internally the win isn't "I got the most," it's "the plan lands and this person still wants to work with me next time."
Aligning one-on-one and sequencing moves — where's the line between this and "playing politics, going behind backs"?
The line is whether what you say privately and publicly is the same thing. Playing politics is one face in person, another behind their back, manipulating via information gaps; pre-alignment is giving each stakeholder time to digest and comment on what you'll say in the public meeting — same content, just space to not have to declare in public. In a healthy org, major decisions should almost never make their first appearance ambushed at a big meeting. A self-check: would I be embarrassed if what I told A privately were overheard by B? If yes, you crossed the line.
BATNA stresses "the ability to walk," but inside a big company you often can't walk. How do you negotiate with a weak internal BATNA?
This is a real constraint for big-company leaders: many internal negotiations have no credible "walk" option. Shift leverage from "exit" to other currencies — the non-scarce resources you can give (future collaboration, endorsement, priority swaps), the objective standards you can appeal to (policy, precedent, data), and time (I'm not in a hurry, you are). Another route: place the single negotiation inside a long-run game — "I help you this time, noted" is itself a slow-motion BATNA. Don't pretend you can walk (you'll be seen through); trade it for "we still have many collaborations ahead" — the steadiest chip in a weak-exit scenario.