cmswire-logo-01

Teams vs. Slack Debate: Which Is Best for Collaboration?

By Mike Prokopeak April 19, 2022

Salesforce’s Slack and Microsoft’s Teams both offer important collaboration capabilities for the digital workplace, but they’re not the only game in town.

There’s a multitude of tools available today that enable workers to connect, collaborate and exchange ideas, share updates and network across the digital workplace. However, over the past two years, a lot of the air in the discussion has been sucked up by two in particular: Slack and Teams.

It is arguable that the reason Salesforce’s Slack and Microsoft’s Teams have dominated the conversation these past few years is because of highly publicized mudslinging between the two companies. The current debate centers around data published by Microsoft that shows Teams has greater traction in the enterprise. Slack has questioned how Microsoft is compiling its Teams usage figures, leading to some interesting verbal exchanges between the two companies.  

SaaS intelligence firm Productiv recently took a look at the issue by analyzing an anonymized subset of data to determine how employees of Productiv’s customers use the two apps. The results over a period of 60 days in July and August 2021 showed Slack well in the lead, with 83 percent of engaged Slack users, compared to 42 percent engaged Teams users.

So, is Microsoft lying? Well, no. The results of the Productiv study aren’t that black and white. Writing about the research, Kristin Crosier and Jin Baik of Productiv said while Slack has more engaged users, Teams still has the upper hand for certain use cases.

The State of Current Engagement

In the fast moving digital workplace, the arguments may seem close to irrelevant. Microsoft and Slack have been slugging it out since the beginning, so no one is paying much attention anymore. What’s more important is engagement with collaboration tools and how workers are interacting with these products.

In its study, Productiv measured engagement — defined as something that happens when a user logs in and completes a task using an app or a platform — across the following variables:

  • Engagement with each application over one day, seven days, 30 days and 60 days.
  • How engagement varied across specific teams.
  • The distribution of engagement percentages across companies.
  • How the features of each application were being used.

The findings indicate that Slack has higher engagement, with more than twice the daily user engagement when compared to Teams. However, that is not the only story. According to the research, while Slack has more engaged chat users, Teams prevails for meetings. There are three notable figures:

  • Private messages: Over 30 days, 89 percent of engaged Slack users interacted with private messages, compared to 60 percent for Teams.
  • Group messages: 92 percent of engaged users in Slack used the group messaging feature over a 30-day period, versus 11 percent of engaged Teams users.
  • Meeting attendance: 62 percent of engaged Teams users attended a meeting over 30 days, compared to 13 percent of engaged users who attended a meeting through Slack.

This is probably not surprising for anyone who has access to both platforms in their workplace. Explaining the difference in use cases, Crosier and Baik wrote: “Microsoft Teams’ out-of-the-box integration with Outlook may help explain why meeting attendance is significantly higher for Teams.”

Related Article: The Future of Video in the Virtual Collaboration Market

Should Enterprises Deploy Both Tools?

Considering users typically engage with Slack and Teams for different purposes, what should organizations do?

George Prior, vice president of IT at Vista, Calif.-based ServiceNow provider NewRocket, said the case for Slack vs. Teams depends on the use an organization intends to make of the platforms. Despite usage differences, the two share several core collaboration capabilities such as video conferencing, instant messaging, file sharing and integrations with other systems. 

“Both tools offer like functionality and have some differentiation,” said Prior. “Teams definitely higher targets video usage because it replaced Skype, so it was a natural pivot. MS Teams is also a [unified communication as a service] system, so telephone and video teleconferencing are natural offshoots. Slack is very much messaging specific and leverages that.”

Does this mean that enterprises should be using both tools? According to Prior, it doesn’t make financial sense to deploy both tools because they have too much overlap and not enough differentiation. In an organization with centralized IT, the CIO will usually choose one. Only in organizations where there is some decentralization would you expect to see both tools deployed, he said.

“From a management perspective, managing both products requires higher headcount and security controls, so that tends to negate the need for both,” Prior said. “In very small organizations that are, for example, 50 seats or less, it is probably more likely for [both Slack and Teams] to be deployed. However, once you reach the SMB space and higher, it is unlikely you will have both except for some very specific use cases.”

Related Article: Collaboration Tools for Remote Workers Are No Longer Enough

Find the Right Mix of Synchronous and Asynchronous

User engagement across the two collaboration tools varies depending on the user’s intention, said Anique Drumright, vice president of product at asynchronous video messaging platform Loom.

With live video, there is richness of live discussion but it can be time-consuming. Citing a recent Loom survey, Drumright said when meetings were reduced by 40 percent (the equivalent of two days per week), the company found productivity to be 71 percent higher because employees felt more empowered and autonomous.

Meanwhile, text communication is faster and more scalable but stripped of nuance, tone and humanity. The key to finding the right tool to ensure employee engagement lies in finding the right mix between synchronous and asynchronous communication to improve workplace productivity, flexibility and autonomy. 

Sourced from CMSWIRE