Most companies have too many places where announcements appear: email, team chat, the intranet start page, a notice board, a weekly newsletter. The same message is often posted in three of them, and the important one still gets missed. People respond by reading none of them closely.
The fix is not another tool. It is a short set of rules that everyone can remember.
Why announcements get lost
- Every message looks equally important. A new coffee machine and a change of payroll date arrive in the same way.
- Anyone can post anywhere. Channels fill up and nobody knows which one is official.
- Nothing expires. Last year's reminders sit next to this week's changes.
- The same news is repeated in several places, so people learn to wait for the "real" version.
Sort messages by type
Start with a short list of message types. Four or five are enough for most companies:
- Urgent: something that changes what people must do today, such as a system outage or a safety issue.
- Important change: a new policy, a changed process, a new tool. People need to read it this week.
- Team news: updates that concern one team or location only.
- General news: new colleagues, events, small improvements.
- Reference: information that stays valid, which belongs on a normal page and not in an announcement at all (see how to give intranet pages an owner and a review date).
One channel per type
Give each type exactly one home.
- Urgent goes to the channel people look at during the day, usually chat or SMS, and nowhere else at the same time.
- Important change goes to the intranet start page, with one short email or chat pointer to it.
- Team news stays in the team's own channel.
- General news goes into a single weekly digest.
The rule to repeat is simple: the message lives in one place, and other places only link to it. This also makes search better, because there is one version to find (see why intranet search is often broken).
Decide who may post
An open channel turns into noise. Write down who may post in each one.
- Urgent: a small named group, for example IT operations, HR and the management assistant.
- Important change: the owner of the process that changes, after a quick check by the intranet owner.
- Team news: the team lead or whoever they delegate.
- General news: anyone can suggest it, one editor publishes the digest.
The editor's job is also to say no, or to shorten, or to move a message to the right channel. Without that role the rules fade within a month.
Set how long it stays
Every announcement gets an end date when it is posted.
- Urgent: until the situation is resolved, then marked as closed.
- Important change: two to four weeks on the start page, then moved to the relevant page as reference.
- Team news and general news: one to two weeks.
When a message expires, check whether people still need the information. If they do, it should become a regular page with an owner, not an old announcement.
Write the message so it works alone
A good announcement can be understood without opening anything else. Put the point in the first sentence, say who is affected, say what they must do and by when, and add one link for details. Avoid long background and avoid sending the same text again with only the subject changed.
Keep urgent rare
If urgent messages come every week, people stop treating them as urgent. Agree on a few criteria, for example "stops work, risks safety or money, or needs action within a day", and let the editor check against them. If something is merely interesting, it is general news.
Check that it works
Once a quarter, pick two important announcements and ask a handful of colleagues whether they saw them and what they did. Ask where they would look for the latest company news. If the answers differ, you still have too many channels. If people do not open the intranet at all, look at why employees do not use the intranet, and make sure the start page reflects how they actually find things (see navigation by task, not by department).
Common mistakes
- Posting the same message in every channel "to be safe".
- No named editor, so rules are not enforced.
- Announcements without an end date.
- Using the urgent channel for general news.
- Putting lasting information into announcements instead of pages.
Summary
Good internal announcements need only a few rules: sort messages by type, give each type one channel, name who may post, and set an end date. Keep urgent messages rare, link instead of repeating, and test once a quarter whether the important ones were actually seen.
Sources
- Our related articles linked above.
- The approach described here is common practice in internal communication, used as a practical guide for small and mid-sized companies, not as a formal standard. No client results or market figures are claimed in this article.