At this point, let us highlight once more that we were not looking for software featuring documentation exchange, planning, task and bug tracking, source control and solving other technical tasks. We have already successfully implemented all the required software, solutions and tools. So, our challenge is to create a space for corporate and personal communication, sharing company news, chatting and flooding, after all — for all that rapport that we miss when switched to remote work.
To proceed, we registered for a trial and created accounts in all three tools, installed desktop and mobile clients. We tried to apply selected solutions in a real-life working environment and everyday communication and tasks to evaluate how convenient and efficient one or another tool is, whether it fits our needs. And we would like to share our thoughts and comparison of Workplace, MS Teams and Slack based on our usage and practice.
We do not claim to make a full, complete and detailed analysis of the functionality of all the selected tools, as well as we are not going to mention all the pros and cons of each of them. We would like to notice that user experience in Workplace, MS Teams or Slack depends significantly on personal preferences and specific usage scenarios. Our comparison is instead a matter of our own opinions, based on what we liked, what did not in regards to our expectations and company needs.
What we expect from collaboration tools
So, what do we really want to get from socializing tools? We have defined seven categories of what we expect to receive from software:
-
availability of highly-functional desktop and mobile applications
-
a developed system of collective and personal chats
-
audio and video conferencing tools
-
feeds or newsboard both a corporate one for a whole company and separate ones for dedicated teams
-
configurable notifications (we want to be sure that ongoing business messages are visible, checked and solved, not the way people scan Facebook feeds)
-
integration with third-party applications and tools(a calendar, Jira, Confluence, Git and other office tools of all sorts) and additional functionality.
Let us start over :). Since we are talking about an everyday working tool, a vital factor is the availability of desktop and mobile applications. We consider checking one of the dozens of open browser tabs all the time as less effective. In this regard, all the three compared systems are formally parity, since all of them offer applications for Windows and macOS, as well as for Android and iOS platforms. Some of them may also support Linux, but it was not our focus. Also, we did not check how many macOS versions they support, so there may be limitations. A significant difference is that, while Teams and Slack provide almost the full range of functionality in their mobile and desktop versions, Workplace from Facebook is complicated :). Firstly, following its tradition, there are two mobile applications for Workplace: one is intended for viewing the feed, and the second is for chatting. Very convenient, isn’t it? Secondly, the desktop application supports chats only. It also shows notifications on events in the feed, but when you click on such notification, the post itself opens in the default browser. In general, among the implementations of other desktop clients, the solution from Facebook looks interesting least of all.
Comparison of MS Teams, Workplace and Slack
Working with the compared tools for a couple of weeks, we tested them on compliance with our categories of expectations, and we filled the following comparison table with our notes and comments.
Chatting functionality comparison
Feature |
Workplace |
Teams |
Slack |
Comments |
Edit messages after sending |
No* |
Yes* |
Yes |
Workplace: If someone has read a message, the sender can delete the message locally only. Other participants will see the message in the chat.
Teams: A sender can edit a message, but the original message will be saved in the notification feed.
|
Delete a message after sending |
Yes |
Yes |
Yes |
|
Send multiline messages |
Yes |
Yes |
Yes |
|
Use rich formatting in messages |
No* |
Yes |
Yes |
Workplace: However, the tool supports simple formatting with selection modifiers like ** for bold, * for italic, etc.
|
See the information about participants that viewed a message |
Yes* |
Yes |
No |
Workplace: The desktop client, along with indicating a person, shows the time when a message was viewed, while in the web and mobile clients, a mini-avatar of the person who viewed the message is displayed only.
|
Like or tag a message with an emoji |
Yes |
Yes |
Yes |
|
Send attachments in a message |
Yes |
Yes |
Yes |
|
Drag-n-drop attachments |
Yes |
Yes |
Yes |
|
Quoting a selected post for a reply |
Yes |
No* |
Yes* |
Teams: In desktop and web clients, a user cannot quote the message, but the quotation feature is available in a mobile client.
Slack: Replying to a message in Slack, a user starts a separate thread for discussing the original message.
|
Forward the selected message to another chat |
No |
No |
Yes* |
Slack: However, not every message can be forwarded, a user can’t forward messages from personal one-to-one chats, or to another team’s channel.
|
Set a self-reminder for the selected message |
Yes |
No |
Yes |
|
Set a message delivery priority / Appoint a reminder about a message to a receiver |
No |
Yes |
No |
|
Bookmark a message |
Yes* |
Yes |
Yes |
Workplace: The desktop client does not allow to view the list of bookmarked posts.
|
Pin a message |
Yes* |
No |
Yes* |
Workplace: The feature of pinning a message is available for a web client only.
Slack: A user can pin more than one message to a selected chat or channel.
|
Search by posts |
Yes |
Yes |
Yes |
|
Disable or mute chat notifications |
Yes* |
Yes |
Yes |
Workplace: Only web client users can enable or disable notifications.
|
Group chats / Structure chats hierarchically |
No* |
Yes* |
No* |
Workplace: A user can pin or mark as favorite the selected chats and channels.
MS Teams: The tool allows extended functionality of grouping by a team or a chat.
|
Audio and video calls comparison
Feature |
Workplace |
Teams |
Slack |
Comments |
A call recording |
No |
Yes* |
No |
MS Teams: As an additional feature, a call recording can be shared via Microsoft Stream.
|
Screen sharing |
Yes |
Yes |
Yes |
|
Collaboration functionality comparison
Feature |
Workplace |
Teams |
Slack |
Comments |
Create posts for common communication |
Yes |
Yes |
Yes* |
Slack: Communication activities are divided into different chat and channels, so, in Slack, it is just a specific channel or chat.
|
Create polls |
Yes |
Yes |
No* |
Slack: To create a poll in Slack, you need to integrate an external application.
|
Rich formatting in general posts for the whole team |
Yes |
Yes |
Yes |
|
Availability of live feed / news feed |
Yes |
Yes |
No* |
Slack: It is a general chat (channel) for all employees in Slack.
|
Collaboration over a shared post |
Yes |
No* |
Yes |
MS Teams: A user can share a document in a new chat tab for team collaboration.
|
Notifications comparison
Feature |
Workplace |
Teams |
Slack |
Comments |
Availability of Tray Icon for a desktop application |
Yes |
Yes |
Yes |
|
A notification (with color or icon change) about new events in the tray icon |
No |
Yes |
Yes |
|
Automatic status update depending on the meetings planned in the calendar |
No |
Yes |
No |
|
Automatic status update depending on current activities (on a call, away, outside of working hours) |
No |
Yes |
Yes |
|
Integration with Windows Notification Center |
Yes* |
Yes |
Yes |
Workplace: When a user of a web application clicks on the notification window, the chat loads painfully long.
|
Configurable notifications (the separate setting for different channels, settable intervals, the Do Not Disturb mode, etc.) |
No |
Yes |
Yes |
|
Notifications on missed chat messages by email |
Yes |
Yes |
Yes |
|
Integrations comparison
Feature |
Workplace |
Teams |
Slack |
Comments |
Two-way integration with Outlook Calendar |
No |
Yes |
No |
|
Synchronization of shared clouds documents with a local folder on a computer |
No |
Yes |
No |
|
Additional functionality comparison
Feature |
Workplace |
Teams |
Slack |
Comments |
Command-driven operation acceleration |
No |
Yes* |
Yes* |
MS Teams: A user can enter a command in the universal search and command line.
Slack: Commands are available in the chat message input field directly.
|
Integration with the external telephony (PBX) |
No |
Yes |
No |
|
Analytics and statistics sent to an email |
Yes |
Yes |
Yes |
|
Create an organizational structure and chats according to it |
Yes |
Yes |
No |
|
Integrations with third-party applications |
No |
Yes |
Yes |
|
Results of collaboration tools comparison
What did we get as the results of our research of Workplace, MS Teams, and Slack as tools for collaboration and communication? As you can guess the age of miracles has passed, each of the compared software systems has strengths in the area it is intended for and according to the business focus and experience of the company, that provides the solutions.
Workplace
Workplace resembles a social network, with a feed of posts, which is good, of course, at one hand, though it is not clear how to engage a user to make posts there, because a chat which is the most frequently used functionality, is not integrated with posts at all.