Cross-Functional Brokering: Leadership Team Conflict Resolution

The Monday meeting had become a rerun. CRO and CFO, same fight, fourth week running. CRO wanted bottoms-up forecast: rep-by-rep commits, 1.4x coverage, $14.2M for the quarter. CFO wanted tops-down: prior-quarter actuals, 0.85x haircut, $10.0M. The gap was $4.2M. The board deck was two weeks late. Sales kickoff couldn't be planned because nobody knew the number.

The CEO pulled me into a 1:1 on a Wednesday and said five words I'll never forget: "Fix this. I don't care how."

That was the moment I stopped being the person who took notes in the exec meeting and started being the person who decided what got decided. Not because I was qualified to pick the right forecast methodology. I wasn't. But because nobody else in the building was structurally positioned to broker between two VPs without it looking like a power play. That's the Chief of Staff job. Welcome to the actual work.

Why brokering is the highest-leverage skill you have

Every other CoS skill compounds. If you're great at running the staff meeting, you save the leadership team three hours a week. If you're great at writing the board narrative, you save the CEO a weekend. Those are linear wins.

Brokering is different. Get it right, and you compound trust with three executives at the same time: the CRO who feels heard, the CFO who feels heard, and the CEO whose Monday morning didn't get hijacked again. Get it wrong, and you become "the person who took the CRO's side," which is the kind of label that follows you into your next role. There's no neutral outcome on a brokered conflict. You either build career capital with everyone in the room, or you spend it.

Most Chiefs of Staff I've coached underestimate how often this comes up. They think their job is the operating cadence, the OKR rollups, the board prep. Those are the visible artifacts. The invisible work, the work the CEO actually grades you on, is whether the leadership team can make decisions without the CEO refereeing every fight.

The broker mindset: translator, not decider

Here's the rule that took me eighteen months to internalize: your job is to make the disagreement legible, not to resolve it.

The moment you start advocating for an outcome, you stop being useful to both sides. The CRO will smell it. The CFO will smell it. They will both stop telling you the truth, which means you lose the only asset you have: clean information from both rooms. And then the CEO loses confidence in your read, because every brief you write starts to sound like one VP's argument with footnotes.

Translator means: I can tell you what the CRO actually believes (not what he says in the meeting), what the CFO actually believes (not what she emails the CEO), and where the real disagreement lives. I cannot tell you which one is right. I won't even pretend to.

This sounds passive. It isn't. Surfacing a disagreement cleanly is harder than picking a side. Picking a side is a 30-minute exercise. Mapping where two smart people genuinely diverge, and why they diverge, takes a week of careful conversations and a ruthless framing memo. The work is in the diagnosis, not the verdict.

The first time I escalated to the CEO with a recommendation instead of a framing, he handed the memo back and said, "I have a CRO and a CFO. I don't need a third opinion. I need the disagreement on one page." That feedback rewired how I thought about the role.

Surfacing the real disagreement: principle, data, or personality?

Most "strategy fights" between VPs are actually one of three things wearing a strategy costume. Diagnose which one before you write a single line of memo, because each requires a different fix.

Principle. The two leaders genuinely disagree on a value or worldview. CRO believes the company should be aggressive on commits because culture follows ambition. CFO believes the company should be conservative because credibility with the board is the long-term moat. Both are defensible. There is no data that resolves a principle fight. Only the CEO can.

Data. The two leaders are looking at different numbers and don't realize it. CRO's 1.4x coverage assumes the new SDR cohort productivity hits Q2 plan. CFO's 0.85x haircut assumes it doesn't. They're not actually disagreeing on the forecast. They're disagreeing on a hidden input. Fix the input, the disagreement evaporates. This is the easiest fight to broker. It's also the most common. Roughly half the "principled" fights I've seen turn out to be a data alignment problem in disguise.

Personality. The two leaders don't trust each other and the strategy debate is the proxy. CRO thinks CFO doesn't respect Sales. CFO thinks CRO is slippery on numbers. Until you fix that, they will fight about every forecast, every comp plan, every territory. No memo will solve a personality fight. You either get the CEO to address it directly with both of them, or you accept that this is an ongoing tax on the company.

The diagnostic questions I run through before writing the memo:

