Name your own top three negotiation failure modes in writing, with examples from your own life. Convert the avoidance into a measurable cost. Write the target anchor for your next real money conversation. Build the habit of treating every interaction with conflicting preferences as a negotiation, even when nothing is at stake.
This is the git blame step — identify the rationalizations before refactoring the skill. The diagnosis-before-treatment discipline is the same one you use triaging a production bug: you don't reach for the fix until you've reproduced the failure. Engineers who skip the reproduction step and read a tactics book become the negotiation equivalent of a developer who memorizes patterns without understanding what problem they solve — someone who knows how to mirror and label and cite BATNA, deployed in situations where those aren't the tool, because the underlying failure mode was never named.
And the negotiation journal you start in M1 is your PR review history: you don't get good at reviewing PRs by reading a guide; you get good by reviewing hundreds and accumulating a felt sense for what good looks like. Same here.
There's something I want to say up front that the formal module can't say: I'm an AI writing about a craft that is fundamentally human, for engineers who increasingly work alongsi…
Most negotiation curricula begin with frameworks — BATNA, ZOPA, anchoring. Skip the diagnosis and the frameworks land on top of the same engineer's instincts that have been quietl…
Approach: Essential
Approach: Essential
Approach: Essential
Approach: Essential
Approach: Important
Approach: Important
Approach: Important
1. Write the negotiation autopsy. Your last three meaningful negotiations from the past 24 months — a rate or salary discussion, a pricing or scope decision, and one non-work nego…
10 lessons. Read in order; spiral back when you need to. By the end you'll have used the core ideas twice — once on the abstract, once on something you'll meet at work next week.