What is recognition fatigue?

The state in which recognition has become background noise: so frequent, generic or automated that people stop noticing it. A thank you that says nothing specific, repeated often enough, trains everyone to skip it.

What causes recognition fatigue?

Empty content, mostly. Automated messages, expiring allowances that get dumped, a habitual “great job team” at the end of every meeting. Volume on its own does not cause it; volume of messages that carry no information does.

How do you fix recognition fatigue?

Raise the standard rather than lowering the frequency. Remove the automated messages, drop the expiring allowances, and have a few visible people post recognition that names specific work. Attention returns when the messages start carrying something.

Recognition glossary

Recognition fatigue

Recognition fatigue is the point at which recognition has become so frequent, generic or ritualised that recipients and observers stop registering it, and each new acknowledgement carries no information and produces no response.

Recognition fatigue is usually diagnosed as too much recognition. It is nearly always too little content.

What is actually tired

The name suggests people have had too much recognition, and the remedy that follows is to do less of it. Both are wrong. Ask anyone in a fatigued program when they last received a specific, personal acknowledgement of something they did, and the answer is usually months ago. They are surrounded by recognition and starved of it at the same time.

What has worn out is attention. A channel full of messages that say nothing teaches its readers to skip the channel, and once they skip it, even a rare good message goes unread. The fatigue is with the format, and the format failed because the content emptied out.

How it sets in

Automation is the fastest route. A bot that congratulates every merge, every closed ticket or every birthday is generating recognition nobody gave, and readers work that out within a week.

Expiring allowances are the second. Points programs with a monthly budget that vanishes unused produce a spike of low-effort messages in the last days of each month. Recipients learn that a month-end thank you means somebody had points to burn.

Ritual is the slowest and the hardest to reverse. A manager’s “great job all” at the end of every meeting was sincere the first time. By the hundredth, it is a verbal full stop, and the team hears it as one. The same happens to a weekly shoutout round where each person is obliged to name someone whether or not anything happened.

The signs

Reactions fall off before messages do. A channel where posts used to get comments and now get a single emoji is on its way.

Messages shorten. When the median recognition is under ten words, a program is running on obligation.

The same names recur, in both directions. Reciprocal thanks between the same pairs every month is a sign that the recognition has become a social gesture rather than a report of something that happened.

And a real one gets lost. The clearest signal is when somebody posts a carefully written thank you and it disappears into the feed with the rest.

The fix

Do less of the empty kind and none less of the real kind. Switch off the bots. Remove or stop expiring the allowance. Drop the compulsory rounds. Then have a few visible people, ideally senior, post recognition that describes specific work, and keep doing it until the standard resets.

The tips for giving recognition on this site describe what the specific version looks like. Frequency can stay where it was, or rise: as the frequency page argues, weekly recognition that carries information does not wear out. Only the hollow kind does.

What it looks like

A kudos channel where every merged pull request gets an automated “nice work” and a clapping emoji. After two months nobody opens it, and a genuine thank you posted there goes unread.
A points program where the monthly allowance expires, so the last two days of each month are a flood of “thanks for everything!” messages sent to whoever comes to mind. Recipients have learned to ignore them.
A team lead who ends every standup with “great job all” for three years. The phrase has become a signal that the meeting is over.

Questions people ask

What is recognition fatigue?: The state in which recognition has become background noise: so frequent, generic or automated that people stop noticing it. A thank you that says nothing specific, repeated often enough, trains everyone to skip it.
What causes recognition fatigue?: Empty content, mostly. Automated messages, expiring allowances that get dumped, a habitual “great job team” at the end of every meeting. Volume on its own does not cause it; volume of messages that carry no information does.
How do you fix recognition fatigue?: Raise the standard rather than lowering the frequency. Remove the automated messages, drop the expiring allowances, and have a few visible people post recognition that names specific work. Attention returns when the messages start carrying something.