How to address a rumor head-on in writing

Name the rumor in plain words, say what is true, and say what you cannot answer yet. Silence is not neutral ground while a rumor is circulating; it is the most generous evidence the rumor has.

The instinct to say nothing is understandable. Addressing it feels like dignifying it, and there is a real fear of putting the idea into the heads of people who had not heard it.

That fear is usually already out of date. By the time a rumor reaches you, it has been through several people, and the ones who have not heard it will hear it this week from somebody less careful than you.

Say the rumor out loud, in its own words

Quote the thing people are actually saying, using the phrasing they are using, rather than a sanitized version of it.

"Some of you have heard that the Berlin office is closing." That is a sentence people recognize. It tells them they were not imagining the tension, and it tells them you are not going to make them ask.

The alternative is what most organizations produce, which is a message about "recent speculation regarding our operational footprint". Everyone can tell what it means. What it signals is that the writer would rather not say the word, and if you will not say the word, why would anyone believe the rest of the paragraph?

There is a real cost to naming it, and it is worth paying. A rumor that has been said out loud can be answered. A rumor that is only gestured at cannot.

Answer in three states, and use all three

Sort every part of the rumor into what is true, what is false, and what you cannot say yet.

Most rumor messages use only two of those, and the missing one is almost always the third. Writers reach for a general reassurance instead, because "I cannot tell you that yet" feels like an admission of failure. It is the most credible sentence in the message. Somebody who says "no decision has been made about the Berlin office and I will tell you the day one is" has said something checkable, and everyone can watch whether they keep it.

The hard version of this is a rumor that happens to be true. The pressure then is toward a denial that is technically defensible: nothing is signed, no announcement has been prepared, no decision has been finalized. Each of those is a sentence people will replay in a month, and they will not be grading you on technical accuracy when they do. Somebody who feels tricked by a true statement treats your next true statement as a trick.

So when there is something you cannot discuss, say that there is something you cannot discuss. It costs a week of discomfort and it buys the ability to be believed later, which is the only asset in this whole situation.

The useful version is short

The useful version is short and does a small number of things.

• Name the rumor in the words people are using.
• Say what is definitely true.
• Say what is definitely not true.
• Say what is undecided, and when you will know.
• Say where to ask follow-up questions.

The fourth item carries the most weight and is the one to be most careful with. If you name a date, you have to come back on that date, even if the answer then is still "no news". Especially if it is still no news, in fact, because that is the moment people find out whether your commitments survive being inconvenient.

Say it in the same room where it is spreading

Answer in the channel the rumor is living in, not one level up in a formal announcement.

A rumor moving through direct messages and hallway conversations is not reached by a company-wide email in a house voice. That email gets read as public relations, and the private conversation carries on underneath it, now with a new topic: what the email did not say.

So post in the team channel. Say it in the standup. Use your own writing voice, the one people recognize from your ordinary messages, because a sudden shift into formal register is itself a signal that something is wrong.

Deal with it early too. The window in which a correction still lands is short, and after a few days people have started making decisions on the rumor rather than on anything you said.

The version of this I run into on Unvent is smaller and the same shape: somebody asks in public whether the extension does something it does not do, and the temptation is to answer generally and move on. The general answer never ends it. The sentence that ends it is the one that repeats their words back and says no to exactly the thing they asked about.

Ask directly, and ask in private

If a rumor has reached you and you are not the person who can answer it, ask directly and in private.

Go to the person who would know, name what you heard, and say what you want. "I have heard from a couple of people that the team is being split. I would rather hear it from you than keep hearing it sideways." That message is not aggressive and it is very hard to deflect.

Do not ask in public unless the rumor is already public. A pointed question in a group channel forces an answer before the person has one, and what you will get is the defensive version.

And resist passing it on with a disclaimer. "I do not know if this is true, but" is how most rumors travel, and the disclaimer does nothing except let the person repeating it feel careful.

The thing worth noticing about all of this is that the correction is never the expensive part. Naming the rumor takes one sentence, and the reason people avoid writing that sentence is not that it is hard to compose. It is that saying the word out loud makes the situation real for the writer too, which is a private cost that gets paid publicly, by everyone else, in the form of silence.