←back to thread

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

238 points aml183 | 1 comments | 15 Nov 24 19:17 UTC | HN request time: 0.218s | 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 #
ta1243 ◴[19 Nov 24 19:59 UTC] No.42187471[source]▶
Nothing team-related should be in email. It's a horrendous place to hide data - worse than even than slack private channels.
replies(1): >>42193778 #
1. 7k5kyrty45 ◴[20 Nov 24 13:30 UTC] No.42193778[source]▶
Only because we've ruined our email with automated systems that are way too trigger-happy on notifications. I think I've received atleast a thousand-fold amount of mail from JIRA that someone has clicked on something, compared to actually useful, actionable requests.