A correction that keeps the other person's dignity does one job: it puts the right information where the wrong information was sitting. Everything you add past that is about you.
Most corrections carry a second payload. The fact gets fixed, and underneath it a small flag goes up saying I noticed this, and I knew it before you did. The reader hears both. They usually answer the second one.
What a correction is for
A correction exists to stop someone acting on a wrong fact. That is the entire job, and it means some wrong facts are better left alone.
Before you type, ask what changes if you say nothing. If a person is about to build a plan on the wrong number, pay the wrong invoice, or repeat the wrong date to a customer, correct it. If the mistake is a wrong month inside a story that already ended, let it sit there.
A lot of corrections at work are hobby corrections. They cost the writer almost nothing. They cost the reader a bit of standing in front of people whose opinion they care about, and nothing downstream moves at all. We keep making that trade because being right feels like contributing.
Send it to the smallest room that fixes the problem
Audience does more damage than wording. Put the correction in the smallest room where the wrong fact can still cause harm, and no larger.
A private note fixing a number is a favor. The same words posted under a message a dozen people have already read is a performance, no matter how warm your tone was.
Correct in public when one of these is true:
- The wrong fact is in a document or thread that people will act on.
- Others have already seen it and would otherwise walk away holding it.
- The person asked the question in public and is waiting there for an answer.
- Saying nothing would read as agreement to everyone watching.
Everything else goes to one person, in one message. If you are correcting in the channel because it is faster for you, admit that to yourself and then don't.
There is a version of public correction that costs almost nothing, and it is the one that skips the diagnosis. Post the right number as information rather than as a reply to a person. The record gets fixed and nobody has to be the one who got it wrong.
Fix the fact, drop the ranking
Write the right version and stop typing. The part that stings is almost never the fact. It is the packaging.
Here is what to leave out:
- "Actually" at the front of a sentence puts a scoreboard in front of the information.
- Fixing two things at once turns a correction into an assessment of the person.
- "FYI" attached to a correction reads like filing a complaint about someone.
- A question like "are you sure about that?" makes them do the embarrassing part themselves.
- A long account of how the error happened keeps the mistake on screen much longer than the fix does.
The corrections I have received without a wince were all short. Four or five words, the right figure, no lesson attached. I updated the thing and forgot about it, which is exactly what a correction should leave behind.
My own first draft of a correction usually runs thirty words longer than the version I send, because the extra words are me managing my own discomfort at doing it. Reading the draft as the person receiving it strips most of them out. When I want that done at the moment of sending rather than five minutes later, I take the Direct rewrite in Unvent and the padding goes with it.
Give them a road back
Add the reason their version was reasonable, when a real one exists. It costs you one clause and it takes the ranking out of the exchange.
"The renewal moved to the 12th when we resent the contract" carries the same fact as "that date is wrong" and leaves the other person standing. They were not careless. They were reading an older copy, which is a thing careful people do.
Do not manufacture a reason when there is none. Invented generosity is easy to spot and it reads as pity, which is worse than being told plainly that you had the wrong number.
Leave a door open for being wrong yourself, because sometimes you are. One hedge, aimed at your own certainty, is earned: "unless there is a newer version I have not seen". That is different from hedging the fact, which just produces a message where nobody can tell what you are claiming.
The apology that makes it worse
Do not apologize for correcting something that needed correcting. A long apology turns a small fix into an event, and now the other person has to stop and comfort you.
"So sorry, I might be completely wrong here, feel free to ignore me, but I think maybe the figure is different?" The reader now has two jobs. Work out the right figure, and reassure the anxious person who brought it up.
Politeness in a correction is mostly brevity and timing. Say it early and say it once. Do not circle back later in the thread to check that things are fine between you. That check-in is the message that actually makes it awkward.
Take the correction in one line
Take it in one line and carry on. The fastest recovery from a public mistake is agreement without a speech.
"Good catch, fixed" closes the loop. A paragraph explaining how you came to believe the wrong thing keeps your mistake in view for another six replies, in a thread where everybody had already moved to the next topic.
Some corrections arrive with a sting attached, and you get to choose which part you answer. Answer the fact. Ignore the flag. Nothing defuses a status move faster than someone taking the information and carrying on, and the people watching will notice you did it even if the sender never does.
If what you are fixing is a judgment rather than a fact, this is the wrong shape entirely and you want the way disagreement works in writing instead. Facts have a right answer. Calls do not, and pretending otherwise is its own kind of rude.
What a corrected room sounds like
Teams that correct everything in public go quiet, and the quiet gets mistaken for higher standards.
Once a few people have been tidied up in front of an audience, everybody quietly recalibrates, and the number you were only mostly sure about stops getting posted, and the half-formed idea stays in your drafts, and the question you would have asked out loud never gets asked anywhere, and none of it registers as a loss because the channel looks tidier than it used to. What you get is a room where every statement is defensible and almost nothing useful is said first.
So count them for a week. Every correction you sent, and separately, the ones that changed a decision. Do not do what I did, which was start the count, reach an uncomfortable ratio by Wednesday, and quietly stop counting.
Fix the fact, not the person
Unvent rewrites what you are typing, right where you are typing it, in the tone you choose. The correction that leaves your hands is the short, plain one you meant to write, instead of the padded version your nerves produced.
Add Unvent to Chrome