Why chat platforms are killing your business processes

It’s synonymous at any workplace. When you turn on your computer/laptop, amongst many other that will be opened up are also Slack, Teams, Discord or other chat platforms that your organisation have signed up to.

And that makes sense. Over the decades, it has become THE place to have those hallway chats, catching up with colleagues and project chats, albeit in an online environment.

Chat platforms and synchronous communications can have its benefits

Before looking at the problems with those chat platforms in terms of processes and productivity, let’s admit that there are definitely benefits to having synchronous communications.

I should caveat that this is all dependent on having a well-run and organised chatting platform with basic etiquettes and processes, with setups to your liking (like when to receive notifications, what integrations are used, using threads or not, etc.)

  • It creates a centralised synchronous communication: having team conversations, file sharing, and updates in one place can reduce reliance on scattered email threads. And nothing good comes out of a long email thread.
  • It helps with faster decision-making: real-time messaging and instant notifications allow teams to resolve questions and move projects forward without the delays of traditional email or the risk of missing an email because you have 1,032 unread messages (yes, people do that to their inbox!)
  • It organises workspaces instead of one messy thread: when organised well with clear structures, channels and threads keep conversations topic-specific. This ensures information stays structured, allowing relevant team members to follow along without the noise.
  • It creates seamless file sharing and collaboration: documents, images, and links can be shared directly within chats. This is on top of the ability to integrate with tools like Google Drive, Dropbox, or Office 365, which further enables easy sharing and collaboration.
  • It allows integration with business tools and creates workflows: these platforms can connect with a variety of apps like PM tools, CRM systems, and calendars, bringing workflows into a single hub so you don’t have to jump from one app to another.
  • It’s valuable for remote and hybrid workers: many argue that a chat platform is an essential part of distributed teams, as it helps keep everyone connected to ensure remote employees stay in the loop and feel like they’re part of the team.
  • It reduces the number and weight of meetings: we all want fewer meetings. So being able to ask quick questions and request updates via chat frees up time for focused work, reserving meetings for deeper discussions.

So how could chat possibly slow down processes and productivity?

Despite all the benefits that comes with it, it’s important to highlight the downsides, and they can be heavy:

  • It causes constant distractions and notifications: the constant stream of messages, pings, and updates can disrupt your attention, making it harder for employees to focus on deep, uninterrupted work.
  • It can create information overload: teams can easily become overwhelmed by too many channels, groups, and messages, making it difficult to find what’s important or stay caught up.
  • It causes blurred work-life boundaries: the expectation of being constantly available can lead to employees feeling pressured to respond outside of working hours, increasing the risk of burnout.
  • It can fragment communications due to use of multiple platforms and emails: due to lack of guidelines, important decisions or updates can get lost, leading to miscommunication or team members missing critical information.
  • It can create toxic availability and workplace tension: the expectation of being “always on” creates toxic availability, leading to tension between colleagues and between managers and direct reports. Employees can face criticisms if (God forbid!) they stepped away from the screen and were offline for a few minutes.
  • It can be unfair to non-standard workers: it’s unfair to those who work in different time zones or are part-time workers, which can create its own set of tensions and feelings of exclusion.
  • It’s hard to retrieve key information: it becomes much harder to retrieve important information when it gets pushed down and buried by newer messages in fast-moving threads.
  • It can be difficult to navigate across different channels: retrieving specific information is even harder when you’re bouncing from one channel to another, losing context in the process.
  • It creates ineffective AI tool output: since communication are scattered everywhere, you can’t easily find what you need in one central place when you are asking the AI to assist you with that process.

And leaving them too long without dealing with it can cause a form of operational debt, which can carry weight in your team.

What’s the alternative to using how you use chat platforms?

You can still use it, but with certain rules.

1. Use a project management tool as a single source of truth

I’m a huge advocate of, not only using a task/project management tool, but to focus your efforts on using only one project management tool to act as your trusted source of truth.

Once you have that in place…

2. Have all project-related discussions on those PM platform

Whether you use Notion (like me), Asana, Monday.com. etc., they will have some form of chat/comment functionality. They are not used enough in my opinion.

Rather than have sporadic conversations about a project, you can use that the chat functions to have any project specific discussions.

This also includes storing related documents, notes and meeting transcripts. They should all be there. But rather than sending an email or chat message about a message, have it all there so that it’s more transparent, easier to find and keeps everyone on the same page.

It will also create moments of asynchronous communications, which definitely has its place within any team.

3. Create an internal process on how to communicate

In one of my previous employed job, I’ve been on a receiving end of one colleague sending me a Teams chat about a document, then sent me an email that “I’ve sent you a message on Teams”, and then left a comment in a document to send another notification about the same project.

😐

Not only is it a waste of time and energy for everyone, but it’s a frustrating experience, especially for the person on the receiving end of those messages (me!)

As part of your business process optimisation, decide what goes where.

For instance, only use email for certain types of communications with 3rd party stakeholders like suppliers, service providers and during the hiring phases.

All project-related discussions should be done within the appropriate task card of the PM tool to keep contained, structured and easy to find.

