Also, the "new Teams" is missing functionality. It lost the auto-transcribe feature. Go figure.
Totally amateur hour work. I tried once to get my teammates to use Slack, but it's hard to adjust. Slack ain't perfect, but it just works in so many ways that Teams barely hangs on with.
Oh? You have out Windows 11 Pro/Enterprise for 1000+ licenses. We will throw in O365 for a year to get the org fully hooked.
Oh, need windows Active Directory as well? We can add 200 licenses with your existing windows licenses for 1-2 years.
(2 years later) oh your org is downsizing the internal ad sys admins? Don’t worry we got you covered with Azure AD!! Just cough up $250K every quarter. That’s like 1 senior SDE!!1
Oh hey we also have Windows VDIs, Azure Cloud, and other shit. Get into our walled garden. Never leave.
Teams does seem to be on a whole new level of terrible though.
Not to pile onto MS Teams, but it's by far the most amateur hour system I ever had the displeasure of being forced to use.
I feel they even managed to botch their transition from Teams Classic. Official docs were out of sync with the app's transition, whole features were missing, some features were suddenly only made available to pro users. What a mess.
Make no mistake: the problems with MS Teams are not technical. It's product design and management. It felt like a rush job where everyone involved failed to get their stuff out, product managers felt the mess was acceptable, and the senior manager still made the call to release anyway.
MS Teams is a mess for the ages.
I apologize for venting like this but I had multiple critical meetings being postponed and rescheduled because MS Teams failed to work in creative ways. This definitely did not happen with Zoom or Google Meet or Slack.
There is absolutely 0 feedback to show a speaker when their mic is actively transmitting. When anyone else in a call speaks, a ring around their avatar lights up to show you who is speaking. When you speak? Nada. Technically, you can open the settings menu and there is a mic level bar there... but it's not in the standard view.
As far as I've seen, Teams is the only chat app that can't get this right. Not only does it increase the rate of people trying to talk while still on mute, it gives you no way of knowing if sounds in your environment are transmitting to the meeting and disrupting everyone else.
My entire computer can be dying due to intensive cpu load and the teams call is fine. Zoom causes the cpu load. Google doesn't have basic controls.
I'm sure slack is fine but I've never seen anybody use it for external meetings.
Even so... it's better than slack for audio/video and my organization uses teams as primary for calls and slack for text communications(group chats, channels, dms)
Teams only just recently got to that level (like, in the last half of last year)
We are currently moving from Teams to Slack at my workplace and I miss the ability to view my full calendar, join meetings, schedule meetings, share common files, and call others all from one application.
Is there another application that does all that Teams does but better?
I prefer the subscribed channel where I make an intentional choice, and everything else is ephemeral.
I assume it's to disambiguate it from the 'classic' version, but seems like an odd name to use?
I'd +1 on how bad Teams is in general: a few weeks ago I got a popup in it saying "We've made teams even better!", and I thought "I bet you haven't".
Does anyone know if MS use it themselves?
Yes, extensively.
A presentation app where you can't freeze the screen share, a feature requested by hundreds of users 6 or 7 years ago...
It's use should be a firing offense.
"No longer has access to chat" - https://answers.microsoft.com/en-us/msteams/forum/all/no-lon...
"Freeze screen sharing" - https://answers.microsoft.com/en-us/msteams/forum/all/freeze...
which of their other pieces of software are any better?
But Teams is really terrible. And the move to "New Teams" was handled very poorly too. I had hoped it would improve things, but it is basically the same with slightly less RAM usage.
If you mean the DB server itself, sure. But for actually managing it, they've effectively killed further development of SSMS in favor of Azure Data Studio. And while Azure Data Studio is relatively fast and snappy, it's missing a lot of SSMS functionality. Meanwhile they refuse to implement a dark mode in SSMS despite it being the most requested feature for several years running now.
It did crappify somewhat in recent years, but still eons and mountains ahead of anything the competition put out.
I also wonder.. do they have a "UX" team? If so what are these people doing? The usability is abysmal.
We use Slack and Teams at my workplace and regarding chat Slack is lightyears ahead. Sadly the company wants to force more and more people off of Slack and into using Teams.
We are in the post COVID years now and more and more organizations are using it today.
Is it accurate to say they have no incentive to improve, given their dominance in the enterprise space and the complicity of some finance/IT departments into forcing it on their employees given the cost savings and the convenience?
Ummm .. Lync / SkypeForBusiness / Teams has been Microsoft's core communication product for long over a decade now.
It has always been part of their basic/essential packages because they know that everyone needs a communication platform.
How you managed to work at Microsoft on Teams and think that nobody knows about it, is a bit astounding.
Teams was a product for 3 years before Covid. A large amount of companies had been running it for 1-2 years at that point.
The idea that Microsoft built Teams as a Skype for Business replacement, but didn't design for scale or reliability is an absurd statement.
----
Either you are
(1) lying
or two
(2) worked on teams but had no understanding of the product or userbase.
... which kind of does sounds like how teams might have been built
Teams was very much the sleepy rest-and-vest corner of the company that people transferred into to quiet-retire. Teams is not just a reskinning/re-clienting of SfB's backend. They are separate systems.
We all know the code and development direction in teams is lacking. This is one problem.
Microsoft scrambling around COVID times with Teams had more to do with the load / demand / capturing market share, than anything else.
SfB stopped releasing in 2018, 2021 it was lights out no matter what .. everyone was already moving to Teams.
Trying to pretend that their main communication platform is not a "core offering" when it is the definition of one of their core offerings makes no sense.
And trying to say nobody knew about it, when everyone knew about it also makes no sense.
SfB was dead by the time covid started. Where do you think these people migrated to?
Also consider, Teams for Education as a market segment basically didn't exist before COVID.
My point is, many organization had a Teams license but never really pay attention to it until COVID. Which was another problem for Microsoft because although op costs for Teams went up like a hockey stick, they weren't monetizing that growth until a bit later.