A company I worked for produced, among many other products, performance monitoring software for alerting on poor perf of internal apps/databases and could tell you where/why it was slow. Yet, our engineering group mostly depended on users telling us when our internal apps were slow because the company didn't actually roll out its own product internally.
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.
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... :-)
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 :-)
I have this script saved on my Desktop under name useteams.ps1 and I have to run it sometimes multiple times a day.
Finance at Apple probably uses Excel because the finance industry uses Excel.
That being said, I would imagine that for most applications, any speadsheet program is fine.
They are dogfooding it, wich is the way to go, however, the client is pretty poor quality, some people behind it left the company recently btw