From Positions to Interests
One of the most important ideas in this entire book is the difference between a position and an interest.
A position is a specific demand — it answers the question "What do I want?" An employee might say, "I want a 15% raise." A customer might insist, "I need delivery within five days." A tenant might say, "I want lower rent." Positions are concrete, visible, and usually the very first thing stated in a negotiation.
An interest is the reason behind that position — it answers the question "Why do I want this?" The employee asking for a raise might really be seeking financial security, recognition for their work, or a clearer path toward career growth. The customer demanding faster delivery might be trying to meet their own client's deadline. The tenant asking for lower rent might be dealing with real financial uncertainty during a difficult stretch.
Once you understand the interest behind a position, whole new categories of solutions appear. The employee who first demanded a raise might be equally satisfied by a performance bonus, more professional development, flexible working hours, or a scheduled salary review in six months. A landlord who genuinely can't lower the rent might instead offer a delayed payment schedule, a temporary adjustment, or property improvements that add long-term value for the tenant. This shift — from a rigid demand to a flexible conversation about underlying needs — turns negotiation from a contest into a shared search for solutions.
Example: The Salary Negotiation. Position: "I want a 15% raise." Possible interests underneath that: financial security, feeling recognized for contributions, wanting to advance in your career, or wanting a stronger reason to stay with the company long-term. Once those interests are on the table, a much wider set of solutions becomes possible: a performance-based bonus, funded professional development, flexible working arrangements, expanded responsibilities, or a formal salary review tied to agreed performance goals. Instead of a single yes-or-no answer, both sides can build a package that actually satisfies the real need.