How to repair a work relationship after a disagreement
Your line got a laugh at her expense and she's been closed for six weeks. How to name the moment, apologise for the right thing, and propose one rebuild step.
Six weeks ago you and Ana disagreed sharply in an architecture review. You won the decision. Somewhere in the middle of winning it, you said her design belonged in 2015, and the room laughed. Two of her juniors were in that room.
Since then she’s been impeccable and closed. One-line replies. Meetings declined with plausible reasons. The roadmap your two teams share is quietly fraying, and nobody has said anything, because nothing anyone could point to has happened. She’ll give you twenty minutes with a hard stop. That’s the whole window.
Why this one is hard
It’s hard because you can’t tell what you’re apologising for until you’ve already guessed. The obvious guess is the decision, and it’s the wrong one. If you walk in and soften the architecture call to buy back some warmth, you’ll have given up something that was right and she’ll have no more respect for you than when you started.
It’s also hard because she’s going to give you nothing to work with. No anger, no accusation, no opening. A cooled peer is harder than a furious one, because there’s no heat to respond to. You have to supply the moment yourself and say it plainly, in a room where she’s going to let it hang.
Before you walk in
The moment, exactly. Not “the review.” The line, word for word, the laugh, and who was in the room. If you can’t say it precisely, you’re not ready, because she can.
The apology, for the thing you did. You’re sorry you said it and that the room laughed at her in front of her team. Not sorry “if it came across badly.” Not sorry for “how it landed.” Those apologise for her reaction, and she’ll hear the difference.
One rebuild step. Something concrete she can accept or decline in a sentence. A joint review of the integration next week, which you’d open by crediting the parts of her design you kept. Not a coffee, not a reset. A piece of work.
The line you won’t cross. You won’t reopen the decision. The design stays as decided. If the only way to get warmth back is to trade the architecture for it, you leave without the warmth.
Your opening line
The moment, the apology, the boundary, the ask.
In the architecture review six weeks ago I said your design belonged in 2015, and the room laughed, with your two juniors in it. That was a cheap line and I’m sorry I said it. I’m not here to reopen the decision. I’d like to propose one thing to get us working properly again.
It names what you did before she has to. It separates the line from the decision so she can’t hear the apology as a negotiating move. And it tells her the meeting has a shape and a short one.
The version to avoid:
I feel like things have been a bit off between us since the review…
Vague, and it asks her to name what you did. She’ll say things are fine, and she’ll be done.
The three pushbacks you’ll hear
“We’re fine. Is that it?”
A closed door, politely. The word “fine” is doing the work of ending the meeting.
We’re civil, which isn’t the same thing. You’ve declined my last three meetings and the shared roadmap has slipped twice. I’d rather fix the thing I did than ask you to keep pretending it’s fine.
Name the evidence, briefly, and don’t ask her to agree about her feelings. You’re describing the calendar, not her.
“Noted. What’s the next item?”
The apology left hanging, unclaimed. Don’t say it again louder, and don’t ask whether she accepts it. That’s asking her to do the work.
The next item is the one thing I’m asking for. A joint review of the integration next Thursday, which I’d open by crediting the parts of your design we kept. Yes or no is enough.
A concrete step she can take without warming up. It respects the transactional frame she’s chosen instead of fighting it.
“What exactly do you think you’re apologising for?”
She’s testing whether you know, and she’s going to grade the answer. “For the disagreement” fails. “For how it came across” fails worse.
For the line and for the laugh, in front of the two people who report to you. Not for the decision, which I still think was right, and not for how you took it.
Exact, and the decision stays separate. If you pass this, you’ll usually find out what the six weeks were about.
Where you stop
The good ending sounds like: fine. Joint review next Thursday, and you can open it by crediting the parts of my design you kept. That’s where we restart. Take it. Confirm the date and leave. Don’t add a coffee, don’t add “I’ve missed working with you.” She offered work; accept work.
In the good version she may tell you what it actually was. She’d half-agreed with you on the decision. It was the laugh, in front of her two juniors, that she can’t unhear. That’s the thing a good conversation surfaces, and it only comes out if you apologised for the right thing first. If she says it, don’t say you know. Say you should have seen it.
If it stalls, say this once:
I’m not asking you to like me. I’m asking for one review where I say, in front of your team, what I should have said then.
If she says we don’t need to be fine, we need the integration shipped, use the leads channel, then use the leads channel. Don’t push past it. Be precise and generous there, every time, and put the credit for her design in writing in the next roadmap doc whether or not she asked for it. Some repairs are done in the open over months, not in a room in twenty minutes.
Afterwards
Send two lines that evening: Thursday confirmed, and the list of the parts of her design that survived into the final architecture, so she can see you mean something specific. Then open Thursday’s review with exactly that list, in front of her team, before anything else.
Then make the next one easier: before any review where you expect to win, write down one thing you’ll credit the other side with, out loud, before you argue. Most of the damage in a disagreement happens in the ten seconds after you’ve already won.