Reflection — An Honest Take 8 min

Honest Take — Before You Begin

Honest Take — Module 1: Principled Negotiation — BATNA, ZOPA, Anchoring, Reservation Price #

The thing nobody tells you about negotiation vocabulary is that the words themselves are the first technology that changes you. Before you know the term BATNA, walking away is a vague mood — a thing you do when something feels wrong, narrated afterwards as "I just wasn't excited about it." After you know the term, walking away is a parameter. It has a value: a number, a specific alternative offer, a specific prospect already in pipeline. The value either exists or it doesn't, and if it doesn't, you cannot honestly walk, which means you cannot honestly negotiate, because the entire structure of negotiation rests on credible alternatives. The vocabulary doesn't give you new abilities; it gives you the ability to see what was already there. That is the whole module. The rest is examples.

Here is what you'll feel reading Getting to Yes: mildly underwhelmed. The book is over forty years old, the principled-negotiation framing is now table-stakes in business writing, and most of the ideas you'll recognize from osmosis. That recognition is the trap. You have absorbed the words at low resolution; you have not used them operationally. There is a vast gap between knowing what BATNA stands for and writing down, in a dated document the night before a real conversation, the specific number-or-alternative that is your BATNA for that specific deal. Almost no engineer does the second. And when you finally do it, expect a specific discovery: what you'd been calling your BATNA — "I'd just find another client," "I'd just keep interviewing" — was a comforting story, not an alternative. You don't have a concrete alternative; you have an abstract sense that one would materialize. Those are different things, and the other side of the table can read the difference. Once it's on paper, you either build a real BATNA — start two other conversations before the one that matters — or you accept that you don't have one and adjust your expectations honestly. Either way, the writing is what made the difference.

The most underrated material in this module is the anchoring research — Bazerman and Neale, and the Kahneman chapter. The data is genuinely staggering: first numbers shift outcomes by 30-50% even when the anchor is obviously absurd, even when the negotiator knows about anchoring, even when the anchor comes from a literal random wheel spun in front of the participant. This is one of the most replicated findings in cognitive psychology. The implication: the recruiter asking "what's your current salary?" is anchoring you to your current salary. Knowing about the bias reduces the effect by maybe a fifth. It does not eliminate it. The only reliable defense is to refuse to receive the anchor — deflect the question, or counter-anchor immediately with your own researched number. Knowing the bias does not protect you; refusing to be the second mover protects you. That distinction is worth re-reading until it sits.

Interests-versus-positions deserves its own paragraph, because it is the one principle you already practice professionally without knowing it. When a stakeholder asks for feature X and you surface the underlying problem before committing to a solution — because what they need is the outcome X was supposed to produce, not X — you are running Fisher and Ury's second principle. You've been doing it in product conversations for years. This module asks you to run the identical move in commercial conversations, where it is harder only because the stakes feel personal: "what's driving the budget number?" is the same question as "what's driving the feature request?", asked with a tighter throat. The same goes for objective criteria — when two engineers disagree about a pattern, the defusing move is an appeal to a shared external authority, and citing market-rate data in a salary conversation is the same move with money attached.

Two more things before the checkpoint. First, Getting Past No — the smaller, less famous Ury book — is not optional if you deal with counterparts who won't engage in good faith: procurement gauntlets, exploding offers, hardball clients. Getting to Yes assumes a counterpart willing to join the principled frame; Ury's breakthrough sequence is the operating manual for when they won't. Second, a reframe many engineers need, especially those raised in cultures that read persistence and gratitude as virtues and walking as ego: walking away is not a tantrum and not a moral failure. It is the act of having a credible alternative and using it when the deal in front of you is worse. The counterparty will not read your walk as entitlement — they will read it as a signal that you have options, which is the most attractive signal a candidate or consultant can send. If you cannot walk, you cannot negotiate. You can only accept.

The Live-Stakes Track makes all of this concrete, and I want to underline the exercise rather than let it slide past as a checkpoint item: take three real upcoming conversations — an offer window, a renewal, a pricing call — and write BATNA, estimated ZOPA, your anchor, and your reservation price for each. On a page, dated, numbers visible. Not in your head, not "I'll figure it out on the call." Under the body chemistry of a live conversation, the four numbers in your head will dissolve and you will revert to the default behavior Module 0 diagnosed. The numbers on the page do not dissolve. You read them before the call; you anchor to your written numbers instead of to whatever the other side says first. The page is a prosthesis for the part of your brain that has historically failed you under pressure. Use the prosthesis without shame.

Conclusion #

Module 1 is where you stop negotiating with vibes and start negotiating with parameters. The vocabulary is not jargon — it is the load-bearing structure of every module that follows. If BATNA, ZOPA, anchor, and reservation price are not concrete written values for your next three real conversations by the end of this module, you have read the words without using them, and the curriculum will skate on the surface of your behavior the way the books on your shelf already have.

Predictions #

  • The first time you write your BATNA on paper for a real conversation, you will discover you don't actually have one. The discomfort of that discovery is the lesson, and the action item is build one, not fake one.
  • Getting to Yes will underwhelm you for the first hundred pages. Around the objective-criteria chapter something will click and you'll re-read the first hundred. The re-read is where the book lands.
  • The anchoring research will reframe at least one past negotiation in a way that mildly horrifies you — you'll see the exact moment you accepted the other side's frame without noticing. That recognition is protective immunity forming.
  • You will overestimate ZOPA on at least one of your three worksheets, because optimistic ZOPA is psychologically more comfortable. Have someone else sanity-check your numbers before you rely on them.
  • You'll over-deploy "what's your real interest here?" in the first week, in conversations where it sounds therapeutic and out of place. By week three you'll have learned to use the move without naming it.
  • The vocabulary will leak into non-work conversations within a month — you'll catch yourself estimating someone's BATNA in a context that isn't a negotiation at all. The leakage is the sign the vocabulary has become operational.
  • You will under-invest in the set-up half of negotiation — who's at the table, in what sequence, against what no-deal options — because it sounds dry next to tactics. It is the half most engineers ignore, and it decides more outcomes than the tactics do.