4. Create a guideline on what’s obliged and not obliged

It’s one thing to know what goes where. But it’s another to understand the guidelines on what to do and not to do. They can small but very powerful.

For example, reaction-based communications can be used instead of writing a message which forces notifications. If you want to know how many people are attending a workshop, ask them to reply with an ‘hands up’ emoji instead of forcing unnecessary threaded messages and notifications.

Another important guideline is to explicitly outline what it means if you are online. There shouldn’t be a pressure of needing to appear ‘Online’ or ‘Available Online’ all the time. Set the standard by allowing people to step away from the screen to go to the toilet, get a drink, have lunch, get that delivery at the door.

5. Do not use email as the main communication

If it was up to me, I would get rid of the process of using an email in an organisation. Being caught in an email chat or trying to find a specific information is one of the biggest mental drain in any workforce. But I can appreciate it’s not always possible to completely remove it.

What is possible is to only use emails for formal discussions and scenarios. As mentioned earlier, it could be for dealing with suppliers and external stakeholders, hiring/firing employees, sending contracts, sending official messages to employees company-wide.

6. Use chat platforms for social or for quick requests

Have those fun conversations and banter like “I took my dog for a walk and it made muddy footprints in my new carpet” (with a photo attached of course).

Ask those quick questions like “who do I talk to create this creative asset”?

Share important update like “they have signed the contract!” to celebrate a new client.

Communicating with others doesn’t have to be work-only. Life would be too boring otherwise.

7. Enforce contextual threads as a hard rule

Most teams use threads sporadically. I suggest to make it mandatory (if the platform allows it).

Any reply to a specific point must happen in a thread. If someone posts a direct reply in the main channel, the norm should be to gently move it to a thread. This is to prevent a messy main channel page, one where it is hard to find the updates in amongst the noise.

Keep the main channel as a broadcast feed for high-level updates only, while deep dives remain contained. It makes searching for past decisions so much easier and faster.

8. Adopt writing-first decision making

Even though it can be quick, chat can equally be terrible for complex decisions because it encourages rapid-fire, low-thought replies like a thumbs-up emojis and “looks good”, which helps no-one because there’s no context.

If a decision is required, it requires a document. Before a decision is made in chat, the proposer must link to a short doc outlining the problem, options and recommendation. The chat is then used solely to discuss that document.

It forces clarity before discussion. It creates a permanent record of why a decision was made, not just that it was made.

At the same time, if it’s related to a project, make sure they are taken place in that PM tool.

9. Define response SLAs by channel type

As well for the wider communication channels available, having explicitly defined Service Level Agreements for each channel is helpful.

For example:

  • Urgent is for genuine emergencies only via phone or SMS.
  • Chat messages are within 4 hours during working hours, not for urgent decisions.
  • Email or PM comments are within 24 hours.
  • Async updates like Loom videos or docs are read within 48 hours.

The above are just ideas that you can use but I would suggest to find what works for you and your team.

That way, it removes the guilt of not replying instantly to a non-urgent message. It gives permission to batch responses, which is where deep work happens.

10. No-solution-in-chat protocol for complex issues

If a question is asked in chat and the answer is useful for more than one person, the responder must update the relevant SOP or PM task with the answer and link it back in the chat.

It turns every chat interaction into a potential knowledge base update rather than being lost six months later when the same question arises again and the knowledge is lost in the abyss.


Where do I stand on this?

I’m not suggesting we abandon chat platforms altogether. They’re useful tools, and in the wrong context, removing them would create more problems than it solves.

What I am suggesting is intentionality: why and how are you going to use it? In most jobs that I’ve been in, it was the case of opening up the app of company’s choice and just dive in. But I think that’s the wrong approach. Some people will have an idea on what is the general chat etiquette. But if even if everyone has that knowledge, there will be some forms of mismatch as they won’t all be the same.

Every time you open Slack, Teams or Discord, ask yourself: is this actually the right place for what I’m trying to do? If it’s a project decision, does it belong in the PM tool instead? If it’s urgent, would a video call be faster? If it’s information to reference later, can I put it somewhere searchable?

When I started applying these rules to my own work and to clients I support, the biggest shift was in the culture. People stopped feeling guilty about stepping away from their screens. Decisions became easier to trace. And that constant ping noise in the background got quieter.

We’ve all got habits that takes a while to get rid of. And that habit will take a longer to remove when it’s across a company. But if I had to start small, I find these three practical places are the best place to start if you want to test this without overhauling everything at once:

  1. Start with the threads. Make threading non-negotiable for a week. You’ll quickly see how much noise lives in the main channel that should’ve been contained.
  2. Pick one project and move its conversations. Don’t try to migrate everything. Take one active project and insist all related discussion happens in the task card. Compare the clarity after two weeks.
  3. Write down your SLAs. Even if they’re informal, have a conversation with your team about response times by channel. Put it in writing so new people don’t have to guess.

I wouldn’t want the goal is to eliminate chat. I want like it to to stop letting it run the business, killing processes and productivity along the way.

Leave a Reply

Your email address will not be published. Required fields are marked *