1. If I gave both of them the same data, would they agree on the answer? (If yes, it's a data fight.)
2. If they trusted each other completely, would they still disagree? (If yes, it's a principle fight.)
3. Has either of them brought up the other person's competence or motives in the last 30 days? (If yes, there's a personality layer underneath whatever else is happening.)

In the forecast fight, the answer to question one was no, question two was yes. Principle. The CRO genuinely believed in commits-as-culture. The CFO genuinely believed in conservatism-as-credibility. That meant the CEO had to call it. Which meant my job was to brief him before the meeting, not during it.

Pre-meeting alignment: don't surprise the CEO

This is the cardinal sin of CoS work. If your CEO walks into the decision meeting and learns something for the first time, you have failed. It does not matter how good your framing memo is. It does not matter that you were right. The CEO has to look prepared in front of two VPs, and your job is to make sure that's never in question.

The 24-to-48-hour pre-brief is non-negotiable. Here's the script I use, and have used for four CEOs:

"I want to walk you through where the CRO and CFO actually are on the forecast methodology before Monday's meeting. I'm not asking you to decide today. I want you to know what each of them is going to argue, where I think the real disagreement is, and the three options I'm planning to put in front of you. If you want to pre-react to any of them, this is the time."

Three things this script does. It signals you're not asking for a decision in the hallway, which lowers the CEO's defenses. It frames the disagreement as something you've already mapped, which earns trust. And it gives the CEO a chance to say, "actually, I already know I won't pick option C, take it out," which saves you from putting a dead option in the memo and looking lazy.

If the CEO says "fine, decide it yourself," that's a signal. Either the disagreement isn't important enough for him to weigh in (rare), or he's testing whether you'll push back. The right answer is usually: "I can recommend, but I'd rather you make the call. Both VPs need to feel the decision came from you, or the loser will spend the next quarter relitigating." That sentence has saved me from at least four bad escalations.

The framing memo: 3 options, recommendation, why

The framing memo is the artifact that does 80% of the brokering work. It's also where most Chiefs of Staff blow themselves up. Two failure modes: it becomes a six-page deck nobody reads, or it becomes a lawyer's brief for one side.

The template I've used and stolen from for years:

DECISION: [One sentence. The actual question that needs a yes/no/pick-one.]

CONTEXT: [Three sentences max. Why this matters now and what's blocking.]

WHERE THE DISAGREEMENT LIVES:
[Two sentences. Principle, data, or personality. Be honest.]

OPTION A. [CRO's preferred path]
- What it is: [One sentence]
- Why CRO wants it: [Two sentences, in CRO's voice, steel-manned]
- Risks: [Two sentences, honest]

OPTION B. [CFO's preferred path]
- What it is: [One sentence]
- Why CFO wants it: [Two sentences, in CFO's voice, steel-manned]
- Risks: [Two sentences, honest]

OPTION C. [The compromise or third path]
- What it is: [One sentence]
- Why it might work: [Two sentences]
- Risks: [Two sentences]

RECOMMENDATION: [If asked. Otherwise: "No recommendation. This is a CEO call between A and B."]

NEXT STEP: [Who decides, by when, who tells the team.]

One page. If it spills onto a second page, you're not done thinking. The discipline of the page limit is what forces you to find the actual disagreement.

The "steel-manned" part matters. If your description of Option A reads like the CFO would write it about the CRO, the CRO will know within thirty seconds. Both VPs will get this memo or hear it referenced. Both have to feel their position was represented at full strength. If you can't write the CRO's argument so well that the CRO would sign off on it, go talk to the CRO again. You haven't done the work yet.

The recommendation is optional, and that's deliberate. On principle fights, I don't recommend. On data fights, I almost always do, because the data resolves the question and saying "I recommend Option A because the new-SDR-cohort assumption is in plan" is just doing the math. On personality fights, never recommend. Recommending in a personality fight makes you a participant.

When to escalate to CEO vs decide between them

Most Chiefs of Staff escalate too early or too late. Both are career-limiting. The four-question test I run:

1. Is this reversible? If the decision is reversible within a quarter at low cost, you can decide it yourself and tell the CEO after. If it's a budget cut, an org change, or anything that touches headcount, escalate.
2. Does it require a value call the CEO hasn't made yet? If the company has never decided whether to be aggressive or conservative on the forecast, you can't decide that. Escalate.
3. Will the loser accept your decision? If both VPs trust you enough to take a call from you, decide it. If either one is going to walk out and re-litigate it with the CEO an hour later, escalate. Skipping the escalation makes you look like you overstepped.
4. Does the CEO want to weigh in? Some CEOs want every leadership disagreement on their desk. Others want the CoS to filter ruthlessly. Know which one you have. The pre-brief is where you find out.

If the answers are reversible, no value call required, both VPs will accept your read, and the CEO doesn't need to weigh in: decide. Write the memo, take the heat, move on. Anything else, escalate.

The first time I escalated too early, the CEO told me, "I hired you so I wouldn't have to decide things like this." The first time I escalated too late, the CEO told me, "I don't want to learn about this from the CFO." Both lessons came in the same year. The four-question test is what came out of those two scars.

Post-decision communication: making the loser whole

The decision gets made. One VP got their way. The other didn't. If you don't run a deliberate debrief with the loser within 24 hours, you will pay for it on the next decision, and the one after that.

The loser-VP debrief script:

"I wanted to come find you before end of day. I know the call didn't go your way. I want you to know that the memo represented your position fully, the CEO read it carefully, and the decision came down to [the principle / the data point / the strategic priority]. It wasn't because your argument was weak. It was because the company made a different call on [X]. What do you need from me on the rollout so you're not stuck defending a decision you didn't make?"

Three things this does. It tells the VP their position was represented honestly, which protects your relationship. It separates "you lost" from "you were wrong," which protects their credibility with their team. And it offers them help on the rollout, which makes the next disagreement easier to broker because the VP knows you'll have their back even when the call goes against them.

Skip the debrief and the VP starts viewing you as the CEO's enforcer rather than a neutral broker. Once that perception sets in, every memo you write gets read with suspicion. You can't broker from that position.

The "they'll work it out" trap

The most expensive sentence in executive operations is "they'll work it out." Senior leaders default to it because it sounds mature, low-drama, trusting of the team. It is none of those things. It is, almost always, abdication wearing a wise-uncle costume.

Two VPs in genuine disagreement do not work it out. They go quiet in front of the CEO, then run parallel plans inside their orgs, then collide three months later with twice the damage and twice the cost. The forecast fight I described above had been live for four weeks before the CEO pulled me in. In those four weeks, the CRO had already started telling reps the higher number, and the CFO had already sent the lower number to the board's audit committee. The cost of "they'll work it out" was an awkward board call, a sales kickoff that had to be rescheduled, and three weeks of my life.

If a senior leader, including the CEO, tells you the VPs will work it out, the right pushback is not confrontational. It's a question:

"I want to make sure I'm reading the room right. The CRO is telling reps $14.2M. The CFO is telling the board audit committee $10.0M. Both numbers are already public inside their orgs. If we let it run another two weeks, we'll have to explain to the board why two of your VPs gave them different numbers. Do you want me to broker it now, or are we comfortable with that risk?"

The question reframes "work it out" as a specific cost the leader is choosing to pay. Most of the time, when the cost is named, the leader picks "broker it now." When they pick "let it run," at least you've documented the choice and you're not the one holding the bag.

I've never once seen a VP-level disagreement actually work itself out. I've seen them go underground, calcify, and resurface as much bigger problems. Push back on the trap every time.

Common pitfalls

Becoming the CRO's lawyer because you talk to him more. The VP whose office is closest to yours, or who pings you most often, will pull your framing toward their position without either of you noticing. Audit your last three memos. If two of them lean the same direction, you've drifted.

Letting the framing memo turn into a six-page deck. If it doesn't fit on one page, you haven't found the actual disagreement yet. Go back. Talk to both VPs again. Find the principle, data, or personality core, then strip everything else.

Escalating before you've surfaced the disagreement. Putting "the CRO and CFO disagree on the forecast" in front of the CEO is not surfacing. The CEO already knew that. Surfacing means: here is the principle they're actually fighting over, here are the three options, here is why a compromise is or isn't possible. Don't escalate until you can write that paragraph.

Forgetting the loser-VP debrief. Every Chief of Staff I've coached has done this at least once. The decision goes well, you move on to the next thing, two weeks later the losing VP is cold to you in the hallway. You can't undo it. Set a calendar block for the debrief before the decision meeting starts.

Measuring success

You'll know the brokering is working when four things happen. The same fight stops repeating in Monday meetings. The CEO stops being surprised by VP disagreements. Both VPs separately tell the CEO that the CoS handled it well, and you'll hear about it indirectly, which is the highest compliment in this role. And the next disagreement gets routed to you faster, often before the CEO even hears about it.

The forecast fight I opened with took me eleven days to broker. The memo had three options: bottoms-up at 1.4x ($14.2M), tops-down at 0.85x ($10.0M), and a blended methodology with a published reconciliation ($11.8M). The CEO picked the blended option. The CRO got the bottoms-up rep-level commits he wanted in the comp plan. The CFO got the tops-down number she could defend to the board. Both VPs walked out feeling represented. The Monday meeting moved on to the next problem within fourteen days.

Six months later, when the CRO and CPO got into a fight over Marketing-sourced pipeline, the CEO didn't pull me into a 1:1. He just forwarded the email thread with three words: "You've got this."

That's the job.

Learn More

• Companion JD: Business Operations Manager
• Running the Executive Staff Meeting
• Decision Memos That Actually Get Decisions
• Managing Up Without Being a Suck-Up