Adapting Negotiation Proposals to Priorities

Hello. In the previous lesson, you treated a negotiation as a choice between an agreement and each side’s realistic fallback, or BATNA. That remains your safety rail: a creative proposal is useful only if it leaves you better off than no deal.

This lesson adds the move that turns bargaining into joint problem-solving: revise the proposal after discovering what the other person actually values. By the end, you will be able to listen past a stated demand, identify priorities and constraints, and reshape a proposal during a short role-play without giving away what matters most to you.

---

From stated positions to usable information

A position is the outcome someone announces:

• “We need it by April 30.”
• “I cannot go below this price.”
• “I need to work remotely.”
• “I want the whole orange.”

An interest is the reason beneath that position: a deadline imposed by someone else, a need for predictability, a concern about quality, a desire to avoid risk, or a wish to preserve autonomy.

This difference is not semantic. If you negotiate only positions, your options often look artificially narrow. You either give in, insist, or split the difference. When you learn interests, you may discover that several terms can change together: timing, scope, payment, responsibility, quality guarantees, visibility, or flexibility.

Consider two colleagues:

• Priya says: “The team needs the complete customer-support automation live by April 30.”
• Marco replies: “My platform team cannot deliver that before mid-June.”

A positional compromise might be “May 20.” But that date may satisfy neither person. What if Priya needs only a credible demonstration for a board meeting on April 30, while Marco’s real concern is not the calendar but protecting a reliability release in May? The negotiation now has more variables than a single date.

A revised proposal could offer a limited demonstration on time, while moving the full production launch later. That is not simply being nice. It is a trade based on different priorities.

The orange example is deliberately simple, but its logic transfers. A client who asks for a discount may chiefly need cash-flow flexibility. A manager who rejects remote work may be worried about team coordination rather than location itself. A roommate who insists on a strict cleaning schedule may want predictability and a fair distribution of effort.

Do not assume that every disagreement has a hidden win-win solution. Sometimes the issue really is a fixed amount of money, time, or scarce capacity. Even then, understanding interests tells you why a term is difficult and which adjacent terms may be negotiable.

---

Ask, listen, summarize, then revise

Interests are usually not volunteered in a first demand. People may fear that revealing priorities weakens their position, or they may not yet have articulated those priorities clearly themselves. Your task is not to interrogate them or “find the weakness.” It is to establish enough shared information to design a better package.

A reliable conversational pattern has five parts:

1. Acknowledge the stated position.
   This signals that you heard it, even if you cannot accept it.
   “I understand that April 30 is important to you.”

2. Invite explanation with a neutral, open question.
   “What needs to be true by April 30?”
   “How would a delay affect your team?”
   “Which part of the request is most important?”

3. Probe for operational detail.
   If someone says, “We need flexibility,” ask what flexibility means in practice: schedule changes, cancellation terms, payment timing, scope, or decision rights.

4. Summarize your current understanding.
   “It sounds as if the board demonstration is non-negotiable, but a full production launch is not required that day. Have I got that right?”

5. Offer a conditional revision, not an unconditional concession.
   “If we narrow the April deliverable to the two critical workflows and your team provides acceptance criteria, we could prepare a staged demonstration by then and target production in June.”

The summary is a small but important move. It lets the other person correct your interpretation before you build a proposal on it. It also demonstrates active listening, which makes further disclosure safer.

A useful distinction:

Move	Purpose	Example
Open question	Discover what matters	“What would make this arrangement workable for you?”
Information probe	Turn vague language into specifics	“When you say ‘more time,’ what timeline would help?”
Summary probe	Check your understanding	“So certainty matters more than speed, correct?”
Clearinghouse probe	Surface omitted concerns	“What else would we need to address?”
Conditional proposal	Trade one valued item for another	“If we can extend payment terms, could you commit to a longer contract?”

