In a remote team, day-to-day communication happens asynchronously. While startups try to conquer the synchronous space, there is far less work happening on the other side. Let's take a look.
While Zoom is slowly becoming the undisputed champion in synchronous communication, Slack might need to make way for a different tool at some point. Not because Slack is a bad product, but because it's not truly asynchronous.
Our very own glossary classifies asynchronous communication as follows:
Asynchronous Communication (often referred to as "Async") is a form of communication that doesn't happen instantly. Contrary to synchronous communication – for example phone calls or a face-to-face talk – async communication is usually archived or saved somewhere for future reading. The participants therefore don't need to be present to receive the message.
The first part is definitely true for Slack, but the second part not so much: Slack does work best if used in real-time, when all participants are online. Discussions are sorted in linear channels, without much functionality around organizing discussions in an async manner, leading to offline participants feeling left out.
Slack is also known to be quite aggressive with its notification settings, "do not disturb" functionalities and online indicators, pushing it towards a more real-time, instant messaging tool.
If used right, Slack is the logical choice for remote teams. However, there is no support or guidance within Slack itself, so that it is going to be used right from the start, and it takes a lot of work to get there.
With the need of an async communication medium, many organizations are starting to depend more on the traditional e-mail again. That has a good reason, and multinational companies have communicated through e-mail for decades!
While e-mail itself are mostly staying the same, the clients aren't. Superhuman may be the most notable release of the last few years, but many companies – including Microsoft with MS Teams – is pushing towards a new kind of e-mail experience. E-Mail is getting a second life.
Quite probably, the best solution for this will come out of a remote team who struggles with this every day.
Both Slack and E-Mail are probably not the end solution for a remote team: They don't offer the right balance between flexibility and thoughtfulness.
There are a few things that these products have in common, and what makes them great:
This space is one to watch. Who is going to become the Slack of Async Communication?
If you forgot about Slack, and re-imagined remote communication from the ground up, how would that look like?
New generation communication tools mainly like to make use of other mediums of communication than text-only, and that has a good reason.
YAC is interesting because it took a concept which is – at least amongst the younger generation – very widespread (casual voicenotes), and reused it in a business context. Bundled with great UX and good values, it produced a tool which is helping hundreds of remote teams claim back natural discourse.
While this may not be the most productive way of communicating and organizing information just yet, it's definitely something too look out for as new tools pop up.
Deel makes hiring and working with remote talent easier. Deel simplifies compliance and payments for clients and contractors/freelancers.s It provides both parties locally or internationally with a reliable, seamless payment experience.
Knowledge databases are difficult to keep track of and are usually not handy when a question comes up. That's where OneBar helps.
Slack has changed the game for team communication, but when it comes to remote work, it has some crucial design flaws. How can you overcome them?