The apology is the shortest part of repairing a relationship at work after a blowup. It takes a couple of minutes to say out loud. But whether those minutes count is decided by what happens around them. Before the apology there’s the day or so when you work out what you’re actually sorry for. After it come the weeks when the other person watches to see whether anything has changed.
This post is for one of the two people in the argument. The other person might be a colleague you share work with, or it might be your manager. There’s a good chance you both said something you’d take back if you could. But there’s also a fair chance that yours is the line other people remember. If things are still heating up and you need to cool the conversation right now, our guide to de-escalation techniques at work covers the moment itself. If you manage the two people who fell out, the manager’s playbook for repairing trust on a team is a better fit. Everything below starts once the shouting has stopped.
We’ll start with how soon to apologize. Next is what the apology needs to include, along with what one well-known study can and can’t tell you about that. After that comes a worked example where the reply only half lands. We then look at what changes when the person is your manager and what to do if they aren’t ready to forgive you. The last part is about what the following weeks have to look like.
How soon should you apologize after a blowup?
There are two well-known pieces of advice on timing, and at first glance they seem to pull in opposite directions.
The first comes from Melbourne Business School’s article on a 2024 paper by Professor Mara Olekalns and Brianna Barker Caza. The paper is a conceptual review rather than an experiment, and part of what it draws on is research into marriages. Much of Olekalns’s advice is about getting out of your own head. She warns against what she calls “self-immersion”, which she describes as the state “where I dwell on what happened and really analyse the negative impact on me”. She told MBS that this state is “detrimental to being able to repair a relationship and move on.” So what she recommends instead is distance: “Stepping back and viewing the situation as if you are an external observer reduces the intensity of your feelings and helps you get perspective.” She also backs sleeping on it before you send that angry email. But the article doesn’t tell you to wait long, because it also stresses speed. One of its steps is headed “Act promptly to re-establish a sense of ‘we’”. The MBS summary adds that “The speed with which you move to reaffirm the relationship is also critical in order to be able to push through the conflict.”
The second is an HBR tip adapted from Sabina Nawaz. It says: “Set up a one-on-one meeting with the other person. Your initial goal is simply to apologize, so specifically acknowledge what you did wrong.” It goes on to suggest saying you’d like to talk through what happened. Only after that does it add: “(If emotions are still running high, it may be better to pause the discussion here for a day or two.)”
So the pause comes after the apology and the request to talk. It applies to the longer conversation about what went wrong, not to the apology itself. That means the two pieces of advice are closer than they look. Both say to get some distance from your own feelings first and then make the first move without dragging it out.
Our suggestion puts the two together in three steps. It’s a judgment from reading the two sources side by side, not something either of them tested. The first step is to cool off on your own, and above all to stop rehearsing the argument. If you catch yourself drafting the perfect comeback in the shower, that’s the self-immersion Olekalns is warning about. The self-control you need at that point is the same kind covered in our guide to emotional self-regulation at work. The second step is to open the door quickly with a short acknowledgment and a request for a proper conversation. Our rough rule is that this means the same day or the next working day. The third step is the full conversation, which you have once you can both listen. That might be later that week.
People often wait for the other person to apologize first, especially when both sides said something. That’s understandable, but it rarely helps because you only control your own part. If you hold yours back until they offer theirs, the apology turns into a trade. When neither of you is willing to go first, nobody does.
The message that sets up the meeting can be written. But the apology itself is better said than typed, ideally face to face or at least on a call. There are two reasons for that. The first is that a written apology can be forwarded, reread and picked apart. The second is that the study in the next section looked only at apologies that were described or written down, never spoken. Its authors pointed out that tone of voice and body language could change how a spoken one comes across. Where you meet matters too. Amy Gallo covers this in an HBR video episode on repairing a broken relationship at work, where she says to “be sure it’s on neutral territory, not at one of your desks or offices.” If the blowup itself happened in Slack or over email, our post on disagreeing in writing explains why written arguments tend to escalate the way they do.
What does an apology need to include?
If you want to repair a relationship at work, the apology has to contain more than “sorry”. Some of the clearest evidence on what else it needs comes from a 2016 study by Roy Lewicki, Beth Polin and Robert Lount. It was published in Negotiation and Conflict Management Research. The authors broke an apology into six parts.
An expression of regret is the plain “I’m sorry”. It’s the part that tells the other person you feel bad about what happened. An explanation of what went wrong tells them why it happened, which helps them make sense of it. An acknowledgment of responsibility says it was your doing, not the situation’s. A declaration of repentance is the promise that you won’t do it again. An offer of repair is something concrete you’ll do to put it right. Finally, a request for forgiveness asks them to let it go.
The study design matters, so here it is in full. There were two experiments with 755 people in total. Both asked participants to imagine they were the manager of an accounting department hiring a new employee. The candidate had filed an incorrect tax return at a previous job, and he apologized when he was confronted about it. The 333 adults in the first experiment were recruited online. They were told whether that apology contained one, three or all six of the parts. The 422 undergraduates in the second experiment read the apology itself instead. It was written out with anywhere from one to six of the parts. Both groups rated how effective, credible and adequate it was.
The paper’s abstract reports that apologies with more parts were rated as more effective than apologies with fewer. Some parts also mattered more than others, and that ranking comes from Ohio State’s release on the study. Lewicki told Ohio State that “the most important component is an acknowledgment of responsibility. Say it is your fault, that you made a mistake.” The release puts the offer of repair next, and Lewicki explained why it carries weight: “One concern about apologies is that talk is cheap. But by saying, ‘I’ll fix what is wrong,’ you’re committing to take action to undo the damage.” The request for forgiveness came last in both experiments. “That’s the one you can leave out if you have to,” Lewicki said.
The middle three are regret, explanation and repentance, and they’re harder to rank. The Ohio State release calls them essentially tied for third. But the Association for Psychological Science’s write-up lists the explanation among the three most important. Because the two write-ups disagree, this post doesn’t rank them.
The study has limits, and they’re large. Nobody in it was apologizing to a colleague, and nobody had just had a blowup. Instead the participants were judging a job candidate’s apology for a tax mistake, either from a description of its parts or from a written statement. So the study measured how good the apology seemed to people who weren’t personally hurt by it. It didn’t measure whether anyone actually forgave anyone. The APS write-up also notes the authors’ own caveat: “this study relied on written apologies, but tone of voice and body language could have a huge impact on the perception of a spoken apology.” All of that makes the ranking a guide to what to put in and what you can safely leave out. It isn’t proof that your apology will work.
The study also split the tax mistake two ways. For half the participants it was a matter of competence (the candidate didn’t know the tax rules). For the other half it was a matter of integrity (he filed it wrong on purpose). The abstract reports that apologies after competence failures were seen as more effective. But the release says the value of each of the six parts was the same for both kinds. Carrying that over to a workplace argument is our inference from a hiring scenario, not a finding about colleagues. Still, it fits ordinary experience. If you were sharp or curt, that’s closer to a competence slip. But you may have done something that made the other person doubt your honesty or your motives, such as complaining about them behind their back. If so, expect the apology to do less of the work and your behavior afterward to do more.
The study didn’t test the order of the parts, so the order is up to you. We’d start with responsibility because that’s what the other person is listening for. Keep the explanation to a single sentence after that. If it comes first or runs long, it sounds like you’re building a case.
We think two phrases do the most damage. The first is “I’m sorry, but”. It turns the apology into the preamble for a defense, because once the other person hears the second half they stop listening to the first. The second is “I’m sorry if you were upset”. It makes their reaction the thing in doubt, which gives them something to defend. So now they have to argue that they had a right to be upset before they can hear anything else. Asking for forgiveness has a quieter problem. It hands the other person a job in the first minute of the conversation, when they haven’t had time yet to decide how they feel. That’s probably part of why it’s the one you can leave out.
If you still think your point was right
Apologize for what you did and how you said it, and keep your view on the actual issue for a separate conversation later. This is our judgment, not something the study tested. Our guide to giving feedback to your boss walks through how to own the delivery without taking back the point. A blowup where you both said things adds one more pull, which is the urge to mention their part too. Leave it out. Once your apology includes what they did, it stops being an apology and becomes the opening of round two.
One blowup, one apology, and a reply that only half lands
The case below is illustrative. Elliot and Clara are made up, and so is their company. But the shape of what happens is common.
Elliot and Clara are coordinators at a mid-sized professional services firm. This year they’re running the annual client conference together. Clara owns the vendors and contracts, while Elliot owns the program and the speakers. Two weeks before the event, the caterer’s final invoice comes in well over the quote. Clara had approved an upgraded menu without checking how it changed the per-head price. Something has to go if they’re going to stay within budget, and the obvious candidate is the dinner for speakers.
That came up in the Monday status meeting, with six people on the call. Elliot had seen the new total ten minutes earlier. Clara explained the overrun, and Elliot’s reply was blunt: “If you’d actually read the numbers before signing, we wouldn’t be canceling dinner on our speakers.” Clara came back with “That’s rich from someone who’s left the venue’s emails sitting for a week.” “Fine. I’ll do your half of the job as well, then,” Elliot said. The meeting moved on in silence.
Both of them said something they regretted. But Elliot’s line was the sharper one and the more public, because he’d called Clara careless in front of three colleagues and her manager. He’d also made it about her competence rather than about the budget.
The day after
Elliot spent most of Monday evening building a defense. He went back through the shared inbox and found two other occasions when Clara had approved something without looping him in. He drafted the explanation he’d give if anyone raised it, and it sounded calm and devastating in his head. He went to bed convinced the meeting had been her fault.
That’s the self-immersion Olekalns describes. It was making the next step harder, not easier. On Tuesday morning a simple question broke it: what had the other four people on the call actually seen? They hadn’t seen the shared inbox. All they’d seen was him make a cutting remark about a colleague’s competence in front of her manager. His “evidence” didn’t change any of that for someone looking in from outside. All it did was make it more likely he’d say it all again.
The message that opened the door
Elliot sent Clara a direct message around lunchtime on Tuesday: “Clara, I was out of line in Monday’s meeting and I’d like to apologize properly. Have you got twenty minutes tomorrow? I could meet you in the small room on four, or we could walk to get coffee.”
He kept it short on purpose, because a longer message would have started the apology in writing. He wanted to say it to her face. He named the meeting so she wouldn’t spend the afternoon guessing what he wanted. He also suggested two places that belonged to neither of them, so she wouldn’t have to come to his desk or sit through it at hers. She replied an hour later with “Coffee, 10am,” and nothing else.
The apology
They walked to the coffee place around the corner. Elliot started with responsibility, because that was the thing Clara would be listening for. “On Monday I said, in front of everyone, that we were canceling the speaker dinner because you hadn’t read the numbers,” he began. “That was wrong of me, and it was worse to do it in that meeting. It made you look careless to your manager and three other people, and that’s on me.”
He named the exact words and the exact setting so she wouldn’t have to wonder which bit he meant. He also named what it cost her, which was looking careless in front of her manager. That was the real damage, and leaving it out would have meant pretending otherwise.
He followed it with one sentence of explanation, and only one: “I’d seen the new total ten minutes before the call and I took it out on you.” That sentence says why it happened without suggesting the reason excuses it. Only after that did he say, “I’m sorry.”
The offer of repair was something he could actually do, and something that matched the damage. Because the damage had been public, the repair would be too: “On Thursday’s call I’m going to say that I was out of line on Monday. I won’t go into the budget, just that.” He followed that with the promise not to repeat it: “And if I’m worried about something you’ve signed, I’ll come to you first, not raise it in front of the group.”
He had planned one more line and cut it on the walk over. The version in his head ended with a closing thought: “I think we both said things we didn’t mean.” It sounded fair. But it would have turned the apology into a negotiation in its last sentence. It would also have reminded Clara of her own remark just as he was asking her to forget his. He also left out any version of “Are we OK?” because she hadn’t had time to decide yet. Asking would only have put her on the spot.
The reply
Clara listened until he’d finished. “Thanks,” she said. “I appreciate you saying that, and Thursday would help.” She paused. “But honestly, Monday isn’t the part that bothered me most. You’ve been telling people for two weeks that the budget’s a mess. I heard it from three different people before you ever said it to me.”
This was the part Elliot hadn’t prepared for. He’d apologized for one remark, but she was hurt by a pattern he hadn’t thought of as part of the problem. His first impulse was to explain that he’d only been venting and that the budget really had been a mess. He didn’t say either. Instead he said, “I didn’t know you’d heard that. You’re right, I’ve been complaining about it to other people instead of talking to you, and I’ll stop.”
He didn’t repeat the apology with more feeling or ask whether they were all right now. Both would have made the conversation about his discomfort rather than her complaint.
Clara had one more thing to add: “I still think the menu was the right call, for what it’s worth.” Elliot didn’t agree, but he didn’t argue either. He said he’d like to talk about how contract sign-off worked between them, just not today. She agreed to find a time next week. They left that disagreement open on purpose, because it’s a real question about how they split the work. It was never going to be settled on the walk back from coffee.
On Thursday’s call he said what he’d promised, briefly and a bit awkwardly. Someone made a joke about it, and Clara didn’t say anything.
The apology dealt with Monday. But it didn’t touch the two weeks of grumbling, and those had done more damage. Clara was polite for the rest of the week, though a little more formal than usual. She also copied their manager on her next two emails about the budget, which she’d never done before.
What if the person you blew up at is your manager?
None of the research above looked at apologies to a manager, so what follows is our judgment rather than anything a study tested. Most of the advice carries over. You still cool off first and say what you did and what it cost. You still keep the explanation to a sentence and offer something concrete. But a few things change, because your manager has power over your work and you don’t have power over theirs.
You ask for the meeting, and the request should say what it’s about. If a vague “Can we grab ten minutes?” sits in your manager’s inbox all afternoon, they’ll wonder whether you’re about to resign or complain. So say it’s about the conversation that went badly.
What you offer is a change in how you’ll behave, not a plea about the relationship. A manager can hear “I’ll raise concerns with you one to one, not in the team meeting” and hold you to it. But “I really want us to have a good relationship” asks them for reassurance in the moment, which gives them a job to do.
Keep the explanation shorter than you would with a peer. Your manager decides your rating and your projects, so a long explanation can sound like an excuse to them. They’ll remember the excuse more than the apology.
If your manager waves it away with “It’s fine, forget it,” take them at their word in the room. But let your behavior over the next few weeks do the rest, because a dismissal can mean anything from “it really is fine” to “I don’t want to talk about it with you.”
There are two things to avoid. Don’t recruit colleagues to tell your manager you’re sorry, and don’t go over your manager’s head as a first move. Both make a private disagreement public. The blowup may also have been about a real concern you still hold, such as your workload or how your work is reviewed. If so, apologize for how you raised it and keep the concern itself for a separate conversation. Our guide to giving your boss feedback without the fallout covers that conversation.
The power gap cuts one more way. When it’s a peer, you’re both equally free to walk away from the repair. When it’s your manager, you can’t make the repair happen. All you can do is make it easy for them to meet you.
What if they don’t accept the apology?
“Not accepted” can mean three different things, and it helps to know which one you’re dealing with.
The first is not ready. The person heard you, but they’re still angry or still deciding what they think. They might say “OK” and leave, or “I need some time.” That’s a reaction on their timeline, not a verdict. The second is partial, like Clara’s reply. They take part of what you said and tell you the real problem is something else. The third is a clear refusal. They tell you they don’t accept it, or that they don’t want a working relationship beyond the minimum.
The same things make it worse in all three cases. Repeating the apology sounds like you’re trying to wear them down. Asking whether they’ve forgiven you yet puts the job back on them. Explaining again what happened reopens the argument you just apologized for. Sending a third person to carry the message turns a private matter into a public one, and it tells them you couldn’t wait. Venting about their reaction to other people is the quickest way to undo the whole thing, because it tends to get back to them. That’s what happened when Elliot’s grumbling got back to Clara.
What helps is less dramatic. Let the first conversation stand. Keep any commitment you made, and keep it visibly. The rest is ordinary, useful contact. That means answering their questions well and sharing the thing you’d have shared anyway. It also means turning up prepared to the meetings you’re both in. Gallo passes on advice from Brian Uzzi in the same HBR episode. His point is that you shouldn’t try to persuade someone you’re trustworthy by talking about it. You should show them instead, and ordinary contact is how you show it. A bit of empathy helps here too, because their pace says more about how long they take to trust a change than about the quality of your apology.
How long should you wait before raising it again? Gallo says, “Repairing relationships can take time,” but no source we read gives a number. So our rough rule is to give it at least a couple of weeks of steady, normal behavior before you ask for another conversation. When you do ask, make it about how you work together from here and not about the apology.
The relationship may still be getting in the way of the work after that. If the two of you can’t sort it out directly, it may be time to involve a third person. That might be the manager you share, or HR if your company has a route for this. Bringing someone in isn’t an admission of failure, and it doesn’t make the third person a judge of who was right. It just gives the conversation a structure that the two of you couldn’t hold on your own. Our posts on how conflict mediation at work runs and on conflict between peers when nobody has authority cover what that looks like.
Some working relationships don’t go back to what they were. We don’t think that’s the same as failing, because a relationship can be repaired enough for two people to work well together. They can have clear handoffs and civil meetings without becoming friendly again.
What repair looks like in the weeks after
The apology gets you a hearing. But what you do over the following weeks decides whether the relationship actually recovers. Amy Gallo makes the same point in the HBR episode, drawing on the psychologist Susan David: “One coffee or one Zoom call isn’t going to fix everything. It’s typically the small everyday stuff that adds up to bigger change.” She goes further: “Sitting down and talking is helpful, but it’s not where the real work happens. You need to make an effort to change the tone and tenor of your everyday interactions.” That’s practitioner advice rather than research, but it matches a line from the abstract of Olekalns and Caza’s paper on resetting relationship trajectories. “Coworkers’ responses to a relationship threat determine whether relationships are repaired or whether the threat leads to a loss of commitment, lowered satisfaction, and increased negative affect,” the abstract says. So what counts is how people respond over time, not only the first response.
The weeks after mostly come down to a few things you keep doing.
Keep the specific commitment you made, and keep it where the other person can see it. If you promised to raise concerns privately first, the first concern you have is the test. It’ll probably come sooner than you’d like.
Change one small, recurring behavior rather than announcing a new you. The other person will notice a pattern change over several weeks, but they won’t believe a speech about it.
Don’t re-argue the original dispute, and don’t bring the apology up in a way that implies they owe you something for it. “I did apologize, you know” undoes most of what the apology did.
Keep a private note of what you said you’d do and what you actually did. It’s for you, not for them. It’s useful because memory is generous to the person doing the remembering, and the note will show you honestly whether you’ve kept your side.
Stop narrating the repair to other people, too. Telling colleagues how hard you’re trying keeps the blowup alive in their minds, and it often gets back to the person you’re trying to repair things with.
Elliot’s real test came in the second week. The venue sent a revised quote for audiovisual equipment, and it was over budget again. Somebody asked about it in the team channel before either of them had answered. The old reflex was right there: a quick, slightly sarcastic reply that would make it clear whose problem this was. Instead he messaged Clara directly: “Saw the AV quote. Do you want to reply in the channel, or shall we look at it together first?” She wrote back: “Together, 2pm?” They worked out a cut in twenty minutes.
That went well, but the rest didn’t resolve as neatly. Clara opened the budget item in the next status meeting with “Elliot and I have already discussed this.” Her tone was a little cooler than it needed to be. The conversation about contract sign-off was the real disagreement from the first day. It was moved twice and still hadn’t happened by the time the conference was over. The everyday contact between them was much better. But the thing they actually disagreed about was still waiting.
That week mattered more than the apology did, because the apology only told Clara what Elliot intended to do differently. The AV quote showed her whether he would. That’s why our rough rule is to give it about a month of consistent behavior before you judge how the repair is going. Some relationships need longer. If the blowup turns out to be one of several with the same person, our guide to dealing with difficult coworkers is the better place to start.
When an apology is the wrong move
Everything above assumes two people who both behaved badly in a single incident. It also assumes they both want to keep working together, at least at some level. When that isn’t the situation, the advice changes. What follows is our judgment.
If the other person was abusive or threatening, an apology is the wrong tool. That holds even if you said something sharp in response, and it’s just as true if they were harassing or discriminatory. What you should do instead is stop engaging with them one to one and keep a factual record of what happened and when. You can then take it to HR or your manager through your company’s process, if it has one. Don’t try to repair your way out of it.
If you’re apologizing to a manager who might use it against you, be careful about what you put in writing and what you concede. An apology you offer freely can be quoted back to you later. That’s why it’s worth keeping a note of what you said and what they said. If the underlying issue is a real concern about how you’re being treated, raise it through a proper route rather than a private apology.
If this is a pattern rather than one incident, an apology on its own won’t fix it. You can apologize for the latest blowup, but the next one will come along on schedule. Our guide to dealing with difficult coworkers looks at repeated behavior.
Someone may demand an apology as a kind of performance for things you didn’t do. If so, apologize only for your part. Saying sorry for the rest doesn’t settle anything, and it gives the other person a version of events you don’t agree with.
If you were the one wronged and the other person hasn’t owned any of it, you may need a boundary rather than an apology.
The last limit is the evidence itself. The study at the center of this post was about a job candidate’s apology for a tax mistake, judged by people who’d been told about it or read it on paper. None of the sources we read tested apologies between colleagues after a blowup. So the ranking is a sensible guide to what to say, but it isn’t a promise about how the other person will respond.
Before the conversation
If you have a conversation like this coming up this week, decide two things before you go in. The first is which of the six parts you’ll actually say. That includes how you’ll name what you did in one sentence that doesn’t mention them. The second is one thing you’ll do differently in the first week after. Make it small enough that you’ll really do it, and visible enough that the other person will notice. If you want a sense of how you handle disagreement more generally, the conflict resolution assessment takes a few minutes.
The hardest moment is usually the first reply. You’ve said your piece and they say something cool or unexpected, so the pull to defend yourself is strong. That’s why it’s worth practicing before it counts. Merlin can play the other person so you can try your opening and hear a cold reply back. It works natively in Slack or Microsoft Teams, or on the web. What you tell Merlin stays between you and Merlin. Your conversations are private. If what happened involved harassment or abuse, take it to HR or the right person at your company rather than a practice conversation.