How to clear up a misunderstanding at work

When someone has misread your message, say their version back to them before you say yours again. That restatement is what ends the thread. Almost everybody does the opposite and leads with the correction, which is why these threads run for days.

This feels backwards, and I resisted it for a long time. Being misread is annoying in a specific way: you can see the exact sentence they skipped, and the obvious fix seems to be pointing at that sentence harder.

Pointing harder does not work. I have tested this more than I would like.

Why correcting the record first makes it worse

Leading with your correction fails because the other person is not reading your words yet. They are reading their reading of you, and anything new gets sorted into it.

Once someone believes you asked for the whole thing to be redone, your clarification arrives as a retreat. Your evidence arrives as lawyering. Your calm tone arrives as condescension. None of that is fair, and all of it is what happens.

"What I actually said was" is the worst opening in the genre. It converts a confusion into a contest about who read carelessly. You might win that contest. You will still be misunderstood, and now they have a second reason to be annoyed with you.

There is a quieter thing going on across the table. A person who has misread you is often already half aware of it, and a reply built out of quotes forces them to defend a position they were two minutes from dropping. You can lose an argument by winning it too visibly.

Say their version back in their own words

A good restatement is one flat sentence saying what they think you meant, specific enough that they can correct it in a single line.

Skip the counselling phrasing. "So what I am hearing is" announces that a technique is being run on someone, and people feel the technique. Say the thing plainly instead. "You are reading this as me wanting the audit redone from scratch before Friday."

Make it the strongest version of their reading, not a weak one you can knock over. If your restatement makes them sound unreasonable, they will correct the restatement first, and now you are two arguments deep with the original one untouched.

If the message in front of you is angry rather than confused, the restatement is doing a different job: there it proves you read them, here it locates the sentence that went wrong.

What belongs in the restatement:

• The thing they believe you are asking for, in concrete terms.
• The cost they believe it lands on them.
• The motive they have attached to you, if you can write it without flinching.
• Nothing else, because the next person to speak should be them.

The motive line carries most of the weight. Almost no misunderstanding at work is really about the deadline or the scope; it is about what a person thinks the deadline says about how you see them, and that part never gets typed by anyone.

Often they correct your restatement and the whole thing dissolves before you defend a word of it. "No, I thought you wanted the client version pulled." Fine. Two lines, done, nobody had to be wrong out loud.

Restating is not agreeing

Saying someone's position back to them concedes nothing, and the fear that it does is why most people skip the step.

The worry makes sense on its face. Write their wrong version down in plain text and it sits there looking like an admission, especially in a thread with an audience. So put your correction in the same message, one line below. Restate, then correct. The order is the whole trick. Your side is still in there, it just lands second.

With an audience the restatement helps more, not less. Whoever states the other side accurately reads as the steadiest person in the thread, and that impression outlives any single point in the argument. It is a slightly unfair advantage. Take it.

I would rather be mistaken for agreeing for ten minutes than spend three days watching two people defend positions neither of them holds.

Correct one thing, not the whole history

After the restatement, fix exactly one belief: the one that, once it changes, makes the rest stop mattering.

Correction replies fail by trying to repair everything at once. Where the thread went sideways, what the third bullet meant, why your summary was accurate, why the timestamps are on your side. Each extra repair hands the reader a fresh thing to disagree with, and a long defense reads as a nervous one.

Cut before you send:

• Cut the sequence of who said what and when.
• Cut the screenshots and the quotes of your own earlier message.
• Cut any sentence whose real job is proving you were clear the first time.
• Cut the apology for their reading if you did not cause their reading.

That last one runs against the usual advice, which says to open with "sorry, I was not clear" and absorb the whole thing. Say it when it is true. When it is not true, it is a small lie about who caused what, and enough small lies of that shape give you a reputation for vagueness you will never see and never shake.

There is a true sentence that does the same warming work: "That is not what I meant, and I can see how the second paragraph got you there." It gives ground on the effect without lying about the cause.

The first draft of a correction is usually a defense with a clarification buried somewhere in the middle. Mine were, for years. So I type the defense out, because that is how I find the clarification, then take the calmer version in Unvent, which sends the clarification and leaves the case I was quietly building in the box where I typed it.

When it is not a misunderstanding

Some misunderstandings are disagreements in a costume, and you find out when your restatement gets confirmed and the argument carries on anyway.

You say their version back. They say yes, that is exactly the thing I object to. The confusion is gone and a real conflict is standing where it stood all along.

That is progress, and it is also where people panic, because a clean disagreement is harder to sit with than a messy misunderstanding, since a misunderstanding always carries the hope that everyone secretly agrees and only the wording went wrong, and letting go of that hope is what threads circle for days to avoid.

Name it anyway. "Then we do disagree about whether the audit blocks the release, which is a different conversation than the one we have been having." From there it is an ordinary disagreement, and those have a shape that works.

The sentence I cut most often from my own drafts is the one that says why. It is the longest sentence in the message, it feels like over-explaining, and it is the exact sentence that would have made the misreading impossible. I cut it because on the screen it looks like padding. Then I spend Thursday explaining it in a thread instead.