Too many notifications when everyone is on every project

If your small team gets too many notifications, follow the work you own, use @-mentions for direct asks and put routine updates into one daily summary. Keep blockers, client messages and work due today on the instant-alert list.

Start with a one-week tally of what arrives and what people act on, then agree the policy in a 15-minute conversation. Changing settings together gives everyone the same expectations about which messages need an answer.

Contents

• Why does a small team get so many notifications?
• How do you know alerts are being ignored?
• How do you measure the noise in one week?
• Which notifications should you switch off first?
• What should still interrupt people?
• Too many Slack notifications: what to change?
• How do you agree a notification policy in 15 minutes?
• Questions about team notifications

Why does a small team get so many notifications?

In many project tools, joining a project also subscribes you to its updates. Someone who needs access can end up following 40 tasks without choosing to. A team of six may add everyone to every project so anyone can help, then send each person updates they do not need.

The numbers grow faster than the team does. Take a sample team of six people running eight client projects, all six on every project. If the whole team creates, moves or comments on 30 tasks in a day, and each of those events notifies the other five members, that is 150 notifications a day across the team, or 25 each. Very few of them are about anything the reader has to do.

Add a seventh person and every event now reaches six people instead of five. Add a chat channel that mirrors the project tool, and each of those 25 arrives twice. Add email copies and it is three times. One tool sends the update to the inbox, another to the phone, a third to the desktop, and the person who gets all three has learned within a fortnight to clear badges without reading them.

The same pattern shows up in reviews of very different tools. A gallery director whose marketing agency brought their small arts team into Asana wrote that, because the team was tiny and everyone was on everything, the notifications were too much no matter how they set them. A software company's chief executive reviewing Basecamp complained that admins could no longer set notification preferences for participants, so each person had to change them project by project. Neither is really about the tool. Both describe a team where nobody decided who should hear what.

How do you know alerts are being ignored?

Alerts are being ignored when people miss direct questions, leave badges unread or follow up on every task comment in chat. Look for these patterns across the team:

• Badges nobody clears: the red counter sits at 60 or 200, and people treat it as wallpaper.
• Everything muted: someone switched off all email from the project tool months ago and now hears about work only in meetings.
• "Did you see my comment?": the person who needed an answer follows up in chat, which adds another notification to the pile.
• Missed asks: a real question to one person was buried between ten status changes, so it waited two days.
• Work moves back to chat: people stop commenting in the project tool because "nobody reads it there", which is how teams drift back to Slack.

When people need a second message to prompt a reply, sending more alerts adds to the problem. Reduce routine updates so direct asks are easier to find.

How do you measure the noise in one week?

Ask everyone to keep a tally for five working days: how many notifications arrived, from where, and how many they actually acted on. Acted on means they replied, changed something or did a task because of it. Reading and dismissing does not count.

Keep it rough. A note on paper or a line per day in a shared document is enough. The point is not precision, it is giving the team a number to look at instead of a feeling. A sample tally for one person on the team of six above might look like this:

These are sample figures, not measured data. Here, 43 of 376 notifications prompted an action, and 19 of those 43 came from direct messages and mentions. Use your team's tally to find which sources people act on.

Also record duplicate alerts and important messages that arrived late or were missed. Remove the duplicates first and keep the missed messages in mind when choosing instant alerts.

Which notifications should you switch off first?

Switch off updates about work you do not own, and duplicates of anything you already get somewhere else. Use these three rules to decide who needs each update:

1. Follow what you own. You hear about tasks assigned to you, tasks you created and tasks you choose to follow. Being a member of a project is not a reason to hear about every task in it. Many tools let you leave a task's followers or switch off project-wide updates while keeping your own.
2. Mention when you need someone. If a comment needs a specific person to act, it names them with an @-mention. A comment with no mention is information, and information can wait. Pair this with the first rule so questions go directly to the person who needs to answer.
3. Put the rest in one daily summary. Status changes, new tasks and comments on other people's work go into a digest that arrives once a day, at a time the team agrees. Anyone who wants to know what moved reads one message instead of fifty.

Then remove the duplicates. Pick one place for each kind of message: the project tool for work, chat for conversation, email for clients and anything outside the team. If chat already mirrors every task update into a channel, choose which copy to keep and switch off the duplicate alerts.

What should still interrupt people?

Keep instant alerts for anything that stops work or has a clock on it today. That is a short list, and it should stay short, because each extra item makes the others easier to ignore.

