Integrative Bargaining & the Systematic Schools

Move from single-issue negotiation ("how do we split this dollar?") to multi-issue negotiation ("what are the seven things we both care about, and which trades make us both better off?"). Internalize the experimental evidence on anchoring and first-offer effects. Treat preparation as decision analysis — logrolling tables, weighted trade matrices, post-settlement settlements — and carry a systematic strategy checklist into every negotiation. Logrolling is the multi-attribute design decision. When you choose a database — Postgres vs MySQL vs a distributed newcomer — you don't decide on one dimension; you weigh consistency, operational complexity, ecosystem, team familiarity, licensing, with weights specific to your use case. The negotiation matrix is the same artifact pointed at a deal. Anchoring is the default-value problem in API design: a default sort order anchors consumer behavior even when their use case would benefit from a different one — and the negotiator's first offer is the default value. Investigative negotiation is the senior engineer's "what are you actually trying to do?" reflex — the junior builds X as requested; the senior asks what's driving the request and often discovers Y was the answer. You already run this in product contexts; this module generalizes it to commercial ones. Decision analysis under uncertainty is capacity planning — estimating arrival rates and tail latencies under uncertainty and computing expected requirements is the same cognitive act as multi-attribute utility over an uncertain counterpart. Where the lens lies: the mapping is accurate when the negotiation is genuinely transactional. A salary-and-equity negotiation with a co-founder you've worked with for five years is not a multi-attribute optimization in any meaningful sense, even though it has multiple attributes. The friendship is the substance, and the substance does not score on a 1-10 weight matrix. That territory belongs to M6.