The meeting I'm about to run is going to be a fight.

What to do when the meeting you are about to run is going to be a fight

Silicon Valley. Early two-thousands. Ben Horowitz is running Opsware, the company that came out of the wreckage of Loudcloud, and Opsware's survival depends on a single contract.

The contract is with eds, the enterprise services giant, and it's worth twenty million dollars a year. The renewal is up. The eds executive making the renewal decision does not like Opsware's product. He has not liked it for some time. The product has improved. His view has not.

Horowitz's team go looking for what does work for him.

What surfaces is small and surprising. The eds executive has a personal attachment — long-running, almost sentimental — to an old inventory-management product called Tangram. Tangram is a tool he used early in his career. It is not, by most measures, a strategic technology. It is just a thing he likes.

Opsware doesn't own Tangram. The company that owns it is for sale. The price is ten million dollars.

Horowitz buys the company.

Then he gives the Tangram software to the eds executive, free, unasked. Not as part of the contract negotiation. Before the contract negotiation. As a thing that has happened, that the executive now possesses, with no expected reciprocation.

The renewal goes through.

Horowitz writes about this years later in The Hard Thing About Hard Things, and he writes about it with the awareness that it is one of the more expensive ways to win a meeting on record. Ten million dollars to set up a twenty-million-dollar conversation. Half the value of the contract he was trying to save, spent in order to save it.

The arithmetic is grotesque only if you read the meeting as a meeting. Horowitz didn't. He read it as a meeting about something other than what was on the agenda — a meeting about whether a man who didn't like Opsware's product could find a way to keep working with Opsware — and he changed what the meeting was about before he walked into the room.

The meeting is not always about what is in the meeting.

So let's go to the office and work through it.

"The meeting I'm about to run is going to be a fight."

The feeling is braced.

You know the room. You know who's in it. You know what they're going to do. The hour is a fixed point on the calendar between now and the rest of the day, and your shoulders have been up since you saw it there.

First read whether you hold any leverage

Two choices. The wrong one isn't a tactical mistake; it changes what the rest of the hour is.

When you can afford to give ground

Choice one: you've got leverage. Not a lot, necessarily — but enough that you can afford to give ground because you can afford to lose some of it. The conversation is structurally yours to lose, and the other side is coming in expecting a fight because that's the shape they've been ready for.

If that's the trap, open with a concession so disproportionate to the fight that the other side feels slightly foolish being hostile about it. Not a negotiating move. An overcorrection. The point is to change what the meeting is about before the meeting starts. People who were ready to argue with you find it surprisingly hard to argue with someone who's already given them more than they were going to ask for. Hormozi calls it asymmetric generosity; the older lineage runs through every negotiator who learned that the room you're in is partly the room you walked into.

When you have no leverage left

Choice two: you've got none. The other side holds the cards, and you're there to take the hit. Pretending otherwise — bringing your spreadsheet, your bullet points, your prepared rebuttal — only confirms that you're not paying attention to the actual shape of the hour.

If that's the trap, say so in the first thirty seconds. Not as a performance of humility. As a weather report. This is going to be uncomfortable, probably for most of an hour, and I don't think we're going to enjoy it. The expectation of pain is what makes pain tolerable. A meeting that announces itself as hard is easier to sit through than a meeting that pretends to be fine. Sutherland on psychological reframing — name the thing accurately, and the room recalibrates.

Get this wrong in either direction and the meeting becomes the thing you were braced against. Open generously when you have no leverage and you've handed them the win for free. Open as the weather forecaster when you have leverage and you've given away the room before anyone sat down. Read the leverage before you choose the move.

How to diagnose the threat before you defend against it

Three tools. The discipline is to diagnose the threat before you defend against it.

Name what is actually under threat in the room

The first is

SCARF Model.

David Rock published the SCARF Model in the NeuroLeadership Journal in two thousand and eight, drawing on the social-neuroscience work that had been gathering through the two-thousands on how the brain processes social threat.

The reason the tool exists is that meetings that turn into fights are rarely fights about the topic on the agenda. The thing being defended is something else — the protagonist's standing in the room, the in-group they belong to, their sense of where the decision should sit. Without a way of naming what's actually under threat, you respond to the symptom and the meeting gets worse.

The unique insight is that the brain treats social threats with the same circuitry it uses for physical threats. Same fight-or-flight response, scaled. Five domains carry most of what the brain reads as social threat. The standard mistake is to respond to the symptom — the aggression, the withdrawal, the cold disengagement — rather than to the domain underneath it.

What you get is a way to walk into a fight already knowing what it's actually about, and a response calibrated to the domain rather than to the noise.

So. The five domains, each with the question to ask and the response that lands.

Status. Are they about to be made smaller, in front of others? Acknowledge it publicly.

Certainty. Are they being asked to commit to something they can't predict the consequences of? Bound it — here is what we're committing to, here is what we're not.

Autonomy. Is the meeting taking a decision they think is theirs? Give a choice inside the decision.

Relatedness. Does the meeting threaten an in-group they belong to, or signal they're outside one? Signal that the in-group still includes them.

Fairness. Are they about to be treated by a different rule than someone else in the room? Articulate the rule.

Wrong domain, wrong response, worse meeting. The diagnostic is the meeting before the meeting.

Move the fight from positions to interests

The second is

Conflict Resolution.

The lineage that earns its place runs through Fisher and Ury's Getting to Yes, nineteen eighty-one, out of the Harvard Negotiation Project — untangle the people from the problem, focus on interests not positions, insist on objective criteria.

