There, I said it. I said the S word. More specifically Teams versus Slack. And no, I don’t hate Slack. I think its great actually! It has it’s place as do most productivity tools do. Heck, I still use it for our DnD sessions! But that’s because I don’t need anything more complicated than a private messaging platform. I’m not crazy… Just hear me out.
I recently saw an article from the University of Technology Sydney that said Slack lost the showdown with Teams, and I’m still bitter about it. and I thought it was an interesting read.
Mainly because I think their selection method was a little misguided. 90 seconds to pitch one against the other in a public audience seems silly especially when they are both different things.
It’s like comparing a Motorbike to a Ute. The Motorbike can get somewhere really quickly. But it has to call its mates as soon as you need to carry something other than a backpack. The Ute however can get somewhere quickly and carry stuff with music and aircon and has the added benifit of airbags in case someone hits you.
In my mind teams is not designed to be “Slack competitor” alot of people think it is because its “Chat first”
As far as I’m concerned (Yes, I have been at Ignite this year and drinking a bit of kool-aid recently) Teams has alot more on Slack out of the box.
Yeah sure there are heaps more apps for Slack than Teams and more IT Pro features but that’s because it was born out of a developer centric mindset where we automate and know keyboard shortcuts for everything.
Teams guiding light seems to be embracing the entire workflow, not just the code cutters or the discussion on something before farming the document storage off to another app. Adding with it another account and another set of compliance headaches.
So a business unit can pickup Teams and with a few clicks has SharePoint, OneDrive, native collaborative editing (no fiddling about in google docs settings), Calling, Meetings with PSTN dial in and Video for their next project! All with very little interaction with “The department of No!” (the IT Dept)
This lets us focus on making the experience better rather than trying prove to higher ups that all these third party solutions are compliant. With a simple “It’s stored in our existing Office365 tenant” you have turned weeks of auditing and emails back and forth into a non-discussion.
Add to that that Teams has the engineering nouce of the Skype for Business team behind the AV side and you start to see how having everything in one product makes sense.
You’re not going to see Slack based phones or Meeting room devices anytime soon. Sure, I’ve been fighting for headset’s first for years. (Look at all my headset reviews) But they don’t always fit the bill. Sometimes you need a phone at Reception for when its unattended, a paging system, a door phone at a loading dock. All things I don’t see an elegant solution when using a chat focused app like Slack or even Discord for that matter.
What about when you need to call that external call center? Are you going to send them an invite to install Slack? or are you going to call them on the phone?
I’d be interested to see your thoughts below.