←back to thread

238 points aml183 | 1 comments | | HN request time: 0.213s | 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
danjl ◴[] No.42186923[source]
Use Google docs. Ideally, everything or as much as possible should be public and accessible to anyone on the team. Especially planning and scheduling documents. Each meeting should have an agenda attached to the meeting on the Calendar. Each meeting should be transcribed and then summarized using Gemini.

Minimize the unsearchable communication tools, like Slack and Discord, though these tools are fantastic for casual conversations. Everything possible should be done to minimize notifications from Slack/Discord. In fact, minimize interruptions as much as possible to maximize the asynchronous benefits of working remotely.

On the development side, everything should be code reviewed before merging to main, as this helps spread knowledge and increase the signal:noise in written communications.

On the business side, all customer meetings (many of which should use GMeet), should be transcribed and summarized so the developers and other folks can be as close to the customer as possible.

Meet in person as a whole company AT LEAST once per year, perhaps 2-3 times. This can get expensive. As the team learns each other, the frequency can reduce. During periods of employee growth, increase the frequency.

Read "Remote" and other books by the Basecamp team.

replies(1): >>42186971 #
sandbx ◴[] No.42186971[source]
we also use Google Suite. Google Doc's [] task button is very helpful. We use a single to-do list for the team, which helps keep everyone on the same page
replies(1): >>42187288 #
1. danjl ◴[] No.42187288[source]
Right. Also use the @user comments to notify people as needed.