AdvancedHRManagerPeopleOps

Manager-vs-manager turf war: a step-by-step HR playbook with scripts

Two peer managers fighting over scope, headcount, or a shared report. A playbook for the HR partner — diagnose the structural cause, run the joint…

12 min read

On this page▾

Step 1 — Find the structural cause
Step 2 — Align the shared boss
Step 3 — Joint conversation (script)
Step 4 — Re-cut decision rights
Special case — fighting over a shared report

60-Second Summary

Turf wars are almost never about the turf. They’re about an unresolved structural decision — scope ambiguity, comp inequity, or unclear decision rights — that the managers are litigating through proxy fights.
Don’t mediate the symptom (this week’s flashpoint). Mediate the structure (who decides what, who owns whom, what the success metric is).
Both managers need the same shared boss in the room or in the loop. Without that, any agreement gets relitigated as soon as one of them goes around the other.
Re-cut decision rights in writing within 14 days. Without an artifact, you’re back here in two months.

Two peer managers in a turf war is one of the most damaging dynamics in an org — it cascades to both teams within weeks. The right move is almost never to ‘get them in a room and work it out.’ The right move is structural.

Step 1 — Find the structural cause

Cause	How to spot it	Fix
Scope ambiguity	Both think the same work is theirs	Written RACI for the contested decisions
Comp/level inequity	One is paid/leveled higher for similar scope	Comp review with both; equalize or justify
Unclear shared metric	They optimize for different scoreboards	One shared OKR with joint accountability
Shared report drama	A report plays them off each other	Named single manager; the other gets defined input rights
Resource scarcity	Headcount/budget allocation favored one	Transparent allocation method; both see the math

Step 2 — Align the shared boss

Script — HR to shared boss

‘I want to brief you before I bring [A] and [B] together. The flashpoint is [X]; the structural cause is [Y]. I’m going to propose [specific re-cut]. I need three things from you: (1) be in the room or endorse the outcome in writing within 24 hours; (2) don’t take side calls from either of them about this for the next two weeks; (3) commit to backing the re-cut publicly even if your favorite manager loses on this one.’

Step 3 — Joint conversation (script)

Script — opening the joint conversation

‘Thanks for making time. I’ve talked to each of you. We’re not going to relitigate the [flashpoint] today — we’re going to fix the structure that keeps producing flashpoints. Here’s what I’m proposing as the diagnosis: [structural cause]. Here’s what I’m proposing as the fix: [RACI / metric / re-cut]. I want each of you to push back on the diagnosis first before we discuss the fix. [A], you start. Three minutes. [B], paraphrase before responding.’

If either manager keeps pulling the conversation back to ‘what [B] did on Tuesday,’ call it: ‘That’s the flashpoint. We’re working on the structure. I’ll come back to Tuesday if it’s still alive after we re-cut.’

Step 4 — Re-cut decision rights in 14 days

Write a RACI for the 5–8 most contested decision types. R = responsible (does the work), A = accountable (one person, makes the call), C = consulted, I = informed.
Shared boss countersigns within 7 days.
Publish to both teams within 10 days. Public-by-default kills relitigation.
Set a 60-day review — keeps both honest, signals you’ll act if it isn’t working.

Special case — fighting over a shared report

When the contested resource is a person who reports dotted-line to both, the report is often (consciously or not) feeding the conflict by giving each manager a different version of priorities. The fix:

Name one solid-line manager. Dotted-line is a real thing but only one person writes the review and decides comp.
The other manager gets defined input rights — 360 input on the review, weekly priority sync, veto on a narrow scope.
Joint 30-min weekly between both managers + report — same agenda each week: this week’s priorities, blockers, comms.
If the report keeps triangulating after the new structure, that’s a performance conversation with the report — not a mediation between the managers.

Written by Pawan Joshi.Sources cited inline.

First published 15 Jun 2026See site changelog →