People Management
Mediate a Conflict Between Teammates Without Deciding Who Is the Better Person
A fictional facilitator screens a runbook-review disagreement, helps both colleagues accept a working agreement, and revisits a missed review without deciding personal blame.
To mediate a disagreement between teammates, first confirm that a voluntary discussion is suitable and that you can facilitate it fairly. A manager-led problem-solving conversation is not automatically the trained mediation service described by an employer. Help each person describe the work, its impact, and what they need next. Then turn the shared ground into actions both people accept. If you have a stake in the disputed decision, need to investigate an allegation, or cannot provide the agreed process, arrange appropriate support rather than presenting your own judgment as neutral mediation.
This LandOffer.ai guide includes an original fictional meeting agenda and a completed agreement with a missed action and a later review. Public institutional guidance was checked October 27, 2026. No real employees were interviewed, meeting held, report sent, or personnel record accessed. The examples teach preparation and follow-through; they do not establish legal rights, guarantee confidentiality, or demonstrate improved relationships or performance.

Decide whether you should facilitate this conversation
Begin with the kind of problem in front of you. A disagreement about review requests may benefit from clarifying expectations. A disputed payment, disciplinary finding, or allegation requiring investigation needs its relevant process. Calling every difficult conversation mediation can hide those differences and create promises you cannot keep.
UC San Diego's conflict-management overview distinguishes early informal problem-solving from formal complaint procedures. Its separate mediation guidance describes voluntary assistance from a trained mediator who helps people design their own solutions. These are named institutional practices, not automatic rules for another employer.
Ask whether each person can participate voluntarily and whether you can remain impartial. Being their manager does not automatically disqualify you from a useful discussion, but your involvement matters. If you ordered the disputed deadline, are deciding a performance consequence, or already committed to one person's account, disclose that problem and seek an appropriate facilitator. Do not simply promise to put your stake aside.
Check organizational procedures before offering confidentiality. UC San Diego's mediation service has specific rules about discussion records and disclosure. Those rules do not transfer to an ordinary manager meeting. Agree what can be recorded, who will receive it, and any limits that the authorized process requires. If a person raises a concern needing another route, pause and explain that route rather than negotiating silence.
Prepare each person without deciding the case in advance
Meet separately if the agreed process calls for it. Explain the purpose, your role, the proposed format, and how either person can raise a concern about continuing. Ask each for a few concrete examples and the change they want. Do not promise that the joint meeting will endorse their account or require the other person to apologize.
Keep the preparation focused on accessible work records. A request date, a changed deadline, or an unresolved review comment can clarify a disagreement. It may not establish why someone acted or how the other person experienced it. Ask what each record shows and what remains disputed. Avoid inviting private colleague histories or unnecessary personal information into a shared packet.
Acas describes workplace mediation as impartial, voluntary, and focused on future working arrangements. Its guidance is written for the UK workplace context. Its description of confidentiality belongs to that mediation process; this article does not treat it as a legal protection for every employer conversation. Acas also discusses trained internal mediators and external help when impartiality is difficult.
Do not use the invitation to pressure consent. Explain alternatives under the actual organizational procedure, and avoid promising that declining will have no consequence you cannot control. If voluntary participation is not possible, record that the proposed discussion did not proceed and seek the right support. Ask what prevents voluntary participation and use the appropriate route; do not record a jointly chosen solution when consent is absent.
Worked agenda: a review disagreement with an impartial facilitator
Asha and Ben work at fictional Cedar Services. Asha maintains an internal deployment runbook; Ben reviews operational instructions. Their manager Omar requested a rushed deadline that is now part of the disagreement. Omar asks Mina, a trained internal facilitator from another team, to assess whether a voluntary discussion is appropriate. Mina has no responsibility for the disputed work or either employee's evaluation.
In the authored preparation, each person separately agrees to the discussion. Mina confirms the limited purpose: agree how ordinary runbook-review requests will work next. The meeting will not decide misconduct, change release authority, or require agreement about past motives. Both approve sharing only their final operational agreement with Omar; Mina explains the employer's process limits before they participate. The article's fictional dialogue is a teaching device, not a retained mediation transcript.
They select three records that they are allowed to discuss:
| Record | Shared factual reference | Different accounts still to hear |
|---|---|---|
| R14 | Asha requested review Tuesday at 16:40 for Wednesday noon; Ben responded Wednesday at 11:15 | Asha expected a morning review; Ben says no review window had been accepted |
| R15 | Ben added a terminology question after Asha marked the draft ready | Asha saw reopening settled work; Ben thought the wording changed an operational instruction |
| R16 | Asha placed the latest revision in a new document while the request linked the old one | Asha expected Ben to find the update; Ben reviewed the linked version |
These records establish a starting point, not a verdict. The case supplies no measured delay cost, production incident, or reason to label either colleague careless. R15 may also need a content decision outside the meeting. Mina keeps that question separate from how review requests should be made.
Her completed 45-minute agenda has a purpose for each part:
| Minutes | Facilitated activity | Output in the fictional meeting |
|---|---|---|
| 0–5 | Reconfirm purpose, participation, sharing boundary, and ability to pause | Both accept discussing the review process without deciding personal blame |
| 5–15 | Each person explains one record and its impact without interruption | Asha describes uncertainty near deadlines; Ben describes receiving requests without an agreed slot |
| 15–23 | Each restates the other's concern and asks a clarifying question | They distinguish receiving a link, accepting review work, and approving content |
| 23–35 | Compare workable options and the authority each requires | They choose proposed review windows and a single current-draft link; release authority stays unchanged |
| 35–45 | Read back actions, exceptions, sharing permission, and a review date | Both accept a two-week arrangement; Omar's capacity support is requested separately |
The agenda does not reserve equal blame. Mina gives both people space to speak while allowing a factual discrepancy to remain unresolved. Asha can acknowledge that the old link caused confusion without accepting Ben's interpretation of every earlier request. Ben can acknowledge deadline uncertainty without agreeing that every late change was unnecessary.
Mina asks, “When you say the review was accepted, which response meant that to you?” Asha points to an acknowledgment. Ben explains that he meant only that he had seen the request. Neither person had stated a review time. They have identified an acceptance rule to change without agreeing about each other’s motives.
Build an agreement people can actually carry out
Translate the discussion into observable actions. “Communicate better” leaves the next disagreement waiting. A useful agreement says how to request work, how the other person accepts it, where the current version lives, and what to do when the arrangement cannot hold. Include limits so that the next request can proceed without repeating the same ambiguity. Acknowledging receipt, accepting a review time, and approving content remain three different actions.
Within the fictional case, Asha and Ben accept the following trial for November 2–13, 2026. Omar subsequently confirms protected review capacity on October 30. His confirmation is a separate authored action; Mina does not assign his time while he is absent. No third teammate is volunteered as a substitute.
| Agreed action | Owner and accepted term | Evidence for the follow-up |
|---|---|---|
| Make the request reviewable | Asha links one current draft, identifies changed sections and the requested completion time | The request contains the link, scope, and deadline |
| Accept or negotiate the review | Ben replies with an accepted completion time or a proposed alternative; “received” alone means acknowledgment | A separate response states the agreed review time |
| Protect routine capacity | Omar reserves Monday and Thursday 14:00–14:30 review slots during the trial | Both employees receive his accepted capacity arrangement |
| Flag consequential wording | Either person marks an unresolved operational meaning question and identifies its owner | The draft retains an open question; no inferred approval |
| Handle absence or urgency | The available person contacts Omar through the ordinary work route for a revised plan | Omar's explicit decision, not an assignment to an absent colleague |
| Revisit the arrangement | Both meet Mina November 6 and November 13 for a bounded review | Accepted actions, missed actions, and remaining disagreements are distinguished |
The protected slots are not a guarantee that every request fits. A request requiring more than thirty minutes needs a separate capacity discussion. Likewise, an urgent operational risk follows its existing response process instead of waiting for Thursday. The agreement changes routine coordination, not safety, release, or approval controls.
Before circulating it, Mina reads each term back and asks each person whether it matches their commitment. She removes a proposed sentence saying they now trust each other: neither accepted that description. Their operational agreement can be complete even while the relationship needs more work. They authorize the agreed terms to go to Omar, without adding their private preparation accounts.

