A customer-facing announcement is written to persuade. An internal one is written to inform people who already work there and who will act on what it says. That difference changes the structure. A sale announcement can open with a headline and a feeling. A policy change cannot: it needs to say what is changing, why, and exactly when it takes effect, or people will get it wrong.
Lead with what people need to do
If a policy or process is changing, the effective date is not a detail to mention somewhere in paragraph three. It belongs near the top. Someone reading quickly between meetings should be able to tell, from the first few lines, whether this affects them today or next month. The same goes for anything people are expected to do differently: say it plainly, rather than trusting the reader to infer it from context.
Say what does not change
Organisational announcements cause more anxiety from what they leave out than from what they actually say. If a team is merging, being renamed, or gaining a new reporting line, people quietly worry about their own role, their manager, and their day-to-day work. Stating clearly what stays the same is not filler. It is often the single most reassuring sentence in the whole announcement, and skipping it is what sends people straight to their manager or a colleague to ask “wait, does this mean…”.
Corporate buzzwords cost you trust here more than anywhere else
Customers might skim past a bit of marketing gloss. Colleagues read dozens of internal announcements a year and can spot filler instantly. Phrases like “we are so excited to announce” or a paragraph of throat-clearing before the actual news read as a sign that there is nothing much to say, or worse, that something is being softened. Say the thing. If it is good news, plain language lands better than forced enthusiasm. If it is a hard change, plain language is simply more respectful of people’s time.
A placeholder beats a guess
It is tempting to smooth over a missing detail, an effective date you have not confirmed yet, an exact policy line you are not sure of, by writing something plausible. Do not. An internal announcement with a wrong detail in it causes real confusion: people will act on it, quote it back to you, and plan around it. If a detail is not settled, leave an obvious placeholder like [insert effective date] so whoever finalises it knows exactly what still needs filling in.
Match the length to the news
Not every update needs three paragraphs. If the actual news is two sentences, write two sentences. Padding a short, simple update to make it look more considered has the opposite effect: it buries the point and signals that nobody trusted the news to stand on its own.
Example
Common mistakes
- Burying the effective date in the middle of a paragraph instead of stating it upfront.
- Corporate buzzwords and hollow enthusiasm that make people skim past the actual news.
- No clarity on what stays the same, leaving people to assume the worst.
- Padding a two-line update into three paragraphs to make it look more thorough.