Protocol

Do not add an alert without an expected response

An alert with no expected action is usually just a new demand for attention.

About 1 min read

Before you use it

Use when
  • Someone proposes another warning, notification, banner or automated alert because a risk is important.

Keep this limit in mind

  • Some awareness alerts are justified even without immediate action, but they should be intentionally designed as awareness rather than pretending every notification is urgent.

An idea to explore.

Try this idea.

Inspect the example, try the idea in your situation, then check your next move.

Keep reading

Why it matters

Before adding the alert, define who receives it, what state it signals, what action or decision should follow, and when no action is appropriate. If nobody can act on the information, prefer a dashboard, log or periodic review instead of interrupting the user. Alerts should change attention because something now deserves action.

Steps

  1. For every interruptive alert, a receiver can explain the intended response without guessing.

An example

A quality bot should not ping the whole team for every low-confidence anomaly. A critical alert goes to the owner who can stop the release; low-priority anomalies can accumulate for review.

Check your result

For every interruptive alert, a receiver can explain the intended response without guessing.

Save and practise this idea

My learning

Read. Recall. Repeat.

Save this idea and return to it on any device.

Use email
Keep exploring

Connected ideas

You are readingDo not add an alert without an expected response

Evidence and sources
Supports

AHRQ PSNet describes alarm fatigue as slower or absent response when people are repeatedly exposed to alarms that are invalid or nonactionable.

The cited evidence is clinical; notification fatigue in software can share the attention mechanism without having the same risk magnitude.

Ten years later, alarm fatigue is still a safety concern · Summary

Supports

AHRQ's alarm-safety summaries emphasize reducing nonactionable alarms and improving the usefulness and prioritization of alerts rather than simply adding more alerts.

The correct alert threshold and modality depend on the task, consequence and user environment.

Ten years later, alarm fatigue is still a safety concern · Summary

All sources (1)
Edition and review

Version 0.1.0

No review details are supplied for this edition.

Read this idea as JSON · Release details