The Mistake of Meeting an Unreasonable Demand Halfway

The request lands on the conference table with a soft thud, but it feels like a physical blow. You’re in the final project review, two days from launch, and a senior manager has just said, “This is all looking great, but we really need to add a full reporting dashboard before it goes live.” The air in the room thins. Your team, already running on fumes, looks at you. Your mind races past the obvious impossibility of the request to the political calculation. This person has influence. You don’t want to be seen as “not a team player” or “making excuses.” Your first instinct, the one that feels like de-escalation, is to find a compromise. You open your mouth to say, “Okay, a full dashboard isn’t possible, but maybe we can build out two or three of the key reports…” Stop. This is the mistake.

That impulse to compromise, to meet them in the middle, feels reasonable. It feels collaborative. But it’s a trap. The problem isn’t your willingness to negotiate; it’s that the other person has just warped reality. By making an outrageous demand, they have single-handedly moved the centre of the conversation. Your “halfway” point isn’t a compromise; it’s a capitulation to their distorted starting position. You’ve already given up a huge amount of ground before you’ve said a single word.

What’s Actually Going On Here

This dynamic works by exploiting our natural desire for fairness. The person making the unreasonable request sets an extreme anchor, and they know it. When a client demands a 50% discount on an already fair price, or a colleague asks you to take on half of their project the day before it’s due, they are not starting a good-faith negotiation. They are reframing the entire field of play.

Their extreme number becomes the new “100.” Your perfectly reasonable boundary, the actual price, the actual scope of your job, now looks like a stubborn “0.” In that skewed context, meeting them at “50” feels like a fair deal. But you’re not splitting the difference. You’re agreeing to a 25% discount you never intended to offer, or you’re signing up for a weekend of unpaid work that has nothing to do with your own responsibilities. You feel a brief sense of relief for having resolved the conflict, but that feeling soon sours into resentment.

This pattern doesn’t happen in a vacuum. It thrives in systems, companies, teams, even families, where boundaries are blurry and people are rewarded, implicitly or explicitly, for pushing. If the person making the demand has learned that the only way to get resources is to scream the loudest, or that making an absurd opening bid always results in them getting more than they would have otherwise, they will keep doing it. The system has trained them. And every time someone “meets them halfway,” the system teaches them that the strategy works.

What People Usually Try (and Why It Backfires)

When you’re caught off guard, your brain defaults to a few common, logical-seeming responses. They almost always make the situation worse.

• The Compromise: You offer 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 backfires because you have just validated their premise. You’ve agreed that the original, sanctioned plan was insufficient and that your team’s capacity is, in fact, flexible. You’ve taught them that an extreme demand is a successful opening move.

• The Appeal to Logic: You refer back to a prior agreement or objective reality.

  “But the project plan we all agreed to in January doesn’t include a dashboard.” This backfires because the person making the demand is rarely operating on logic. They are operating on perceived pressure, a lack of planning on their part, or a sense of entitlement. Your well-reasoned argument will bounce right off their immediate need.

• The Delaying Tactic: You buy yourself time, hoping the problem will shrink.

  “Let me take that away and circle back with the team to see what’s feasible.” This backfires because you’ve accepted the burden of solving their unreasonable problem. You are now responsible for spending your team’s valuable time and energy trying to contort reality to fit their demand, only to deliver a “no” later, which feels even more personal.

• The Explanation: You give a detailed account of why it’s impossible.

  “Well, to do that we’d need to pull the lead engineer off the final security audit, and the API for the data isn’t even ready, which would mean…” This backfires because it sounds like a list of excuses. To the person making the demand, these aren’t legitimate constraints; they’re just obstacles you should be willing to overcome for them. You’ve invited them to start problem-solving every item on your list.

The Move That Actually Works

The most effective move is not to negotiate on their terms. It’s to ignore their anchor and re-anchor the conversation to reality.

This isn’t about becoming rigid, oppositional, or yelling “No.” It’s about holding your ground and making the objective constraints, time, budget, and resources, the firm, immovable third party in the conversation. You are not the one saying no; reality is. Your job is to be the calm, clear-eyed messenger of that reality.

This works because it refuses to accept the other person’s distorted frame. You are not meeting them halfway on a map they drew in crayon. You are putting the real, topographical map back on the table for everyone to see. The conversation shifts from a battle of wills (your “no” against their “yes”) to a shared orientation to the facts. This puts the burden of dealing with the consequences back where it belongs: on the person making the unsustainable request.

What This Sounds Like

These are not scripts, but illustrations of how to re-anchor a conversation in reality. The tone is calm, firm, and non-apologetic.

• 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 successfully.” Why it works: This frames the team’s capacity and the timeline as fixed, non-negotiable facts. It’s not about your willingness; it’s about the physics of the situation.

• Reframe the choice around trade-offs.

  “To add that, we’d have to remove the final security testing and the integration QA. Are you comfortable telling the leadership team we’re launching without those?” Why it works: This makes the consequences of their demand clear and tangible. It moves from a vague “can we do this?” to an explicit “are you willing to accept this risk?” and puts the decision back on them.

• Say the quiet part out loud, calmly.

  “So I hear you. The request is to add a major new feature, which we haven’t scoped or tested, and deliver it in the next 48 hours. I just want to make sure I’m understanding the ask.” Why it works: When you repeat an unreasonable demand slowly and without emotion, it often reveals its own absurdity. It forces the person to hear what they are actually asking for, separate from the pressure they are trying to apply.

• Validate the idea, not the timing.

  “A reporting dashboard is a great idea. It’s too important to rush and risk getting it wrong. Let’s put time on the calendar for next week to scope it out properly for the next release cycle.” Why it works: You are separating their idea (which might be good) from their timing (which is impossible). You show you are listening and that you value their contribution, but you hold the professional boundary around doing the work well.