How to Use Slack Notification Sounds to Improve Team Creativity in Remote Work
Focused work is fragile and notification sounds are where most of it goes. The fix is not fewer notifications, it is better-chosen ones. Six rules for picking sounds that cost you a second instead of a morning.
Short beats pretty
Keep every sound under about a second, ideally closer to half. A short sound is over before your attention has fully turned toward it, which is the difference between noticing something and stopping to listen. Long sounds also collide during busy stretches, and two overlapping alerts convey less than one.
One sound per decision, not per channel
You will reliably recognise four or five sounds. Assign them to the decisions you actually make: drop everything, look soon, look later, ignore. Channels change constantly; the decisions do not. This also means adding a channel rarely means adding a sound, which keeps the set from growing on its own.
Reserve the unpleasant one
Your top-tier alert should be a sound you would not want to hear at eleven at night. That is the point. If the urgent sound is nice, you will stop treating it as urgent within a month. Make it slightly sharp, slightly grating, and then protect it by making sure almost nothing qualifies.
Test at working volume, in your working room
Sounds that are obviously distinct in headphones at full volume turn into the same soft blur through laptop speakers in a room with a fan. Audition candidates in the setup you actually use, while typing, without looking at the screen. If you cannot name the sound that played, it is not doing its job. Do the same check again if you change desks or headphones, because the set that worked in one room often stops working in another.
Silence is a valid choice
Most notifications deserve no audio at all. Bot posts, green builds, announcement channels, digests. Assigning them a quiet sound feels like a compromise, but it is not; it is a small tax paid dozens of times a day for information you were going to read later anyway. Let the banner do the work. Silent rules are also the cheapest way to shrink an overgrown set, because you can mute a whole tier without deciding what it should sound like instead.
Retire sounds you have stopped hearing
Any alert you routinely dismiss without acting has expired. It is now background noise that still costs attention. Every quarter, look at what fired and cut anything that never changed what you did next. A sound set that only grows is one you will eventually mute entirely, and then you are back where you started.
Chirpy is a native macOS menu bar app for exactly this: rules on app, channel, person or keyword, priority ordering, volume per rule, 72+ built-in sounds and your own .mp3, .wav or .caf files. It reads notifications locally through the Accessibility API, so no Slack login is involved. See the setup guides if you want the short version of getting it running.