The reason the tool exists is that meetings that go wrong almost always go wrong for the same reason: the people in them are arguing for positions they've taken without ever putting the interests underneath those positions on the table. Position-against-position is unwinnable; interest-against-interest usually isn't.

The unique insight is the position-versus-interest distinction. Two children fight over an orange. The position is I want the orange. The interest, when you ask, is that one wants the juice for a drink and the other wants the peel for baking. The single orange satisfies both interests once you've pulled them clear of the position they were both arguing for.

What you get is a meeting where the room finds, almost always, that the interests are less in conflict than the positions made them sound.

So. How to run it inside the meeting.

Hear. Don't argue with it yet. Let it land. Positions get louder when they're not heard, and you can't surface an interest under a louder position.

Surface. The phrase that does the work, when the meeting is heating up: help me understand what would have to be true for that to be the right answer. Not aggressive. Not dismissive. It moves the conversation from the position to the interest underneath it.

Reframe. Restate the question in a form that includes both interests. We need a decision that protects margin and supports the deal. The argument is no longer about whether to support the deal; it's about how the decision serves both.

The skill is patience. Refuse to engage at the position level until the interests are explicit. Slower in the short term. Faster overall.

Map the overlap when the conflict is structural

The third is

Alignment Techniques.

The lineage on Alignment Techniques is broader and thinner — Harvard Project Management Institute work on stakeholder alignment, the OKR tradition formalised by John Doerr in nineteen ninety-nine at Intel and Google, goal-decomposition research from decades of strategic-planning literature. No single canonical source. The discipline that earns its place is what the lineage shares.

The reason the tool exists is that some meetings that look like fights aren't personal. They're structural — two parts of the organisation pursuing legitimate goals the room is letting them pretend are incompatible. Personal de-escalation doesn't fix a structural conflict; it postpones it.

The unique insight is that the move is to map the overlap. The CFO and the cro of the same company sit on either side of the table. The CFO's goals are margin, runway, predictable cost. The cro's goals are growth, deal velocity, market share. From outside the room they look like opposing forces. When you map them on a board, the overlap is almost always larger than either side thought. The CFO needs the deals to land — runway depends on revenue. The cro needs the cost discipline — deals end more cleanly when the company isn't burning. The shared interest is deals that land at the right unit economics.

What you get is a meeting where the structural fight stops being one, because the room can see the opposition was thinner than it sounded.

So. How to run it.

List. Each side, on the board, names what they need over the next quarter. Concrete, quantified where possible. Not values, not aspirations — goals.

Find. Where do the two lists touch each other? Where does what one side needs depend on what the other side delivers? Draw lines between the touching items.

Draw. Where the lines cluster, restate them as a shared goal both sides own. The shared goal is the artefact the room walks away with.

When the meeting is going to be a fight and you suspect it's structural rather than personal, draw the map before the meeting starts.

That's the toolkit. One more story before we close.

A precedent: using the meeting to lock in a number

The Horowitz story we opened with is about changing what a meeting is about by acting before it. The story we close with is the inversion: someone who used the meeting itself to make a public commitment that changed what every subsequent meeting could be about.

The seventeenth of March, two thousand and fifteen. Capitol Hill. The House Armed Services Subcommittee on Strategic Forces is holding a hearing on the Air Force's launch-vehicle programme.

Two witnesses at the table. Tory Bruno, chief executive of United Launch Alliance, the joint Boeing–Lockheed-Martin venture that has held a near-monopoly on national-security launches for fifteen years. And Gwynne Shotwell, president of SpaceX, whose company has spent the previous year suing the Air Force over the way the launch contract was awarded to ula without competition.

The legal fight is grinding. It is public. It is unlikely to resolve quickly. The hearing is the first room in which both companies have to defend their pricing on the record, in front of each other, with congressional staff holding the margin arithmetic in writing.

Shotwell makes the cost case explicit. American taxpayers have spent more than twenty billion dollars on the EELV programme since nineteen ninety-eight to underwrite a launch system that depends on Russian RD one-eighty engines — strategic vulnerability and commercial absurdity in the same sentence. I don't know how to build a four-hundred-million-dollar rocket. The line is meant to be heard.

Then she does the structural move. She commits SpaceX, on the congressional record, to Falcon Heavy pricing of one hundred and fifty to one hundred and sixty million dollars per launch, and to a fully domestic engine programme. The numbers are specific. The commitment is public. It is in the hearing transcript.

Once stated on the record in front of a competitor, the commitment cannot be softened quietly in subsequent contract negotiations. Ula cannot let SpaceX restate its price upward without losing the comparison. The Air Force cannot let SpaceX walk back the commitment without losing leverage with Congress. The number is locked.

Falcon Nine is certified for EELV missions in May two thousand and fifteen, two months later.

Shotwell didn't win the hearing by out-arguing Bruno. She used the hearing to lodge a number into the record, after which the argument was no longer about SpaceX's claims. It was about whether ula could meet them.

So. Horowitz changed the meeting by acting before it. Shotwell changed every subsequent meeting by what she said inside it. Both moves do the same structural work. The meeting is not always about what is in the meeting. Sometimes the move is to redefine the meeting before it starts. Sometimes the move is to use the meeting to commit to something the fight can't walk you back from.

The fight you're walking into is not always the fight worth having. The harder discipline is to spot, before the room starts, what the meeting could be made to be about that would make the fight unnecessary.

So. The question from this playbook.

Which two people on your team are pretending to agree in meetings and arguing in DMs — and what's it costing you to leave that conversation un-had?