The Mistake of Meeting an Unreasonable Demand Halfway

Explains why splitting the difference with an outrageous request often leads to worse outcomes than holding a firm boundary.

A client brings you a scene that still has them rattled. A senior manager, two days from launch, asked for a full reporting dashboard that was never scoped. A buyer demanded half off a price that was already fair. A colleague tried to hand over half their project the night before it was due. In each case the client did the thing that felt reasonable in the moment. They offered to meet the demand partway. They came to you because the partway offer left them resentful and somehow worse off, and they cannot work out why. The clinical move is to show them that the compromise was not a compromise at all.

The instinct to split the difference reads as collaboration. It feels like de-escalation. Your client experiences it as the mature, generous option. What they have not seen is that the other person already moved the center of the conversation before a word was negotiated. The extreme demand did that work. By the time your client offers their reasonable middle, they are bargaining from a position someone else drew for them.

What the halfway move is actually doing

The mechanism is an anchor. The person making the demand sets an extreme number, and the extremity is the point. When a buyer asks for fifty percent off, or a colleague asks for half the workload the day before delivery, they are not opening a good-faith negotiation. They are redrawing the field.

Their extreme figure becomes the new hundred. Your client’s actual price, the actual scope of their role, now looks like a stubborn zero. Inside that skewed frame, landing at fifty feels fair. It is not fair. Your client has agreed to a twenty-five percent discount they never meant to offer, or to a weekend of unpaid work that was never theirs. Relief arrives first. Resentment follows, because some part of the client knows the math was rigged.

The pattern does not run in a vacuum. It lives in systems, companies, teams, families, where boundaries are soft and pushing gets rewarded. If a person has learned that the loudest voice secures the resources, or that an absurd opening bid reliably nets more than a modest one, they keep doing it. The system trained them. Every time someone meets them halfway, the system confirms that the move works.

This is the part most clients miss. Their compromise is not just a personal loss. It is a tuition payment that teaches the other party to come back harder next time.

The four moves your client has already tried

When the demand lands and your client is caught off guard, the mind reaches for the responses that feel logical. Each one tends to make things worse. Your client has usually run through several of these before the session, which is useful, because you can name the pattern instead of inventing it.

The compromise. Your client offers to do part of the unreasonable thing. “We can’t build the whole dashboard, but what if we do the two main sales widgets.” This validates the premise. Your client has just conceded that the sanctioned plan was insufficient and that their team’s capacity is flexible after all. The lesson the other side takes away is that an extreme demand is a winning opening move.

The appeal to logic. Your client points back to a prior agreement or to plain reality. “The project plan we all signed off in January doesn’t include a dashboard.” The person making the demand is rarely running on logic. They are running on pressure, on their own failure to plan, on a sense of entitlement. A well-reasoned argument bounces off the immediate want.

The delay. Your client buys time and hopes the problem shrinks. “Let me take that away and circle back with the team.” Now your client owns the burden of solving the other person’s unreasonable problem. They will spend their team’s hours trying to bend reality to fit the demand, only to deliver a no later, which lands as more personal than an honest no would have.

The explanation. Your client lays out in detail why the thing is impossible. “We’d have to pull the lead engineer off the security audit, and the API isn’t ready, which means…” This reads as a list of excuses. To the person making the demand, those constraints are not legitimate. They are obstacles your client should be willing to clear for them. The explanation invites them to start problem-solving every item on the list.

The position to coach the client toward

The move that holds is to stop negotiating on the other person’s terms. Your client ignores the anchor and re-anchors the conversation to reality.

This is not about your client becoming rigid or oppositional or barking no. It is about making the objective constraints, time, budget, resources, the firm third party in the room. Reality does the refusing here, and the client gets to stand beside it. Your client’s job is to be the calm, clear-eyed messenger of that reality, which is a job they can do without bracing for a fight.

The position works because it declines the other person’s distorted frame. Your client is no longer meeting them halfway on a map drawn in crayon. They are setting the real, topographical map back on the table where everyone can see it. The conversation turns from a contest of wills, the client’s no against the other’s yes, into a shared orientation to the facts. The consequences of the unsustainable request return to the person who made it.

Coaching this is partly a job of giving the client permission. Many of them treat the refusal as a personal stance they have to defend, which is exhausting and feels aggressive. When they grasp that the constraints are doing the refusing, the whole interaction gets lighter. They stop guarding a boundary and start describing a situation.

Language that fits the new position

Give your client these as illustrations to hear the shape from, rather than lines to recite. The tone underneath all of them is calm, firm, and free of apology.

State the constraint as a neutral fact. “That’s a big piece of work. With two days left before launch, the current plan is what the team can deliver well.” This frames capacity and timeline as fixed. The refusal is not about your client’s willingness. It is about the physics of the situation.

Reframe the choice around trade-offs. “To add that, we’d have to drop the final security testing and the integration QA. Are you comfortable telling leadership we launched without those?” This makes the cost of the demand concrete and hands the decision back. The question moves from a vague can we do this to an explicit are you willing to own this risk.

Say the quiet part out loud, slowly. “So the ask is to add a major new feature we haven’t scoped or tested, and ship it inside forty-eight hours. I want to make sure I’ve got that right.” An unreasonable demand repeated slowly and without heat tends to expose its own absurdity. The other person has to hear what they are actually requesting, stripped of the pressure they were applying.

Separate the idea from the timing. “A reporting dashboard is a strong idea. It’s too important to rush and get wrong. Let’s book time next week to scope it properly for the next release.” Your client is splitting a possibly good idea from an impossible deadline. They show they were listening and they value the contribution, while holding the boundary around doing the work well.

What to listen for in the next session

Find out where the anchor settled. When your client reports back, the first question is whether they re-anchored to reality or quietly drifted toward the other person’s number. A client who says “I told them the timeline was fixed” held the position. A client who says “we agreed I’d do just the two widgets” picked the rope back up at some point in the hour.

Listen for the resentment reading. If the partway move was the old pattern, the somatic receipt was resentment after the fact. A client who comes back lighter, even if the other person grumbled, usually held the frame. A client who comes back aggrieved and overloaded usually capitulated and is now living the cost.

Watch for the client’s report that holding the line “made things tense.” That judgment is worth examining with them. Tension in the moment is often the sound of an anchor failing to land, which is the intervention working. The work is to help your client tell the difference between a relationship rupturing and a manipulation losing its grip.

When halfway is the right move

Sometimes the demand carries no manipulation at all. It is a genuine request from someone with real authority and a real reason, and the constraints your client is clinging to are softer than they think. The tell is whether the other person keeps pointing, steadily, at a concrete need rather than escalating pressure. A manipulator pushes harder when met with reality. A legitimate stakeholder engages with the trade-offs your client lays out. If your client is using the anti-anchoring frame to avoid a reasonable accommodation, you are now coaching rigidity, and that is its own problem.

And some clients cannot hold the line for reasons that sit deeper than tactics. The inability to disappoint a senior figure, the conviction that any no ends the relationship, the dread of being seen as not a team player, these run below the conference-room scene and will not yield to a better script. That client will agree with you in session and capitulate again on Monday. When the halfway move keeps repeating across unrelated situations, the conversation is no longer about anchoring. It is about what the client believes will happen to them if they take up space, and that belief is the work.

Continue reading with a Rapport7 membership

Get full access to 1,500+ clinical guides, directives, audiobooks, and weekly case supervision.

View Membership Options