Notification fatigue: sending the right alert to the right person

What is notification fatigue and how do you prevent it? Staged reminders, the right channel and role-based dashboards keep critical alerts from getting lost.

FUFerhat UğurluYazSis TeamPublished: November 23, 20265 min read

How many of the notifications on your phone did you dismiss this week without reading? It is no different with business software: if most of the alerts that arrive during the day are irrelevant, you dismiss the relevant one with the same reflex. Notification fatigue is when a person, faced with a large number of mostly irrelevant alerts, stops reacting to alerts. The result is that a critical date passes without anyone noticing.

The solution is not sending fewer notifications but sending more accurate ones: to the right person, at the right time, with the right weight. In this article we explain five rules for this, using the Reminder and Dashboard modules of YazSis KurumsalPortal.

Three symptoms of notification fatigue

  • The “mark all as read” habit: The notification list is opened but not looked through item by item; this is a sign that the list has lost trust.
  • A missed critical date: The expiry of a permit, an inspection or a contract goes by with the excuse “the notification came, but I didn’t pay attention.”
  • A pile of filters and rules: Employees throw work e-mails into a separate folder and never open it.

The common root of these symptoms is the unclear question of whom the alert belongs to and how important it is. The system has “given the information,” but nobody has done their part. And the problem is invisible: nobody complains, because everyone shares the same noise.

Five rules for the right alert

  1. Give every alert an owner. Nobody takes on an alert sent “to everyone.” The alert should go to the person or team who will do the work; an alert with no clear owner quietly goes stale, like a task with no owner.
  2. Think in stages, not one-off. A single alert arriving close to the final day is often too late. A staged advance warning that arrives 30, 7 and 1 days before the critical date invites planning at the first, action at the second and a final check at the last.
  3. Choose the channel by urgency. Sending everyday news and the final warning through the same channel in the same tone devalues both. A portal notification, an e-mail and an SMS carry different weight; which is used for what should be a conscious decision.
  4. Record what is completed. If completion is recorded when the check is done, the question “was it done?” is not asked and the history of the work is kept. For periodic checks, this history also becomes a reliable starting point for the next period.
  5. Simplify the screen by role. Showing everyone the same dashboard is another form of notifying everyone about everything. When a person sees only what concerns their own work, they trust what they see.

Example: permit, inspection and maintenance dates

Picture someone responsible for administrative affairs: vehicle inspections, work equipment checks, permits, contract renewals and periodic maintenance. If these dates sit in a spreadsheet or in one person’s calendar, the tracking is lost when that person goes on leave or leaves the company. And when the date is noticed only after it has passed, you often have to rush to renew, or even stop the work.

In the Reminder Module, inspection, permit, contract, maintenance and periodic check dates are gathered in a single list. When a record is created, the date is set and a repeat rule is chosen; warnings are given 30, 7 and 1 days before the date by portal notification, e-mail and SMS. Administrative affairs, HR, quality and maintenance teams work from the same records. When a check is done, completion is recorded and the history of each check is kept.

If everything is urgent, nothing is urgent.

Who needs to know what?

A practical way to simplify notifications is to ask, for each role, “what must I know?” A sample distribution might look like this:

  • Employee: Their own pending work and the tasks assigned to them. Nothing that concerns someone else’s process.
  • Unit manager: Their team’s requests awaiting approval and deviations in their unit’s indicators.
  • Senior management: Only the indicators that require a decision and critical deviations; not the day-to-day operation.
  • Administrative affairs, HR, quality and maintenance teams: Critical dates that are approaching and periodic checks.

What should the dashboard show?

The Dashboard Management module shows each user, on a single screen, the KPIs defined for their role, pending and upcoming work, notifications and process shortcuts. Senior management, unit managers and employees do not see the same dashboard but the data that belongs to their own role. That way a manager looks only at the deviations that concern them and, on seeing one, moves to the relevant process and turns the decision into action.

Which indicators go on the dashboard is decided when roles and KPIs are defined. This decision is one of the most effective ways to reduce notification noise: data that does not make it onto the dashboard disturbs nobody. Choosing a small number of indicators at the start and adding more as they are used is healthier than putting everything in from the beginning. If you want to turn the dashboard into a daily decision tool rather than a data dump, every indicator should have an owner and a purpose.

To track critical dates, take a look at the Reminder Module, and for role-based dashboards, the Dashboard Management page.

Frequently asked questions

What is notification fatigue?

It is when a person, faced with a large number of mostly irrelevant alerts, stops reacting to alerts. It also causes critical alerts to get lost in the noise.

When are alerts sent for critical dates?

The Reminder Module of KurumsalPortal sends a staged advance warning 30, 7 and 1 days before the critical date. Alerts can be delivered as portal notifications, e-mail and SMS.

Is a separate account needed for sending e-mail and SMS?

E-mail is sent through the organization’s own SMTP account, and SMS through the organization’s own NetGSM account.

Does every manager see the same dashboard?

No. The dashboards in the Dashboard Management module are role-based; each user sees the KPIs and work defined for their own role and can access only the data they are authorized for.

FU
Ferhat Uğurlu · YazSis Team

Builds enterprise software, AI and digital transformation products together with the YazSis team.