← All articles
StrategyAugust 9, 20264 min read

When a post goes out wrong

The mistake is rarely the damaging part. The half-hour of silence, the quiet delete and the defensive reply usually are.

Sooner or later something goes out that should not have: the wrong file, a name spelled wrong, a joke that lands badly, a scheduled post that arrives on a day when it reads terribly.

Decide which kind it is, first

  • Cosmetic — a typo, a wrong date in the caption. Edit it. Nothing else is required.
  • Factual — the information is wrong and people have acted on it. Correct it visibly, not quietly.
  • Harmful — it hurt someone, or it went out at a moment that made it cruel. Take it down and say something.

Most incidents are the first kind and get treated as the third, which is its own kind of mess.

Deleting is not a fix by itself

A deletion with no explanation reads as hiding, and screenshots exist. If something is worth removing, it is worth one sentence saying it was removed and why.

“We got this wrong, here is the correct version” closes the subject. Silence keeps it open, and so does an explanation longer than the mistake.

Timing beats wording

A plain response in twenty minutes does more than a perfect one the next morning. Most of the damage in these situations accumulates while nobody is saying anything.

Afterwards, fix the process

Almost every one of these traces back to something structural: no second pair of eyes, media attached at the last minute, a queue nobody looked at before a difficult week. An approval step, or simply reading the week’s queue on Monday, prevents more than resolve does.

One case worth planning for in advance: something happens in the world and your scheduled posts are suddenly wrong in tone. Knowing how to pause the whole queue, before you need to, is worth the five minutes of finding out where that button is.

Stop watching the clock. Start drifting.

Get started free

Keep reading