←back to thread

244 points aml183 | 1 comments | | HN request time: 0.202s | 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
why-el ◴[] No.42185886[source]
I learned the following:

- Everything public in Slack. Create a fun-sounding moto that discourages DMs. Even if a DM happens, and the back and forth resulted in a consensus, share that consensus in a public channel (which makes it searchable).

- Record your team meetings, preferably with software that can AI-summarize. Folks on vacation / leave can get the rundown easily.

- Encourage the sharing of solutions to various problems (technical or otherwise) in Slack. If a developer is stuck, and someone helped them in a huddle or a pairing app, share the solution afterwards (again, makes it searchable). Discourage the over-sharing of screenshots (of your application and other things). Again, not searchable. If one must be shared, describe it. For instance, many devs share a picture of a stack-trace. Not super helpful for others. Grab the text and dump it to Slack.

- Have a good pairing software setup, unblocks for when Slack back and forth is too tedious. I like Tuple (tuple.app).

- Connect your issue tracker to Slack, if you use one, makes creating issues easy. Linear does this well.

- If feasible, have your team meet in person, cadence up to you, but at least once. Meeting the people in real life humanizes them more. I know it sounds silly to say, but it's very true in my experience. Your people will seem even lovelier.

replies(17): >>42186106 #>>42186307 #>>42186329 #>>42186525 #>>42186829 #>>42186914 #>>42187317 #>>42187945 #>>42187974 #>>42188264 #>>42188551 #>>42188809 #>>42188843 #>>42188885 #>>42190285 #>>42193704 #>>42194033 #
patrickhogan1 ◴[] No.42186525[source]
Great list. Add a few..

1. Meet in person every quarter. Fly people into the HQ if there is one. If not just rent meeting place.

2. Have a well written handbook like Gitlab that explains how your company works.

3. Onboarding program - remote onboarding sucks. Do onboarding in person (if you can) or assign an onboarding buddy if you can’t.

4. Slack Is Great But (SIGB) - teach people that they don’t need to read everything. Many people get overwhelmed. Great engineers don’t read everything nor should they. Let everyone know that it’s a shared brain or knowledge source - and it’s ok to turn it off to focus.

replies(5): >>42186608 #>>42186836 #>>42188763 #>>42188950 #>>42193674 #
7k5kyrty45 ◴[] No.42193674[source]
>Meet in person every quarter

What benefit would you see in doing this? The only thing I've heard is some consider it nice to be in close proximity to others, but that doesen't really sound like a business reason

replies(1): >>42194064 #
j33zusjuice ◴[] No.42194064[source]
Quarterly would be a gross misuse of budget, imo. I think there’s tremendous value in physically meeting your team—-I can’t quantify it, but I can feel it—-so once a year is good, to me. Maybe twice if one is business and one’s a party or something.
replies(1): >>42195835 #
1. setsewerd ◴[] No.42195835[source]
Seconding this. My team meets annually for several days, at a conference that gives us plenty of social time together in the evenings.

As you said it's hard to quantify the value, but anecdotally I notice it most in 3 (distinct but somewhat overlapping) areas:

(1) Overall morale - everyone enjoys work more when you have a good relationship with your coworkers, so people are willing to do more than the bare minimum. People approaching burnout feel more enthusiastic about work afterwards. (2) Everyone is more inclined to help each other out with tasks outside of their routine but within their skillset, reducing bottlenecks. (3) Similarly, you develop a better sense of each other's personalities and skillsets in a way that's much more difficult when remote, so communication is more efficient, and collaboration more effective due to that increase in understanding and empathy.