←back to thread

Ask HN: How do you communicate in a remote startup?

243 points aml183 | 1 comments | 15 Nov 24 19:17 UTC | HN request time: 0.371s | 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
kingkongjaffa ◴[15 Nov 24 19:44 UTC] No.42150186[source]▶
Slack / IM often, don't demand a response instantly though, async & remote go hand in hand.

Put important stuff in email not slack/IM

Have a company wiki

Prefer video calls for alignment

Write to each other often, spend time crafting written narratives, 1-pagers, amazon 6-pagers etc. to share ideas, make people read them, use google docs or ms word online and get comments inline in the document using those tools, follow up on video calls to confirm alignment.

Gitlab has a handbook for this stuff, they are a 100% remote business and very open about their practices: https://handbook.gitlab.com/

consider personal readme's if your team is a bit larger (example): https://gitlab.com/swiskow/swiskow

replies(3): >>42186214 #>>42187413 #>>42187471 #
1. shortrounddev2 ◴[19 Nov 24 17:48 UTC] No.42186214[source]▶
> Put important stuff in email not slack/IM

I personally think important stuff should be in public slack/teams/whatever channels. I pretty much never use email for any communication; the amount of spam I get, even on my work email leads me to ignore basically all email notifications I get. If I really need someone to see some information, it goes in slack. Email is only used for external communication, and even then if both orgs use slack we just create an external channel instead. I get crap for this on HN every time it comes up but I just can't stand email as a communication medium