Disagreements at work often go back and forth. One person makes a point, the other responds defensively, and the discussion stops being productive. Eventually someone sends a 👍 and the thread goes quiet.
The conversation ended, but the disagreement didn't. Nothing was actually agreed, so the issue lives on.
On a tense thread, a thumbs up is not agreement - it is an escape hatch. It looks like closure, but it usually means "fine, whatever", and both people walk away with a different idea of what happens next.
Alex: Please don't deploy on a Friday afternoon again.
Sam: I don't see any problem
Alex: Please don't deploy on a Friday afternoon again because a bad deployment could cause the stress of fixing it on the weekend
Sam: Still don't see a problem, this was a little change
Alex: I have just checked with the CTO. Please please don't deploy on a Friday arvo.
Sam: 👍
❌ Figure: Bad example - The conversation went back and forth, ended on a 👍, and nothing was agreed - so it will happen again
This is a different problem to using 👍 as a status update. For reactions on everyday messages, see Do you keep your chat reactions meaningful?
A disagreement is only finished when there is:
Anything else is kicking the can down the road.
Figure: Ending a disagreement without an agreement or a follow-up is just kicking the can down the road
Often the other person is not going to die on this hill. They have reasons for preferring their way, but they can see the other point of view - they are just in a defensive mindset.
The way through is to name the disagreement, say why it matters, and ask for a straight answer.
"I can see we're not quite seeing eye to eye on this, and I know you've got your reasons for preferring the other way. But this one is important to me, and I'd like it done this way every time. Can you agree to that?"
✅ Figure: Good example - Names the disagreement, gives the reason, and asks for a yes or no
The value is that it forces a real answer. When someone says "OK, I'm not going to die on this hill - I'll do it your way from now on", that is an agreement worth having.
It also makes next time easy. Instead of restarting the whole argument, the conversation becomes "Hey, we agreed on this one" - which is a much shorter and friendlier discussion.
Sometimes the mindset isn't right. Emotions are running high, someone is being defensive, or it is the end of a long day. That is a bad time to force a resolution - but a great time to book one.
Bad: "Let's talk about it later."
Good: "I can see we're not seeing eye to eye on this one. It is an important one for me, so can we grab 15 minutes on Monday at 10am to sort it out?"
✅ Figure: Good example - A follow-up with a real time beats a vague promise that never happens
"Later" never arrives. Give it a time, send the invite, and let the other person cool off knowing the issue is not being swept away.
Tip: If a disagreement is going back and forth over IM, that is a strong signal it should be a call. See Calling - Do you call instead of IM when communication is not simple?
The goal is agreement, not surrender. Shutting the conversation down wins the exchange and loses the person - they will comply while it is fresh, then quietly go back to their own way later. Leaning on seniority has the same problem. It ends the discussion without ever getting a genuine yes.
"I'm going to have to pull rank on this one."
❌ Figure: Bad example - Rank closes the conversation, but leaves the disagreement intact
Explaining why it matters and then asking for agreement gets to the same outcome, and the agreement actually sticks.
Occasionally a follow-up conversation still ends without agreement. That is fine - but make the position clear in writing so nobody is surprised later. See Do you send a 'For the record' email when you disagree?
And once the dust settles, offer an olive branch. See Conflict - Do you fix problems quickly?