5 ms·
Disclosure: Microsoft employee. Using a throwaway. Satya, please don't track me down and fire me. I've never agreed so heavily with a headline and disagreed so
by throwaway7000 7y ago
Disclosure: Microsoft employee. Using a throwaway. Satya, please don't track me down and fire me.
I've never agreed so heavily with a headline and disagreed so vehemently with the actual content. Some of this is right, but a big chunk is wrong and I think misses some of the most egregious horrors of Teams.
I used Slack professionally before in a fairly large org (>200).
Two things the author got wrong:
First - things the author got wrong. Notifications are absolutely configurable by Channel - at least with the bits I'm on and how the internal Microsoft tenant is configured.
Second, a huge portion of the things mentioned by the author are config switches that apparently his tenant admins decided to muck with (auto-adding to Teams, no outsiders, etc).
The biggest complaint I have about this piece is it doesn't actually talk about some of the real, most egregious parts about Teams:
Teams has atrocious search, performance (functionally and by footprint, and UI - which the author covered.
On top of that, it seems clear that the Teams team didn't have a coherent vision for the user/grouping model, so channels are kinda treated like groups but so are channels? For instance, you can mention a channel from another channel. Wtf. This drives me insane on a daily basis.
The development story is a mess. Not going into details here but if folks in the comments care to peruse the docs, I'd love to hear other folks' perspective.
Other random complaints:
- The emoji story is hilarious. There's a taskbar thing called "emoji" which are animated stickers (some of which are actually fantastic) but definitely aren't emoji. You used to be able to shortcode emoji (ie :smile:) and get a thing that looked like an emoji but still wasn't unicode emoji. AND you could use the actually emoji keyboard on your device to actually type unicode. So, 3 ways to get 3 separate sets of glyphs, all referred to as "emoji". Yes, I know this complaint is dumb but it shows a weird lack of attention to detail.
- The formatting story is the union of every formatting concept ever. Quasi-markdown is supported inline, but its essentially an editor trick that triggers (what I assume is) richtext formatting.
- This is ANOTHER thing trying to be the* dashboard in Microsoft's product suite. There are like... 7. PowerBI, Azure Devops, SharePoint... Teams... I'm sure I'm forgetting some. Which leads me to...
- It was clear from early development that leadership wasn't fixated on "do one thing well" and were trying to be the sum of all productivity goals. The result is chat sucks, feels halfassed and there's a lot of stapled on shit that makes the experience gross.
There are a lot of smart people on this team but the folks at the helm set things on a terrible course that misses the fundamentals, which is super depressing.
As an aside, one thing I'm genuinely curious about from folks that use Slack in very large orgs (>500), how does Slack's usability scale?
- alexandre_m 7y agoBeen using Slack on a daily basis for work since 2015. We have a fairly large group of users from different departments (IT, admins, engineers) of > 1500. I would keep it succinct and say it's excellent. We're much more efficient at communicating than we used to be.
- OhSoHumble 7y agoMy organization is replacing Zoom with Teams and keeping Slack. I have two problems so far: 1. I'm an engineer that uses Linux. Zoom has a native Linux client that works really well. Teams doesn't work on Firefox and doesn't ship a Linux client - despite being an Electron application. I can use Google Chrome to call in but if I need to share my screen then I have to switch off all my monitors because Chrome's screen sharing functionality is a little bit broken. There is a PR against Chromium to fix that. 2. The UX of Teams is garbage. Nobody can figure out how to use it because it has so many features. With Zoom, there are like four buttons. I can join a call or I can host a call and figuring out how to do either is incredibly easy. I would never want to use it as a chat application because that would be awful. Our IT department wants everyone in the company to use Teams because they all like Windows/Microsoft and it comes for free with our Microsoft suite contract.
- sytringy05 7y agoI wholeheartedly agree with the emoji thing. Seems simple and unimportant but it's a way to communicate and teams is terrible at it. the people who work on teams seem nice though, I actually got a helpful answer to my SO question about emojis: https://stackoverflow.com/questions/53384141/teams-webhook-send-emojis-in-notifications https://stackoverflow.com/questions/53384141/teams-webhook-s... oh and the formatting thing is a disaster. Something slack go so right - (markdown text input, styled on rendering), Teams gets so wrong (a way too easy to break rt javascript horror. entering code snippets is a nightmare, ` type something ` hope the "code" box pops up. `` right after each other - nope.)
- brynjolf 7y agoReading this thread [0] on your Uservoice shows that no progress has been done since August 2018 on notifications management for the end user. I'm sure you allow control when you create a channel but convincing the teammanager who very day pings the entire channel to say their work hours that day is impossible so that feature is more or less useless. The fact that you can praise coworkers with unicorns is implemented before proper notifications has made me go from believing in the future of Teams to now praising Slack. It is maddening. [0] https://microsoftteams.uservoice.com/forums/555103-public/suggestions/20592283-mute-a-channel-mute-chat-is-complete https://microsoftteams.uservoice.com/forums/555103-public/su...