You're Not Negotiating for Budget. You're Negotiating for Belief.

A lead I worked with went into a finance meeting asking for two contract engineers for eleven weeks. He'd built a proper case: the run rate, the slip, the cost of the delay against the cost of the people. It was a good case. He got a flat no in about ninety seconds, walked out furious, and spent the next fortnight telling anyone who'd listen that finance didn't understand delivery.

Finance understood delivery fine. What he'd missed was that the finance director had been told in March to bring contractor spend down by the year end, and had said so publicly, and was now being asked to personally approve the exact number that was being counted. The money was never the problem. The visibility of the money was.

A position is the thing someone says: no more contractors, the date can't move, we need it in Q3, that architecture is not acceptable. A position is the answer they've already arrived at.

An interest is why they arrived at it. Protect a public commitment. Avoid being the one who signs off an overspend. Not get caught out in front of their own boss again after last time. Keep a team they've spent a year rebuilding from burning out.

If you argue against a position you can only win by making someone publicly wrong, which they will not do, and which makes them worse off even if you win. If you find the interest, you can often satisfy it with something that costs you very little.

In that contractor example, the interest was contractor spend appearing in a year-end number. The deal that eventually happened, three weeks later than it should have: one contractor instead of two, plus two internal engineers borrowed from a project that was blocked anyway, plus a start date pushed by nine working days so the spend landed in the new financial year. The delivery got about eighty percent of what it needed. The finance director's public commitment held. Nobody lost.

That arrangement was available on day one. It took three weeks to find because the first meeting was a fight about whether two contractors were justified.

So the preparation question isn't "how do I make my case stronger". It's "what does this person need to be true when they walk out of the room". Write that down before you go in. If you can't answer it, you're not ready, and you should spend twenty minutes finding out rather than burning your one clean shot.

Most of what you'll negotiate as a technical lead is with people who don't report to you and who you don't report to. Another team's lead. A supplier's delivery manager. A security function that can stop you dead. You have no lever. What you have instead is being the person in the room whose numbers turn out to be right.

That's a slow asset and it's built in an unglamorous way. You publish a figure. The figure holds. You publish another one. It holds too. Six months later someone says "if she says it's eleven weeks, it's eleven weeks", and at that point you can move things you have no authority over at all.

It's also fragile in one specific way, so protect it. Never round in your own favour. If the honest range is nine to fourteen weeks, say nine to fourteen weeks and explain what makes the difference between the two ends. Saying eleven because it sounds decisive gets you one easy meeting and a very expensive reputation, because when it comes in at fourteen you will be remembered as the person who was wrong rather than the person who gave a range.

And bring the evidence the other person would have gathered themselves. On a network refresh for a national charity, the argument with operations wasn't won by the delivery plan. It was won by pulling the site completion rate across their regional offices for the previous six weeks, splitting it by region, and showing that the two regions with a named local coordinator were running at nearly double the rate of the four without one. Operations weren't being asked to believe a forecast. They were being shown their own data, and the conclusion drew itself.

You will occasionally be asked for something you should not agree to. A date you know is fiction. A scope addition with no time attached. A sign-off on a design you think is genuinely unsafe.

What stops you folding in that moment is not courage. It's having decided, before you walked in, what happens if you don't reach agreement, and being honest with yourself about whether that alternative is survivable.

Sometimes it is. "If we can't get the extra two weeks, we deliver the core payments flows on the date and the reconciliation module lands in February, and I'll put that in writing today so the finance team can plan." That's a real alternative. You can say it calmly because you've already made peace with it.

Sometimes it isn't, and then you need to know that too, because negotiating hard from a position you can't back up is how people lose credibility in one meeting. If your only alternative is "we miss the regulatory date and get fined", you are not in a negotiation about the date. You're in a conversation about what gets cut, and you should open with that rather than posturing for forty minutes first.

Write the sentence out beforehand. Actually write it. The act of putting it in words tells you very quickly whether you've got a position or a bluff.

One caution on the internal version of this. Inside your own organisation, you are negotiating with someone you'll need again in six weeks, and there is a shared outcome underneath both your positions even when it doesn't feel like it. Winning too hard internally is a form of losing. With a supplier, under a contract, a firmer line is appropriate and expected. Using the supplier register on a colleague is how you become the person everyone routes around.

You almost certainly have one coming. More people, a later date, a different architecture, a budget line.

Before that meeting, sit down for fifteen minutes and write three things on one page.

First, their interest. Not their position, the reason behind it. If you don't know it, go and ask someone who does, or ask them directly in a two-minute call beforehand. That call is the highest return fifteen minutes in this whole business.

Second, the one piece of evidence they would find hardest to argue with, ideally drawn from their own numbers rather than yours.

Third, the sentence you'll say if the answer is no, including what you'll do instead and the date you'll confirm it in writing.

Then decide, on paper, which of the three you're least prepared on. Fix that one before you walk in.