Avoid a common failure mode: asking a question, hearing an answer, and immediately returning to the proposal you prepared beforehand. If the answer does not change what you propose, the other person reasonably concludes that you were merely performing “listening.”

---

Revise the package, not just one number

A revised proposal should respond to the information you learned. It does not mean accepting the other person’s first priority at any cost. It means looking for terms that are inexpensive for one side and valuable for the other.

Think in terms of a package. In everyday negotiations, possible issues often include:

• scope or quantity;
• timing and sequencing;
• price, budget, or payment timing;
• quality level, risk, or guarantee;
• who performs which work;
• review points and decision rights;
• duration, flexibility, or renewal;
• visibility, credit, or recognition.

The key question is:

Which differences in priorities can become an exchange?

Suppose a freelancer initially offers a client a three-month analytics project for a fixed fee, with a final report at the end. In conversation, the freelancer learns that the client’s highest priority is an investor update in four weeks, while the freelancer’s priority is avoiding last-minute scope expansion.

A weak revision is simply, “Fine, I will finish everything in four weeks.”

A better revision changes several terms:

“If the investor update is the priority, I can deliver a focused dashboard and briefing in four weeks. We would then complete the broader analysis over the following eight weeks. To make that feasible, we would need a named decision-maker, weekly feedback within two business days, and a written list of the metrics for the investor update.”

The client gains early visibility. The freelancer gains scope protection, timely decisions, and a manageable delivery plan. Neither side has abandoned its interests.

Use “what if” proposals as tests

A proposal can be a test, rather than a final commitment. This is especially valuable when you still have uncertainty about the other person’s ranking of priorities.

For example:

“Would you prefer a smaller discount with delivery next week, or a larger discount with delivery at the end of the month?”

The response supplies information. If delivery next week matters far more than the discount, you have learned something important. You can then revise again.

Where feasible, present two packages that are both acceptable to you but vary along different issues. This prevents the conversation from becoming a simple yes-or-no response to your single preferred deal.

Tentative package	What it tests
Earlier delivery, reduced scope, standard price	Whether timing matters more than completeness
Full scope, later delivery, discounted price	Whether completeness or budget matters more
Early pilot, later full rollout, shared testing responsibility	Whether proof of progress matters more than immediate full implementation

Be explicit that you are exploring:

“I am not treating either of these as a final offer. I am trying to understand which trade-off would work best on your side.”

That phrasing reduces the risk that an exploratory idea is mistaken for a concession that cannot later be revised.

---

Role-play lab: revise after the hidden priorities emerge

Set aside about 15 minutes for this simulation. Use a partner if possible. If you are working alone, play the Platform Lead first; after making your opening response, reveal the Product Lead’s private information and continue the dialogue aloud.

Shared situation

A company wants to automate six repetitive customer-support workflows. The Product Lead asks the Platform Lead to have all six workflows live by April 30. The Platform Lead’s initial proposal is to deliver the complete project by June 15.

Both sides want the project to succeed. The disagreement concerns the design of the agreement, not whether automation is useful.

Platform Lead: your private priorities

Keep these priorities in view throughout the conversation:

1. Your team is responsible for a reliability release on May 10. A rushed full production launch before that date is unsafe.
2. Your team cannot take responsibility for defining business rules or performing acceptance testing.
3. A security review is required before anything reaches production.
4. You would prefer a clear, limited commitment over an ambiguous “we will do our best” deadline.
5. Your fallback is to keep the work in the existing June roadmap. Do not accept a deal that damages the May release merely to avoid disagreement.

Product Lead: information to disclose only after questions

If you have a partner, give them this card privately. If you are solo, uncover it only after you have asked at least two questions.

• The April 30 date comes from a board meeting.
• The board needs a credible demonstration, not necessarily a full live rollout.
• A staging demonstration of the two highest-volume workflows would satisfy the immediate need.
• Product can assign an operations analyst one day per week to specify business rules and conduct acceptance testing.
• Product has up to $8,000 for temporary quality-assurance support.
• Full production capability is preferred by June 30, but the exact date is less important than a reliable demonstration in April.

