Skype for business had a 60% favorablity rate when we rolled it out. Teams has a 95% favorablity rate. People love it, find it easy to use. Their two biggest gripes are needing more video feeds like zoom, and the ability to pop things out
With all due respect, you're going about this backwards. * Define your requirements * Break them out into Must Have and Nice to Have Look at multiple products that meet your requirements, maybe tracking them in a matrix. Function, cost, support, etc. Let the data make your business decisions, not strangers on the Innerneck.
The heavy integration with sharepoint online and the creation of o365 groups slowed down initial rollout as we had to plan out permissions and the grouping of our teams. We also had to turn off allowing everyone to create teams as it was creating groups visible in the exchange email lists with similar names. Past that it has been great.
I like the agility that it's allowed for our large company to go remote rather quickly. I moved us to a teams based phone system almost overnight. If I could ask for one improvement it would be different themes for the client and conversation. I can't count how many times I've accidentally said something in the wrong thread because it all looks the same.
MSFT Teams was very good once our organisation figured out how to use it properly. And at the rate they are developing it, a lot of the concerns I had 3 months ago have been fixed or at least attempted to be fixed.
Love the integration with the other Office products and Office 365 / Microsoft 365 products we already use. It's a no-brainer if you're already using the other pieces.
My one word of caution is be careful when deleting channels. In the early days we played with Teams but didn't use it that much. Created Teams, Channels etc and then deleted some channels. Came back to it a couple months later and tried to create some of those standard channels i.e. Sales, HelpDesk, Operations and couldn't create them, name is in use!! Turns out there's no way to permanently delete a channel and if you don't rename it before you delete it then there's no way to reuse it again. Turns out if you don't restore it within 30 days (I think it was 30) then you can not longer restore it to use it or rename it, it's forever stuck in nowhere land. Really irritating as you have to stay on top of it for clients as they can easily fall in this trap of creating and deleting channels and someone will eventually want to use that same channel name again down the road. The other thing that's a huge pain is as an IT provider we work with a number of clients and the fact that if we're a guest of their org (able to access sharepoint resources for example) we then have to switch between tenants when using Teams, we can't just say in our Tenant and communicate making it really useless method of communication because people will send you chat messages that you'll inevitably miss. This is probably the worst part for us. Otherwise it's been a pretty invaluable tool in this move to WFH for all our clients.
Controls around team owners are lacking, ability to only see 4 webcams at once in a meeting. Other than that it's great and an everyday part of my day.
It takes a little to get people who are not used to slack to get it but we moved over 3 months ago and I couldn’t imagine not having it
I find it fine when it's just internal people using it. When we need external people to contribute, it tends to fall
Put it this way, most users on Slack/Zoom aren't wishing they were on Teams in my experience. Your org will move to Teams regardless as it's better for security and admin. We use it but too many features are 'coming soon' - I find myself on Teams Uservoice pages too often to see that everyone is screaming for basic stuff and Microsoft's reply is 'We're working on it' or similar.
My perception might be biased in that in our engineering team we didn't need an "email replacement", so coming from Slack, Teams is a lot worse. For one thing, it just feels heavy and slow (search is especially bad) and doesn't fit into our conversational flow (we mostly never use the teams themselves but chat channels because of this). Second, the integrations are overall worse and it's a lot harder to write your own compared to the Slack API. Third, and this might well be because of our admins, but it seems like the speed at which new features are added/enabled is glacial. And don't get me started on having to invite outside people to a team. But what it has going for it is that it's so much better than Skype for Business, and being able to schedule a meeting in a particular team, record it and have the recording available right there via MS Stream (including the chat) is pretty nice.
No I don't. I like how you were able to put your status on away or busy or invisible but you don't have that option in Teams. This is something they really need to integrate in it now because Zoom is about to take a lot of business away from them.
Yes. Though this is like asking if I like my iPhone. I do. But the reasons I like Teams may be completely different to why YOU would like teams.
Give this a peek. Pop down to existing Teams site instructions. This is from ShareGate, not MS but pretty good. https://sharegate.com/blog/microsoft-teams-sharepoint-integration-how-to-adopt-teams-existing-team-sites#create-team-site
My biggest issues involve the inability to pop things out to separate windows... having multiple different chats going on at once is \*painful\* .. That is something that Skype for Business (which it replaces) had that is Sorely Missed. That feature has been "Coming soon" for Teams for over a year now :(
Thank you all! Your responses have been a great help...
Don’t like it. People who were on various crappy products previously or people who love Microsoft eco-system seem to really like it. I feel bad for them for not knowing there’s a better life out there. I will say it’s one of the better Microsoft products I’ve used, but still lacks good UX in many ways. Slack for example is a superior product. - Teams has a poor UI - it’s not easy to see all your channels - Chat within a channel is not easy to read - The structure and how they push you to use group chat sucks (you’ll end up with tons of group chats) and no threads in group chat - No inline commands sucks - lack of granular notifications setting - if you have to bring in users outside your org (contractors, etc) you’ll have problems and they won’t want to do it - lack of @mention abilities I could make a list of another 20 items. There is a reason that Microsoft is bundling Teams with other products. Way less people would choose to be on Teams if they weren’t getting it for “free”. However I would argue the productivity and effectiveness losses by being on Teams are more expensive than the money you “save” by being on it. If your org is all in the entire Microsoft suite of products then that definitely helps. Also, I think a common issue that clouds this conversation is that lots of org has other poor products (video calling, soft phone, etc) and so Teams feels like a improvement but it’s actually a better tool in those areas but not a better tool when it actually comes to chat/email replacement.
Honestly, I think it’s a mess. It has a lot of good communication features but it is hard to wrap your head around and really hard to explain to others. Our biggest gripe is that you can’t choose the base sharepoint for the team. It’s makes it’s own sharepoint when you create a team. We have a sharepoint site for each of our departments and now every department has a team with a separate sharepoint. This causes a lot of confusion. People share documents within the team and wonder why the document they dragged in is not updating on their department sharepoint.