
THE MESSAGE THAT DOES NOT DIE



A director sent a two-paragraph email announcing a policy change. Clear. Direct. Unambiguous.
By Friday, three different teams had three different versions. Sales heard "more flexibility." Legal heard "more oversight." Product heard "nothing changes."
The director was furious. "I said exactly what I meant."
That was the problem. He said it once. A message that does not survive retelling is not a message. It is a hope.
Most communication advice asks: did they understand? Wrong question. The real test: what survives when you leave the room?
People will summarize. They will forget the caveats. And then they will be certain. Certainty is the danger. A confused person asks for clarification. A certain person acts.
Before you send anything important, ask: "If someone read this who does not like me, what would they say it says?"
Most distortion is not malice. It is inattention. The opponent test is a stress test. It reveals where your message is vulnerable. If an opponent can bend your words, so can someone who is tired, distracted, or in a hurry.
The director rewrote the email. He replaced "teams may adapt processes as needed" with "teams must follow the standard process unless Legal approves an exception." Then he added one sentence: "If you are unsure, default to strict."
The complaints did not stop immediately. One manager argued the new rule was too rigid. Another said it would slow them down. A third asked: "What if the exception process takes too long?" The director did not defend. He let the message stand.
Strict clarity has a cost. It removes room for judgment. That is the trade-off. Know it going in. The alternative is a message that bends until it breaks.
Within two weeks, the arguments stopped. Not because everyone agreed. Because the message was no longer the problem. The arguments moved to the exception process. That was a better problem to have.
Note on authority: This works if you have authority to set the rule. If not, keep the test. Skip the rewrite. The test works regardless of your role. The fix requires positional power.
Write the message that does not need you there. Then get out of the way.
