Two people, one number, no tiebreaker
There's $400,000 in contention. Marketing wants it for a Q4 campaign that supports a pipeline number they are measured on. Operations wants it for capacity they say will fail in November without it — and they're measured on that.
The two department heads are in a conference room on Tuesday. Neither reports to the other. Neither can direct the other to do anything. Neither controls the budget line. And neither of them is wrong.
If they don't resolve it, it goes up to the SVP, who will resolve it in maybe four minutes with a fraction of the context, in a way that will probably satisfy neither — and who will quietly file the fact that these two couldn't sort out a budget question between themselves.
They will also be working together every week for the foreseeable future, on things that matter more than this.
This is the most common significant conflict in corporate life, and it is nearly absent from business curricula, which teach conflict almost exclusively along the vertical axis.
The axis nobody teaches
Look at what a management program actually rehearses. A manager corrects an employee. A manager delivers a review. An employee escalates to a partner. A CFO negotiates with a lender. In every case, somebody in the conversation has authority — either the power to decide, or a clear structural relationship that gives the exchange a shape.
Lateral conflict has none of that, and the absence changes everything.
Nobody can end it. In a vertical conversation, someone eventually decides. Here, the only ways out are agreement or escalation, and escalation is expensive: you spend a chip with your boss, you signal that you can't manage peers, and you hand the decision to someone with less context than either of you.
The relationship is permanent. This isn't a vendor you'll see annually. It's someone whose cooperation you'll need in six weeks on something you care about more. A win that costs the relationship is usually a bad trade, and the calculation of how much winning is worth is one students have never had to make.
Your conduct is observed. Peer conflicts are semi-public inside an organization. How you handle one is information other people use to decide whether to work with you. Unlike an earnings call, the audience is implicit — but it's there.
And both of you are right. This is what makes the scenario genuinely hard, and what makes it useless to teach as a case with a correct answer. Marketing and Operations are each optimizing for a metric they are legitimately accountable for. The conflict isn't between a good argument and a bad one; it's between two incentive systems that were designed separately. Students trained on cases with a defensible answer will hunt for the answer and find that there isn't one.
The argument is almost never about the money
The single most useful thing to teach here: the stated conflict and the actual conflict are usually different objects.
A budget fight is a convenient container for a scope ambiguity nobody has resolved, a status question about which function owns a capability, a strategic disagreement that has never been surfaced explicitly, or a grievance from eight months ago that neither party has raised. Arguing the numbers when the real dispute is about ownership produces three rounds of increasingly detailed spreadsheets and no resolution — because each round is a more precise answer to the wrong question.
Cross functional conflict resolution starts with a diagnostic move that almost no student makes unprompted: find out what the other person is accountable for. Peers routinely do not know each other's metrics. When the marketing head learns that operations is carrying a service-level commitment with a personal bonus attached, the conversation changes character — it stops being a fight over money and becomes a shared problem of two commitments that can't both be funded.
That reframe doesn't guarantee agreement. It does reliably change what's being negotiated, and it's a technique rather than a temperament.
What works
Establish the shared objective out loud, and mean it. Not as a rhetorical opener before returning to your position — as an actual statement of what you're both trying to accomplish. Done cynically it's transparent and makes things worse.
Ask what they're accountable for, before arguing. As above. The two-minute version of this question resolves more conflicts than any amount of advocacy.
Separate the position from the need. "You asked for $400K" and "you need coverage for the Q4 launch" are different objects. The first admits only yes or no; the second has half a dozen possible answers, some of which cost less than $400K.
Arrive with a concession already made. Coming in having given something up — a scope reduction, a phasing, a piece of your own ask — changes the physics of the room immediately. It signals that you've engaged with their constraint rather than just your own, and it makes reciprocity socially expensive to refuse.
Trade across time, explicitly. "I'll take the cut this cycle. I need you with me on the headcount request in Q3." Peers run a ledger with each other whether or not anyone names it, and naming it is more honest than the alternative — which is an unspoken debt one party remembers and the other doesn't.
Agree on the joint story before you leave the room. The most practical and least taught move in the entire scenario. If this goes up, what do you both say? Two people presenting the same framing of a disagreement get a better outcome than two people presenting competing versions, because the boss isn't forced to adjudicate character alongside substance. Even when you escalate, escalating together is a completely different act from escalating first.
Four ways it goes wrong
The escalator takes it upstairs quickly and often wins the money. They also teach their peer that disagreements with them go to the boss, which is a reputation that compounds badly.
The litigator brings a deck and argues harder. Sometimes wins the exchange. Loses the person, and the next time they need a favor from Operations they find out what that cost.
The accommodator folds to protect the relationship, and this failure deserves more attention than it gets in conflict-avoidance literature: their own team notices. A department head who never wins resources is read by their people as someone who doesn't fight for them, and the internal cost lands on staff who weren't in the room.
The back-channeler agrees pleasantly and then works around the agreement — routes the spend elsewhere, appeals informally, slow-walks the implementation. The most corrosive of the four and disproportionately common among capable people, because it feels like pragmatism rather than defection.
Why the curriculum can't build it
Managerial accounting teaches the budget as a computation. Variance analysis, allocation methods, zero-based approaches — all real and all analytical. The budget is presented as an output of a process, when in practice it is a negotiated political artifact that reflects who argued well.
Negotiation courses teach the wrong game. Standard exercises are two parties, often strangers, frequently one-shot, usually with a distributive core. That framework is genuinely useful and it strips out the two features that define peer conflict: the relationship continues indefinitely, and other people are watching.
Group projects are the closest analog and they don't work. Students' only lateral-conflict experience is a team assignment — with a shared grade, no real resource scarcity, and a relationship that ends in twelve weeks. It rehearses none of the actual constraints.
Peer role play is least-bad here and still fails. This is the one scenario in the series where classmates are structurally right for the exercise: they are peers, with no authority over each other. But they lack the domain knowledge to argue a real budget position with any texture, and — decisively — the relationship doesn't continue past the exercise, which removes the single constraint that defines the entire problem. Take away the future, and the correct strategy becomes winning.
What simulation changes
Workplace conflict role play built as simulation supplies a counterpart with a real position, real accountability, and a repertoire of the moves that actually appear:
- The immovable peer, who has a defensible case and won’t shift. Tests whether the student can find a non-monetary trade.
- The escalation threatener, who reaches for the boss early. Tests whether the student can hold without either capitulating or racing them upstairs.
- The one with a grievance, whose resistance is actually about something from last year that surfaces only if asked. This is the highest-value rep in the set.
- The agreeable back-channeler, who concedes warmly in the room. Tests whether the student closes with something specific enough to be verifiable.
Every attempt transcribed — and the transcript answers the question that matters most here: did the student ever ask what the other person was accountable for, or did they advocate for ten straight minutes? Students almost universally believe they explored the other position. The record usually disagrees.
Designing the module
Pass one — find the real conflict. The peer with a grievance. Score whether the student surfaced the underlying issue before arguing numbers, and whether they asked about the other side's accountability.
Pass two — the trade. Score whether the student arrived with a concession, separated position from need, and proposed a trade across time rather than within the quarter.
Pass three — the escalation threat. Score whether the student held the conversation without escalating unilaterally, and whether they proposed a joint framing if escalation was genuinely necessary.
Rubric on observable behavior: Did they state a shared objective credibly? Did they ask what the other party is measured on? Did they offer something before asking? Was any agreement specific enough to verify next month? Did they align the story before leaving?
The program-level case
It's the competency employers name most and programs teach least. "Works well cross-functionally" and "influences without authority" appear in nearly every leadership competency model and nearly no syllabus. In matrixed organizations — which is most large organizations now — this is the dominant mode of getting anything done.
It integrates two courses that already exist. The scenario sits exactly between managerial accounting and organizational behavior, which is the integration business programs claim to want and rarely execute. One exercise makes the budget real in the accounting course and makes the OB content concrete.
It produces direct assurance-of-learning evidence. Teamwork, leadership, and communication sit in essentially every program's stated goals and are typically measured through peer evaluations on group projects — an instrument almost nobody defends. A scored behavioral simulation gives a direct, rubric-anchored measure across sections, which is a materially stronger artifact for AACSB assurance of learning.
It's experiential learning without the coordination cost, and the executive education demand for lateral leadership skills is durable: every reorganization creates a fresh cohort of managers who suddenly have accountability without authority.
The short version
Business schools teach conflict as something that happens between people at different levels, because that's the version with a clean resolution mechanism. The version that actually consumes a working week has no such mechanism — two people who each have a legitimate case, neither of whom can decide, both of whom need each other next quarter.
Influence without authority is not a personality trait some graduates happen to have. It's a set of moves: find what they're accountable for, separate position from need, concede first, trade across time, and agree on the story before you leave. Every one of those is practicable, and none of them are currently practiced.
Foretell AI lets faculty build conversational simulations — including cross-functional budget conflicts like the one above — with configurable counterparties, transcripts, recordings, and rubric-based evaluation. If you're connecting managerial accounting to leadership content or mapping outcomes to assurance-of-learning goals, we're happy to walk through how other programs have structured it.