4 ms·
Arguably, those differences come from size of the core/target market. Slack targeted small companies and startup. Teams targets corporations. A lot of its desi
by TeMPOraL 3y ago
Arguably, those differences come from size of the core/target market. Slack targeted small companies and startup. Teams targets corporations.
A lot of its design decisions make sense in this context: for example, the reason "you have to invite, to be invited, to already know who to speak to" in Teams is that because you can't exactly fit 10 000 employees and an unbounded number of contractors and external parties in a vertical list, and tell the users to scroll through it. At this size, you need some discovery / matching process to even figure out who to write.
This also drives many of the "barriers" in Teams - you can't expose everyone to everyone else by default, because the CPU (and the notification counter) would have trouble keeping up. Instead, with everything being need-to-know by default, a new employee is going to start in a small, cozy team space, and gradually expand their list of contacts and team memberships. However, they're not actually isolated - the megacorp is still there, thousands of teams, tens of thousands of people, all accessible through that unassuming search bar at the top.
- regularfry 3y ago> all accessible through that unassuming search bar at the top. And there's the problem. Slack also has that search bar, but it also has public activity so you have a chance of knowing what to search for. The discovery process is the public conversations. > This also drives many of the "barriers" in Teams - you can't expose everyone to everyone else by default, because the CPU (and the notification counter) would have trouble keeping up. This is just not a problem. If you've got notifications on by default for busy public channels, you're going to have a bad time.