Most project conflict is not two difficult people. It is two legitimate constraints in the same calendar — date versus quality, compliance versus cost, one scarce specialist — and you treat that as a design problem first, because personality is the residue that remains after the constraints are on the table.
Name the competing constraints
Get the fight out of character and onto variables. 'You are being unreasonable' becomes 'you need the compliance pack; they need the May launch.' Write both. If you cannot write them, you are still in the slogan layer. Stay there and the argument will follow you home.
Check the facts before you mediate the feelings. Is the date actually external? Is the regulation real? Is the specialist actually unique? A surprising number of conflicts collapse when one 'must' turns out to be a preference in a loud voice. A surprising number do not — and then you have a real trade-off.
Separate heat from content. People raise their voice when they have been ignored, surprised, or made to look careless. Acknowledge the heat in one sentence — 'you found out in the pack, that was badly done' — then return to the constraint. Therapy can wait. The date cannot.
Facilitate a trade, not a winner
Offer options that protect different constraints: slip the date and keep the check; keep the date and cut scope; keep both and add cost. Make the chooser explicit. You facilitate. You do not pick a favourite sponsor because they are nicer in meetings.
Use the smallest room that can decide. A public argument in a steerco of fifteen is sport. A working session with the two owners and you is work. Bring the evidence, not the audience. If the decision needs a board, take a recommendation, not a live brawl.
Timebox the unresolved. 'We decide Friday or the default is we hold the regulatory scope and move the conference demo to a subset.' Defaults prevent hostage-taking. Without a default, the louder calendar wins by running out the clock.
When it really is people
After the constraints are clear, you may still have behaviour: undermining, stonewalling, or a personal conflict leaking into the work. Address it privately, specifically, and early. 'In yesterday's meeting you contradicted the agreed date in front of the vendor. If the date is wrong, bring it to me before the call.' Vague requests to 'be more collaborative' are wallpaper.
Escalate behaviour that exceeds your authority — formal performance, harassment, ethics — through the actual line and HR path. Do not run a shadow disciplinary process because you have a RACI. And do not leave the delivery constraint unowned while everyone waits for a personality to improve.
Write the outcome of the conflict the way you write any decision: the trade, the owner, the date. Conflict that 'ended well' with no artefact will reopen at the next status. Peace is a recorded choice.
Course complete — what's next
Put constraints on the table, test which 'musts' are real, offer trades to the person who can choose, and record the result. Deal with leftover behaviour privately and through the proper line.
You now have a working comms practice: the right channel, meetings with outcomes, writing people will act on, listening for interests, and conflict as competing constraints. Use it on the next argument you were going to win by sending a longer email.