• Blockers: someone cannot continue until you answer or finish something.
• Client messages: a reply from a client, or a question that a client is waiting on.
• Due today: your own work that is due today or already late, once, not every hour.
• Direct asks: anything with your name on it, whether it is an assignment or a mention.

Everything else can be read in a batch. A useful test for any notification type is to ask what would go wrong if the person read it four hours later. If the honest answer is "nothing", it belongs in the daily summary. If it is "a client waits" or "a colleague sits idle", it stays instant.

It also helps to agree what counts as urgent in practice. One team might decide that a blocker gets a mention in the task plus a short chat message. Another might decide that chat is for urgent things only. The detail matters less than everyone using the same signal, so that a ping means the same thing whoever sends it. People who need longer stretches of quiet can add an off-grid status on top, once the noise is down to the things that matter.

Too many Slack notifications: what to change?

Set Slack to notify you about mentions and direct messages only, then make exceptions for the one or two channels where you want every message. Slack's own notification preferences offer exactly that choice: "Everything" or "Mentions and direct messages", with per-channel exceptions on top.

• Mentions and DMs as the default: under Preferences, then Notifications. Channels you only need to skim stop pinging you, and anything addressed to you still arrives.
• Mute and hide busy channels: from the notifications icon at the top of a channel. A muted channel still shows a badge when you are mentioned there, so muting a noisy project channel does not mean missing a question.
• A notification schedule: Slack pauses notifications outside the hours and days you set. Agreeing the same working hours across the team stops evening pings from feeling like requests.
• Keywords for the things you care about: a client name or a product name, so you hear about it in channels you only skim.

The bigger win is usually upstream. If a project tool posts every task change into a Slack channel, that channel is a second copy of the project's notifications. Either keep the channel for conversation and switch the mirror off, or keep the mirror and stop the project tool's own alerts. One copy of each update is enough. It is the same reasoning behind keeping one source of truth for tasks: when the same update lives in two places, people stop trusting either.

Each extra app brings its own stream. Small companies run about 152 SaaS apps on average, according to the tool sprawl figures, and most of them can notify someone. A notification policy that covers the project tool and chat takes care of most of the noise a small team actually feels.

How do you agree a notification policy in 15 minutes?

Bring the week's tallies to a short meeting, agree the three rules and the short list of instant alerts, then change the settings together before anyone leaves. Make the changes during the meeting so the policy is in place when everyone returns to work.

1. Minutes 1 to 5, look at the numbers. Each person reads out what arrived, what they acted on, and one message they missed or saw late. Use the gap to identify alerts to remove.
2. Minutes 5 to 10, agree the rules. Follow what you own, mention when you need someone, one daily summary for the rest. Agree what counts as urgent and where urgent things go.
3. Minutes 10 to 15, change the settings. Everyone opens their project tool and chat preferences and makes the changes there and then. Someone writes the policy down in one short note the team can find.

Who decides matters in a small team. If the owner or lead never changes their own settings, everyone else will assume the old rules still apply to them. It also helps if an admin can set sensible defaults for new people, so the next person who joins does not start with everything switched on.

In Breeze, each person can turn off email notifications per project under "Emails from" in their profile's notification settings and choose an hourly or daily recap instead. An admin can set the same preferences for a teammate. Notifications for subscribed tasks keep arriving. This setting controls email; it is not a per-project in-app mute.

Look at the tallies again a month later. If the useful line has stayed the same and the large lines have shrunk, the policy is working. If someone missed something important, adjust the instant list rather than switching everything back on.

What is the one change to make this week?

Start by removing duplicate alerts. Then use the week's tally to decide which updates belong in a daily summary and which still need an instant alert. Keep the policy short enough for a new teammate to follow.

Questions about team notifications

Why do I get notified about every task in a project?

Many project tools treat a project member as someone who wants to hear about everything in that project. In a small team where everyone is on every project, that means every comment and status change reaches everyone. Follow only the tasks you own and switch off project-wide updates to stop it.

Should a team turn off all notifications?

No. Turning everything off hides the few messages that matter, such as blockers, client replies and direct questions. Keep those instant, put status changes and other people's updates into one daily summary, and remove duplicates that arrive in more than one place.

How do you reduce Slack notifications without missing things?

Set Slack to notify you about mentions and direct messages only, mute busy channels, and add keywords for the topics you care about. A muted channel still shows a badge when someone mentions you, so a direct question still reaches you.

Written by Lucas

Lucas writes content at Breeze and specializes in project management, team collaboration, and practical workflow advice. He helps small teams and growing businesses plan projects, track progress, and keep work organized by sharing clear, actionable guides.