←back to thread

243 points aml183 | 1 comments | | HN request time: 0.21s | source

We are a remote company. Everything is going well. No plans to be in person, but I’d say we can do a better job at communicating. Any tips or articles to read?
Show context
paxys ◴[] No.42150868[source]
Make conversations public by default. If you use Slack, make team channels, project channels, announcement channels etc. all public. Discourage 1:1 and private communication unless really necessary, especially for engineering topics. This single change will have an immense impact on overall company culture.
replies(15): >>42150920 #>>42150993 #>>42151105 #>>42152006 #>>42152011 #>>42152642 #>>42155060 #>>42155607 #>>42158830 #>>42185599 #>>42185634 #>>42185891 #>>42185940 #>>42186302 #>>42192048 #
vundercind ◴[] No.42185940[source]
Teams badly fucks this up by not providing normal-ass chats that aren't private ephemeral-ish groups. Their "teams" only have these weird announcement-oriented chats with terrible UX and visibility for ordinary chat activity, so you end up having to do everything in meeting-tied chats (created by the meeting, not the other way around) or ad-hoc group chats.

You can fake it with lots of manual "pinning" but that relies on everyone agreeing which chats are primary and should be pinned so they don't start splitting messages over other chat rooms, then you still end up with things like chat for one basic topic being split across multiple meeting-chats that all have the same membership or (worse) just slightly different membership.

It's as if they designed the tool to make effective remote work hard—but this also (like most things that make remote work worse) makes using it in an in-office context worse. It's just flat-out bad.

replies(1): >>42185990 #
1. bsuvc ◴[] No.42185990[source]
100% agree.

The people making the decision to switch to Teams don't "get" slack.

They think the features are the same, so what's the problem?

Ironically, Microsoft Teams is terrible for teams.

It's a Frankenstein cross between instant messanger and SharePoint.