4 ms·
As a drop-in replacement for Slack (or our dearly departed friend Hipchat), Teams is a poor choice. It makes more sense when used organization-wide -- for meeti
by Gene_Parmesan 7y ago
As a drop-in replacement for Slack (or our dearly departed friend Hipchat), Teams is a poor choice. It makes more sense when used organization-wide -- for meetings, sharing/accessing documents, and so on. The chat portion works usually but it's probably its weakest point.
The bugs do need mentioned though. It constantly crashes for me, constantly loses sync, will just straight-up freeze for no discernible reason, will decide it doesn't really feel like actually sending my messages, and so on. It does not at all feel like a mature product.
Our team dropped HipChat and has moved to Teams along with the rest of the org. Our dev team (of 7) had used HipChat as a simple persistent chat app, sandboxed away from the rest of the company. Now we are on Teams with not only Ops guys, but also HR, marketing, and so on. It's fine at being sort of an organizational tool, but we dearly miss having our own private chat-only app that we can make use of as we want/need. Partly this is contextual to our organization, but the way we use Teams now feels far more formalized, and not in a good way.