Olle Pridiuksson

Anecdotally, this has nothing to do with remote work. I’ve been on remote teams where I was given TONS of opportunity to share my opinion and to act on it. I’ve worked in far more offices where I haven’t. That’s team culture, not whether your desk is in your house.https://twitter.com/rakyll/status/1153423031034793984 …

Garann, can you please elaborate or mb provide a piece of advice on how to best develop the remote team culture while keeping the Slack noise managed? Recording scrum demos? Video standups? Team puns channel? Quarterly get-togethers that cost a ton but are worth it? Thanks!

All I have is opinions, but what appears to me to work is 1) creating dedicated channels for specific things like stand ups and individual projects, and 2) making it a shared team priority to share things that spark conversation in the main channel

Sure sure... I just could never understand how to balance the noise vs meaningful conversations (how to qualify for "meaningful"?) ratio in general for distributed teams. For local teams it is clear, imo. But for remote...

I feel like we often underestimate the amount of noise in our in-person interactions and more importantly, the value noise provides

I humbly think noise provides at least cultural/sentimental team bonds, at max it also provides more work context. I could never figure out how to measure that though or how to approach the whole noise concept, esp in distributed/remote teams who wanna focus on getting work done.

Separate noise channel(s) + rules for what's allowed/disallowed/wanted in non-noise (aka work) channels, e.g. "no memes, don't use reaction emojis to acknowledge something". #channel participants is also a huge factor. Should follow #people working on a specific thing.

my humble opinion has always been that enforcing communication policies sort of breaks cultural/emotional bonds in the team, esp in the remote team where "noise" is one of the few ways of bonding daily. In dev communities I've always tried to cultivate empathy instead.