The Slack DM lands on a Tuesday at 4:47 PM.
“Hey, got a sec? Need to pull Sarah onto Project Atlas for the next six weeks. Already talked to leadership, they’re on board. Can we make it work?”
You read it twice. Sarah is your senior engineer. The one who’s been carrying the integration work. The one whose absence would slip your Q3 milestone by two months. The one you finally hired and ramped after a six-month search.
But the message frames it like it’s already decided. “Leadership is on board.” “Can we make it work?” You feel the social pressure: be a team player, be flexible, don’t be the person who blocks the cross-functional thing.
You type back: “Let me check the project timeline and get back to you tomorrow.”
You’ve already lost.
This Isn’t a Request. It’s a Negotiation.
The most overlooked negotiations inside any company are the ones that don’t look like negotiations. The budget conversation we covered in Part 2 at least feels like a negotiation — there’s a meeting, there’s a number, there’s a clear ask. Resource fights are sneakier. They show up disguised as logistics, alignment, or “just a quick favor.”
But every element of a negotiation is there:
- Two parties with different interests
- A scarce resource (your engineer’s time)
- A counterparty using leverage (“leadership is on board”)
- A frame designed to make refusal feel unreasonable
The reason most people lose these is they don’t recognize they’re in one. By the time the formal asks start landing in your inbox, the other VP has already done three weeks of prep, lined up executive backing, and built a narrative where you’re the obstacle.
If the other side is using negotiation tactics and you think you’re being collegial, you’re not being collegial. You’re being negotiated against by someone who knows you won’t push back. The first move is recognizing the move.
Why Resource Fights Are Harder Than Budget Fights
Three things make this conversation structurally harder than a CFO ask.
There’s no spreadsheet. Budget conversations live in numbers. Resource conversations live in narrative. Whose project is more important? Whose deadline is more real? Whose engineer is more critical? Almost none of it is quantified, which means it’s decided by whoever tells the better story.
There’s no neutral authority. A budget request goes to the CFO, who has authority and a framework. A resource request often goes peer-to-peer, with no clear arbiter. If it escalates, it lands on a shared boss who didn’t want this on their plate and will resolve it by splitting the difference — which always favors the asker.
The relationship is permanent. You will work with this VP for years. You can’t burn the bridge. You can’t refuse outright. You can’t even appear difficult. The constraint isn’t “win the negotiation” — it’s “win the negotiation in a way that strengthens the relationship.”
That’s a higher-difficulty game than most external negotiations.
The Three Mistakes That Lose This Negotiation
Before the moves, the failure modes. Three mistakes account for almost every lost resource fight.
The Capitulation. You say yes because you don’t want to look uncollaborative. You’ll figure out how to backfill. You’ll work weekends. You’ll find a way. (You won’t, and your Q3 ships late.)
The Stall. You buy time. “Let me check the timeline and get back to you tomorrow.” You think you’re being thoughtful. They hear “I don’t have a real objection, just give me a day to come up with one.” Stalls always weaken your position. Use the time, but don’t telegraph the indecision.
The Counter-Demand. You push back hard. “Absolutely not, Sarah is fully committed.” Now the conversation is adversarial, the other VP escalates, and you spend the next two weeks defending a position instead of negotiating one.
The right move is none of those.
The Right Response Has Three Parts
When the message lands, the response framework is the same every time. Three parts, in order.
The Resource Defense Playbook
Notice what this does: it reframes the conversation from “will you give me Sarah?” to “how do we solve for both projects?” That’s the whole game. The person who controls the framing controls the outcome.
On “Leadership Is On Board”
The phrase “leadership is on board” or “leadership signed off” deserves a section of its own. It’s the single most common piece of pressure language in internal negotiations, and it’s almost never as solid as it sounds.
What it usually means: the other VP mentioned the project in a leadership meeting, named the resource they wanted, and didn’t get a strong objection. That’s not approval. That’s the absence of pushback in a room full of people who weren’t paying close attention.
"”Leadership is on board” usually means “I told them about it and nobody objected.” That’s a long way from “they decided your team will lose its best person for six weeks.”"
The response isn’t to challenge the phrase directly — that escalates. The response is to surface the trade-off to the same leadership.
“That’s great that leadership sees Atlas as a priority. I want to make sure they also see what this does to the Q3 customer commitment we made in March. Can we get the three of us — you, me, and [shared boss] — in a room for fifteen minutes to align on the trade-off?”
Now you’ve done two things. You’ve not refused. And you’ve ensured the decision happens in a room with full information, with both project owners present, in front of the person who actually has the authority to make the call. Nine times out of ten, “leadership is on board” doesn’t survive that meeting.
When you hear “leadership is on board,” your move isn’t to challenge it. Your move is to put the trade-off in front of the same leadership. The person making vague claims about authority almost never wants to revisit them with the person they cited.
The Game Inside the Game
Every resource fight is also a precedent fight. If your engineer gets pulled this time, with this little process, the same will happen next quarter — with less warning, because last time worked. The other VP just learned that asking gets results.
The opposite is also true. If the negotiation produces a real structure — a defined scope, a time-boxed engagement, a clear handoff plan — the next ask comes with that same level of rigor pre-built in. You’ve trained the other side to take your team seriously.
That precedent is worth more than the outcome of any single ask.
The Mindset Shift
Stop treating resource defenses as the moment your team needs to be protected. Start treating them as the moment you teach the rest of the company how your team gets engaged.
The colleagues who consistently keep their best people focused aren’t the ones who say no the loudest. They’re the ones who reframe every ask as a structured negotiation — and turn each one into the template for the next.
That’s the move that compounds.
"The win isn’t keeping Sarah on her project. The win is teaching the company that “can you spare Sarah?” is a real conversation — not a courtesy request."
Closing the Series
This wraps the three-part Internal Negotiations series. The through-line across all three posts is simple: the negotiations inside your company are real negotiations, and they shape your career more than almost anything else you do.
- Part 1 made the case that these are real negotiations, not “alignment.”
- Part 2 went deep on the CFO conversation — the vertical, structured, numbers-driven one.
- Part 3 covered the resource fight — the lateral, narrative-driven, relational one.
Three different patterns. One underlying skill. The colleagues who consistently get the budget, keep their best people, and ship on time aren’t the loudest or the most political — they’re the ones who recognize when a negotiation has started and prepare for it as seriously as any external deal.
What’s the next resource conversation heading toward your inbox — and have you decided how you’ll respond before the Slack DM lands?
Want to know how your style tends to handle resource defenses — and where the patterns you default to are costing your team?