Review a missed action without turning the meeting into a trial
At the fictional November 6 review, R17 has a current link, an explicitly accepted November 5 review slot, and comments recorded by its agreed completion time. R18 exposes a gap: Ben acknowledged the request but did not state a review time, and Asha treated the reserved Thursday slot as automatic acceptance. The review did not happen by her requested deadline. The case does not invent a production loss or treat this as proof that either person refused to cooperate.
Mina returns to the wording. The first agreement already distinguished acknowledgment from acceptance, but did not specify what Asha should do when a response remained incomplete. Both accept an addition: if no review time is agreed by the preceding workday at 15:00, Asha asks Ben directly; if it remains unresolved, they ask Omar to decide a feasible plan. This is their fictional working threshold, not a universal workplace deadline.
Ben accepts responsibility for making his next response explicit. Asha accepts responsibility for checking whether a slot was actually agreed. They do not rewrite R18 as timely reviewed. On November 6, Omar accepts a revised R18 review on November 9 after checking capacity with both employees. That is a new plan; the original missed deadline remains in the operational record. No one is required to concede a disputed motive to make the next step workable.
By November 13, the fictional R19 request includes the revised fields, Ben accepts the Thursday slot, and comments arrive within that accepted time. Both choose to continue the arrangement for another bounded period with Omar's capacity confirmation. One successful request does not demonstrate lasting trust or measured productivity improvement. R15's operational wording question remains with its designated content owner; this meeting never approved it.
Stop or change the route when impartial discussion cannot continue
Pause if someone withdraws consent, the conversation becomes threatening, or a new issue requires an authorized investigation or other formal route. Do not settle an allegation by asking both people to compromise on the facts. Follow the relevant organizational procedure and get appropriate advice about the concern. This guide cannot determine which reporting duties apply to an actual case.
If your own decision becomes the disputed issue, acknowledge that your role has changed. You may need another facilitator or a separate management decision. Acas's guidance on introducing mediation discusses training and external mediators where there is a conflict of interest. Borrow the distinction, not an assumption that any manager can provide the same service.
For your next step, assess suitability and your role before scheduling a joint discussion. If it can proceed, prepare a small factual agenda, seek explicit commitments, and compare the later work records with those terms. Keep a missed action or unanswered question open until there is evidence of its disposition. LandOffer.ai publishes this management guide; it does not provide mediation, investigate employees, or determine who should receive a workplace consequence.


