Yes, it’s mind boggling. Complaining about Teams is a daily ritual. We all hate it, and we don’t understand why we can’t have something better.
Unfortunately the source code is unavailable as well as the APIs, otherwise many of us would have already re-skinned it.
But we don’t use the chat as much as you would in slack, because it’s totally broken. We mostly just take lots of videos calls and share notes with an internal pastebin/gist tool.
It'd be in Microsoft's interest to make the product they sell good enough for their internal use rather than make a second product and sell an even less improved Teams. Dogfooding at its most basic. The exception would be if they were planning on changing direction with what they offered customers, in which case it doesn't make sense to dogfood the existing product anymore.
saw the discussion in another thread for softwares used in medical, not easy to use, one reason someone mentioned is that the purchaser does not use it much, the real users(doctors/nurses)' voice are probably not heard enough.
wondered about some ux inconveniences in teams, if MS use it internally, should have improved it... :-)
It is not like they are not working on improving things. I will even go as far that getting control of electron was a big motivating behind purchasing GitHub. Moving to Chromium based browser if also part of the plans to get access to and being able to improve Teams. Teams is such a central piece of software to Microsoft and many other Microsoft products and services evolves around teams but to replace the Electron part of teams with something better is apparently not an easy task. Teams for private people, that ships with Windows 11, does not use Electron (uses a webview instead) is part of this mission. I haven't used it as I also hate Teams and have zero desire to use anything teams outside of work, but from what I understand it should be much more performant and useless resources than the Teams for Work Electron app.
slack is built with electron, cannot blame electron much.
probably not fair to compare Teams and slack, as you said, MS has more things to consider for Teams than slack... while seems even some minor things, it is kind of annoying, can be easily fixed, but stay like that for long time... thinking if the Teams product team folks use the product and care, they should have fixed/improved...
seems this is common for MS products, powerful, many functions, but do not care enough for UX..., and one of things makes it different to apple :-)