Announcement fatigue: why nobody reads your announcements

The complaint "we send announcements but nobody reads them" is usually a design problem, not a reading-habit problem. Employee attention is a limited budget, and most companies spend it without noticing.

How fatigue builds up

Three mechanisms work together.

Volume. Someone receiving five announcements a day does not read all of them; they start choosing which to read. They choose by headline and skip most.

Irrelevance. After three announcements in a row that do not concern them, the chance of opening the fourth drops sharply — even when the fourth is relevant.

Channel sprawl. When the same information sits in email, a messaging app and the intranet in different forms, employees cannot tell which is current and learn to trust none of them.

Targeting is the strongest tool

The most effective fix is not sending fewer announcements but sending them to the right people. Every employee seeing only the fifteen of a hundred announcements that concern them beats everyone seeing all hundred.

For that, audience definitions have to be real: location, department, role, working pattern. Once those breakdowns exist, "all employees" becomes the exception.

A practical rule: if you cannot answer "why does this concern group X?" before sending, remove group X from the list.

Separate notifications from announcements

Not every announcement needs a notification. Making that distinction clear resolves most of the fatigue.

A notification is for the time-critical: a system outage, an emergency, a last-day reminder. Everything else sits in the feed and gets read when the employee has a moment.

Leaving notification preferences to the user also works — but only preferences that genuinely work should be offered. A setting that changes nothing when switched off erodes trust.

Take a channel inventory

Most companies have never counted their communication channels. When they do, the count is usually eight to ten: email, intranet, messaging groups, noticeboards, screens, manager meetings, newsletter, mobile push.

Assigning each channel a single job and writing it down ends the overlap. A clear rule such as "process changes are announced only on the intranet, never in messaging groups" lets everyone know where to look.

WhatsApp groups deserve special attention: fast, but not searchable, not archived, and risky for data protection because they contain personal numbers. Moving critical information there means corporate memory scattered across phones.

Archive and freshness

The invisible source of information overload is old content. If a three-year-old procedure is still published, it can outrank the current one in search and an employee acts on wrong information.

The only fix is giving every piece of content an owner and a review date. Content past its date is flagged to its owner; content with no owner should already be archived. We covered this loop in intranet governance and content ownership.

Measure and intervene

The best indicator of announcement fatigue is the trend in read rate over time. If read rate is falling while content quality is constant, the problem is volume.

The second indicator is the notification opt-out rate. If it is rising, most of the notifications sent are unnecessary for the recipient.

Fewer, better

What has to be done is simple but takes discipline: fewer announcements, better targeted, written shorter.

Three good announcements a week do more than twelve mediocre ones. For the publishing workflow see managing company announcements.

Why search matters

One antidote to announcement fatigue is letting information be pulled instead of pushed. If employees can find what they need when they need it, not everything has to be sent to them.

That depends directly on search quality. An employee who cannot find what they searched for does not search next time; they ask someone or give up. Both are invisible costs.

For search to work, content must be titled, tagged and current. Semantic search makes it easier to find the same question asked in different words — when an employee types "leave", the system should find the "annual paid leave procedure".

Leave room for personal preference

Not everyone has the same appetite for information. Some employees want to see everything; some only what is mandatory.

Leaving room for personal preference in the home page layout — which section is pinned, which is hidden — manages that difference. The other half of the rule is that critical content cannot be hidden: personalisation is not the right to miss mandatory information.

A better measure: actions per week

Rather than capping the number of announcements, capping the number of actions asked of employees is a more useful rule. Three announcements to read are not tiring; three forms to fill in are.

Setting a weekly action budget — at most one mandatory action per person — queues requests and forces prioritisation. Once the rule is in place, it quickly becomes visible how many actions were never really necessary.

Clean-up is not a one-off

Information overload accumulates; cleaned once and left alone, it returns within six months. A content review twice a year regularly weeds out ownerless and expired content and keeps search results clean.