Run the conversation

First, make the initial positional exchange.
The Product Lead requests full live delivery by April 30. The Platform Lead explains that full delivery is proposed for June 15.

Next, pause before countering.
The Platform Lead uses open and probing questions, such as:

• “What will the board need to see on April 30?”
• “How much of the workflow needs to be live versus demonstrated?”
• “Which risks would matter most if we accelerated?”
• “What support could Product provide during testing?”

Then, state a summary before redesigning the deal.
A strong summary might sound like:

“I am hearing that the April date is about demonstrating visible progress, while a stable production rollout can occur later. You can provide business-rule expertise and some testing support. Is that accurate?”

Only after the Product Lead confirms or corrects that summary should the Platform Lead revise the proposal.

Draft two revised packages

Aim to change at least two issues, not merely the date.

Package	April 30 commitment	Full rollout	Conditions and trade-offs
A: staged demonstration	Staging demonstration of the two highest-volume workflows	June 15	Product analyst defines rules and accepts the workflows; temporary QA support is funded by Product; security review occurs before production
B: narrow live pilot	One low-risk workflow live, plus a demonstration of the second	June 30	Strictly limited scope; manual fallback remains available; Product supplies weekly decisions and testing support

Neither package is automatically “correct.” Their purpose is to test preferences. If the Product Lead chooses Package A, the April board demonstration is likely the dominant interest. If they favor Package B, a small amount of live functionality may carry special symbolic or operational value.

Finally, make one more revision based on the response. For example, if the Product Lead says, “A live pilot is essential, but we do not care about the second workflow in April,” you might revise to:

“Then let us commit to one low-risk live pilot by April 30, provided the Product analyst owns acceptance decisions within two business days. We will demonstrate the second workflow in staging and schedule the remaining five for completion by June 30 after the reliability release.”

What success looks like

After the role-play, check whether your revised proposal did all four things:

• reflected a priority that was newly revealed;
• protected at least one of your own important interests;
• linked concessions to clear conditions or reciprocal contributions;
• was presented as a specific package, with responsibilities and timing, rather than a vague promise.

Notice the strategic shift. You did not “win” by pushing the other person into your original June 15 proposal. Nor did you automatically concede April 30. You used information to alter the structure of the deal.

---

Ethical boundaries: curiosity is not extraction

Interest-based negotiation works only when there is enough trust for people to share useful information. That makes your conduct part of the strategy.

Be transparent about your purpose:

“I am trying to understand what matters most so that I can see whether there is a workable structure for both teams.”

Do not pretend to explore options if you have already decided there is no flexibility. Do not pressure someone into revealing confidential information. And do not use a disclosed personal constraint as an excuse to impose an unfair deal.

You also do not need to reveal every private limit. It is usually safe and useful to share categories of interest:

• “Reliability is important to us.”
• “We need predictable timing.”
• “We have limited capacity before the release.”

You need not disclose your exact internal budget ceiling, private walk-away threshold, or every alternative available to you.

Integrative bargaining is not surrender. Your BATNA and walk-away threshold remain private guardrails. Shared interests are the raw material for designing a deal that both sides can rationally choose.

---

Key takeaways

A demand is not yet a complete negotiation problem. Separate the position someone states from the interests, priorities, and constraints that explain it.

To revise well during a negotiation:

• ask neutral, open questions and probe vague answers;
• summarize your understanding before making a new proposal;
• look beyond one disputed term and add issues such as scope, timing, responsibility, risk, or payment;
• make conditional “what if” packages that test trade-offs;
• revise in response to the information learned while preserving your own important interests and BATNA.

In the final lesson, you will take this strategic approach into everyday life: designing a small, ethical experiment, predicting another person’s response, and comparing that prediction with what actually happens.