Most companies have a spam problem they never talk about, because the spam is coming from inside the building. Not junk mail. Not phishing. Just the ordinary internal traffic a business generates about itself: the copied replies, the courtesy notifications, the alerts from six systems that all decided your team needed to know something at 4:47 in the afternoon.
Nobody set out to build this. It accumulated. Somebody turned on a notification years ago and never turned it off. Somebody started copying a manager on everything after a bad meeting, and it became habit. A new tool arrived with every alert enabled, and nobody had time to go through the list. Now it is just how the place sounds. Here is why that is worth fixing, and how to do it without a committee.
Where the Noise Actually Comes From
Internal noise has four sources, and knowing which one you are dealing with tells you how to fix it.
- Notification settings nobody ever tuned. Every collaboration tool ships loud, because a vendor would rather over notify than have you miss something. Defaults are a marketing decision, not a recommendation.
- Reply-all culture. One message goes to fourteen people. Four of them reply to all. Now there are five messages in fourteen inboxes, and the useful content is one sentence in the third one. Microsoft’s Work Trend Index special report, published in 2025 from aggregated Microsoft 365 usage signals, found that emails sent to twenty or more recipients rose seven percent year over year while one-on-one email threads declined five percent.
- Copying people as self protection. This is the honest one. People copy a manager because they want a record that they told somebody. Not laziness. Defensiveness, and a symptom of a trust problem rather than an email problem.
- Tools that alert on everything. Monitoring systems, ticketing platforms, backup software, and security tools all want to tell you things. When a system sends fifty routine notices a week, nobody reads the fifty first, which happens to be the one that matters.
The Cost Is Attention, Not Minutes
People justify this work with time math. Twelve seconds per message, times four hundred messages, times fifty employees. That math is not wrong, but it undersells the problem badly.
The real cost is that careful work cannot be interrupted for free. Reading a notification takes three seconds. Getting back to where you were takes far longer, and if you were holding several things in your head, you may not get all of them back. Deleting a message is cheap. Rebuilding concentration is not.
That same 2025 Microsoft Work Trend Index special report puts numbers to the scale. It found that the most heavily interrupted portion of workers face a meeting, email, or chat interruption roughly every two minutes during core work hours, adding up to around 275 interruptions a day. It also reported that the average worker receives 117 emails daily, most of them skimmed in under sixty seconds, and 153 Teams messages per weekday.
Skimmed in under sixty seconds is the phrase to sit with. That is not reading, it is triage. A workforce permanently in triage mode learns to click through things without examining them, which is a security problem as much as a productivity one. We have written before about why phishing keeps getting through, and this is part of the answer. You cannot train people to scrutinize email while also sending them hundreds of messages a day that do not deserve scrutiny.
Start With a One Week Audit
Do not start with a policy. Start with evidence, because the sources of noise are almost never the ones people guess.
- Pick three or four people across different roles. Someone in the field, someone in the office, someone who manages people. Their inboxes look nothing alike, which is the point.
- Have them sort one week of incoming messages into three piles. Acted on it. Skimmed and deleted it. Never opened it. Do not ask for judgment about whether a message should exist. Just what happened to it.
- Count the senders in the second and third piles. A small number of systems and habits generate most of the volume, usually three or four sources, and one is almost always a tool nobody remembers configuring.
- Kill the top offenders first. Turn off the loudest automated sender entirely and see if anyone notices. Most of the time, nobody does. If someone does, you have learned something useful and you can turn it back on narrower.
This takes an afternoon and settles arguments that would otherwise take three meetings. It also gives you a before and after, which matters when someone claims nothing changed.
Agree on Who Gets Copied, and When
Norms beat rules here. A written policy about email etiquette gets ignored. A handful of agreements the team actually made together will mostly hold.
- The to line means action, the copy line means awareness. If you are copied, you are not expected to respond and nobody is waiting on you. Saying this out loud removes a surprising amount of low grade anxiety.
- Reply-all needs a reason. Not a rule against it. A reason. If your reply is useful to everyone on the list, use it. If it is “thanks,” it is not.
- Managers say plainly what they want to see. Most defensive copying happens because nobody ever told people the threshold. “Copy me on client commitments and anything that slipped, not on routine updates” ends the guessing.
- Decisions get a home that is not email. When the record of what was decided lives in a project tool or shared document, people stop copying each other to build a paper trail.
- Long threads become a call. Six replies deep on a decision means email has failed. Pick up the phone, then post the outcome once.
Turn Off Anything That Is Not a Person
This is the single highest leverage change, and it is close to free. The default should be that a notification interrupts you only when a human being is trying to reach you. Everything else can wait for you to go look at it.
Microsoft’s support documentation for Teams describes notification controls organized by category in the notifications and activity area of settings, covering chat, channel, meeting, and app notifications separately, plus a setting to mute everything except calls and meetings. Channels can be adjusted individually and apps toggled one by one. Google Workspace and most other platforms offer equivalent controls. The tools are there. Almost nobody opens them.
The rule we give clients: an automated system gets to interrupt someone only if a human is expected to act within the hour. A backup completed successfully is not that. A backup failed twice in a row is. Route the informational traffic somewhere people check on purpose, and reserve interruption for things that need interrupting.
The Bottom Line
None of this is a technology problem and none of it requires buying anything. Audit one week of traffic for a few people, turn off the loudest automated senders, agree on what the copy line means, and set notifications so only humans can interrupt. That is a day of work with a return you will feel within two weeks.
The part that decides whether it sticks is you. If the owner keeps copying eleven people on a scheduling question, or sends messages at ten at night, nothing else you announce will matter. Staff read behavior, not policy. Model the norm before you ask for it, and be visibly fine with not being copied on things. Reclaiming attention is the same argument we made about why saving time beats saving money, and it is one of the cheapest improvements available to a small business. If you want help sorting out which of your systems are generating the most noise, we do that for small and mid-sized businesses across Denton County. Contact us today
Sources:
Comments are closed