When two people on your team stop working well together, the manager’s instinct is often to give a speech about forgiveness and hope the air clears. It does not clear. The missed deadline, the sharp comment in the planning meeting, the credit dispute over the launch deck, those things sit in the room until someone runs a structured conversation about them.
This piece is a playbook for that conversation. It assumes you have two reasonable adults and one broken thing between them. It does not apply when the situation is bullying, harassment, or sustained toxic behavior aimed at one person. We will cover that boundary before getting into the steps.
What “repairing trust at work” actually means
Repairing trust at work is the structured process a manager runs after a specific incident has damaged the working relationship between two people on a team. It is a sequence: diagnose what broke, decide whether the situation calls for repair or escalation, run a 1:1 conversation between the two people with a clear shape, reset the working agreements between them in writing, and then follow through for four to six weeks until the new pattern holds. The goal is a working relationship that holds weight again, not a feelings ceremony.
Grudges are not free. Two people who avoid each other re-route work, duplicate effort, withhold information from meetings, and pull a third person in to relay messages. The cost shows up in cycle time and rework long before it shows up in an exit interview. The manager who runs the repair early saves the team weeks of dragging.
Step 1: Diagnose what actually broke
Before you do anything, name the specific thing that broke. Vague diagnoses produce vague conversations. In our experience working with managers across 40+ organizations, almost every workplace rupture falls into one of five categories:
- Commitment: someone said they would do something and did not do it, or did it late without flagging
- Respect: someone spoke to or about someone else in a way that landed as dismissive, sarcastic, or sharp
- Fairness: workload, opportunity, or recognition got distributed in a way one person experienced as unjust
- Communication: information that one person needed did not reach them, or reached them too late to act on
- Credit: someone’s contribution got attributed to someone else, or their name went missing from work they did
You diagnose by talking to both people separately first. Ten minutes each. You are not gathering evidence for a verdict. You are figuring out which of the five categories the rupture sits in, because the repair conversation is shaped by the category. A commitment break needs a different conversation than a credit dispute.
Scenario: Maya and Daniel
Maya leads design on the growth pod. Daniel is the PM. In Tuesday’s planning meeting, Maya said “we’d be done already if PM had given us the brief on time” in front of six people. Daniel went quiet, finished the meeting, and has been routing decisions through the engineering lead since. The launch slipped a week.
The break here is two-layered. There is a respect break (the public comment) sitting on top of a real communication break (the brief was in fact late). If you only address the comment, Daniel feels defended but Maya feels unheard. If you only address the brief, Maya feels unheard about the public moment. Both go in the diagnosis.
Step 2: Decide repair or escalate
Repair conversations assume two people who are roughly peers in the dynamic and one specific incident or pattern of small incidents. They do not work, and they cause active harm, when the situation is actually a power imbalance or a pattern of targeting.
Use this table when you are unsure.
| Situation | Repair conversation | Escalate to HR |
|---|---|---|
| One sharp comment in a meeting, both people otherwise functional | Yes | No |
| Missed deadline, blame deflected sideways once | Yes | No |
| Credit dispute on a single piece of work | Yes | No |
| Repeated demeaning comments aimed at one person | No | Yes |
| Pattern of exclusion, public mocking, or undermining | No | Yes |
| Comments touching protected characteristics (race, gender, disability, etc.) | No | Yes |
| Threats, intimidation, retaliation after someone raised a concern | No | Yes |
| Manager-to-report dynamic where the report is the one harmed | Usually no | Usually yes |
If the situation falls on the right side of that table, do not run a repair conversation. Repair frames the harm as mutual, and when one person is being targeted, that framing makes things worse. Read our manager’s guide to workplace bullying for how to recognize the pattern and bring HR in cleanly, and our note on spotting toxic behavior for the patterns that should never be reframed as a personality clash.
Step 3: Run the 1:1 repair conversation
Once you have diagnosed and confirmed this is a repair situation, you bring both people into one room (or one call) with you. Forty-five minutes. Door closed. No notes shared outside it.
The shape is four moves, in this order. Skipping any of them is the most common reason these conversations fail.
Acknowledge
Each person says, in their own words, what happened from their side. You are not refereeing the facts. You are making sure both versions are on the table before anyone tries to fix anything. Most failed repair conversations skip straight to fixing.
Manager’s job here: keep it specific. “Tuesday’s planning meeting, when the brief came up.” Not “communication issues lately.”
Impact
Each person says what the incident did to them. Not what they think the other person meant, what it did. “I shut down for the rest of the meeting.” “I felt set up to fail because the brief was actually three days late.”
Impact is the move people most want to skip because it feels exposing. It is also the move that most often shifts the room. When Daniel hears that Maya was running on three days of weekend work because the brief landed Friday night, the meeting comment stops looking like character and starts looking like pressure leaking. When Maya hears that Daniel went quiet for a week because the comment landed in front of his peers, the comment stops looking like a throwaway line.
Intent
Each person says what they were actually trying to do. This is where most repair happens. Almost no one in a normal workplace is trying to harm a coworker. They are trying to ship the thing, protect their time, look competent, or stay out of a fight. When intent gets named, the other person can usually hear it, even if they still think the behavior was wrong.
Manager’s job here: do not let “I didn’t mean it that way” become a dismissal of impact. Both are true. The impact happened and the intent was not malicious. Hold both.
What changes
Each person says one specific thing they will do differently. Not feelings, behaviors. “I will raise concerns about the brief in our 1:1, not in planning.” “I will flag brief delays by Thursday end-of-day, not Friday night.”
You write both commitments down in front of them. That document becomes Step 4.
This is the conversation worth rehearsing with constructive feedback principles and active listening before you walk in. The structure is simple. Holding it under pressure when one person gets defensive is not.
Step 4: Reset the working agreements
The repair conversation produces commitments. Step 4 is making them visible and mutual, not floating in the air where deniability lives.
Write down three to five working agreements between the two people. Send them to both, copy yourself. Examples for the Maya and Daniel case:
- Briefs land in the shared folder by Thursday 5pm. If a brief will slip, the PM messages the design lead by Wednesday with the new ETA.
- Concerns about cross-functional work surface in the Monday 1:1 between Maya and Daniel, not in planning meetings.
- If something breaks between us mid-week, we Slack each other directly within 24 hours, not the manager first.
- We both attend the Friday team retro and surface anything that is still bothering us there.
The agreements are not policy. They are this pair’s contract for how they work together for the next six weeks. They are reviewable. They are also the thing the manager refers back to in Step 5 when one of them slips, because slips are normal and the agreements are how you talk about them without re-litigating the original incident.
This is the same principle as how managers and employees build trust at the team level, scaled down to a two-person reset.
Step 5: Follow through for four to six weeks
The repair conversation is the easy part. The follow-through is what makes it stick. If the manager runs Steps 1-4 and then disappears, the relationship reverts within two weeks. We have seen it happen often enough to call it the default outcome.
What follow-through looks like in practice:
- Week 1: Check in with each person separately. Five minutes. “How did the agreements hold this week?” Not “how do you feel about each other?” Behavior, not sentiment.
- Week 2: Notice and name one thing each person did that honored the agreement. Out loud, in front of them, ideally in a small moment they will remember. “Daniel, the Wednesday heads-up on the brief was exactly the thing.” This is not flattery, it is reinforcement.
- Week 3-4: If a slip happens, address it within 48 hours, in private, against the written agreement. “We agreed Thursday 5pm. The brief landed Friday afternoon. What got in the way?” The agreement does the work. You are not the parent.
- Week 5-6: Run a short joint check-in with both people. Fifteen minutes. “Are the agreements still right? Anything to tighten or drop?” Most pairs adjust one or two clauses and the rest holds.
If, by the end of week six, one person has missed three or more agreement points while the other has held their side, the repair situation is over. What you have now is a performance or fit conversation. That is a different conversation, and it gets handled through your normal performance process. The point of the six weeks is to find that out clearly, not to drag a broken relationship into a third quarter.
How Merlin helps managers run this
The repair conversation is the part most managers privately dread. Holding the structure (Acknowledge, Impact, Intent, What changes) under pressure is hard, especially when one of the two people gets defensive or starts crying or goes silent.
Merlin, the AI coach inside Risely, lets a manager rehearse the specific conversation before walking into it. You describe the situation, the two people, what each of them tends to do under stress, and Merlin runs the rehearsal as a roleplay. You practice the opening, the pivot when someone deflects, the way you close the loop without letting one person off the hook. Across 15,000+ coaching conversations, the rehearsal pattern is the most-used capability for first-time and second-line managers running their first formal repair conversation.
Risely covers 83 workplace skills, and the cluster around conflict, empathy, and direct conversations is where managers see the fastest gains, with average skill improvement of 26% over 12 weeks.
Bring it back to the team
Two people repairing well is not a private win. It changes what the rest of the team thinks is possible. When a team sees that a sharp comment in planning got addressed, that the brief problem got named, and that both people are still functional and shipping, the threshold for raising the next small thing drops. That is a team where work surfaces early instead of seeping out in retros six weeks later.
The manager’s job is not to make the team a place where nothing breaks. Things break. The job is to make it a place where breaks get repaired structurally, not papered over with a speech about kindness.
If you have a repair conversation on your calendar this week, try Merlin free for 14 days and rehearse it before you walk in.