Your team is losing hours every day to how they communicate
- Michael Amenta
- Nov 11, 2025
- 3 min read
There's a quiet drain to reputation in your everyday habits. To reclaim your team's time, you must address norms.
What would it do to your reputation if you could cut one habit that's been proven to increase your colleague's stress levels?
Defaulting to synchronous tools, like Slack, Teams, and their equivalents, for collaboration — or for communication that doesn't require an immediate response — has the effect of breaking your colleagues' flow states for over 20 minutes.
These tools have permeated because they optimize for the sender: the person who wants your attention gets it instantly. And since it's senders who drive adoption of communication tools, Slack and Teams keep growing.
Slack's casual nature also removes the friction that once protected recipients. Writing an email, scheduling a meeting, or picking up the phone each required the sender to ask themselves: does this actually need to be said, and how should I say it? Slack removes that pause entirely.
The result is a norm most teams never consciously chose: that any colleague is reachable, in real time, for any reason, at almost any hour. Availability became the default, and the cost of that availability to the recipient was never part of the conversation.
It's true that Slack's channel feature can enable genuine asynchronous conversation, but channels aren't the problem. The problem is the cultural expectation of an instant response. No amount of async-friendly features changes what most people experience when that notification arrives.
Choosing the right tool
We've forgotten that communication tools are just that. And while a hammer is great for driving a nail, it's not very good at cutting things into pieces. The mistake isn't using Slack; it's using the wrong tool for the job.
The matrix below maps communication tool choice against two variables: how objectively urgent the request is on the x-axis, and how complex it is for the recipient in the y-axis. Most workplace communication falls somewhere in this grid and choosing the wrong quadrant is where the cost accumulates.
Two situations override the matrix. When a topic involves genuine emotional tension, written communication will make it worse. Sincerity is nearly impossible to convey in text, so ambiguity often fills the gap. Instead, get on the phone or meet in person. And when a topic is genuinely complex, add a shared document that gives the recipient time and context to form a real response, then use planned time together to discuss it.
Unplanned and uncontextualized meetings are the most expensive communication choice a colleague can make. They create two interruptions: the invite itself, which adds cognitive load for the recipient ("what is this meeting? should I attend?"), and then the meeting, which consumes time that reading a well-written document never would. A meeting without a prior agenda and supporting context is a cost multiplier. It transfers the preparation burden from the sender to every person in the room.
What leaders can do
The core problem is inefficiency imposed on the recipient and, since recipients don't drive tool adoption, no product will solve this for you. The culture has to be set deliberately.
Start with notifications. Encourage your team to turn off all banners, sounds, and indicators from messaging tools by default, and establish a cultural norm of 24-hour response times for non-urgent communication. Reserve high-priority messages with @tags for genuine emergencies.
Protect focus time structurally. Several hours of daily focus blocks, free from both Slack and email, reduce the impulse to send unnecessary messages as much as they protect the recipient.
Enforce standards. Require agendas and supporting documentation for every meeting, and circulate summaries afterward. When a colleague sends a Slack message that isn't urgent, ask them to resend it as an email. That single habit, modeled consistently, does more to reshape communication culture than any policy document.
The teams that get this right don't have better tools. They have a leader who decided the defaults weren't good enough.