←back to thread

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

238 points aml183 | 2 comments | 15 Nov 24 19:17 UTC | HN request time: 0.001s | 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. gorfian_robot ◴[19 Nov 24 19:54 UTC] No.42187413[source]▶
a wiki is much better than google docs IMHO as the later quickly becomes an unmanageable dumpster fire. I like mediawiki a lot since most people are familiar with it from wikipedia and linking to yet-to-be-created pages encourages participation.
replies(1): >>42189217 #
2. Aachen ◴[19 Nov 24 23:33 UTC] No.42189217[source]▶
Agreed on the broad points. Personally I found simpler wiki systems to be worth it because you'll spend less time making stuff work and less time debugging because it's less complex. MediaWiki, at least from my experience with -pedia, the OpenStreetMap wiki, and others, is that it's complex and slows down to a crawl for hours~days if you bust the cache by making a change to a central template. DokuWiki runs smooth without needing to concern oneself with caches at all—but, of course, is less versatile if you have a 10'000-people organisation and need advanced features for managing all the information (we don't; it works great for us). I'm sure there are also other great options besides DokuWiki, especially if they use a markup language everyone already knows like Markdown instead of some custom syntax only used on your wiki. Another consideration: GitLab, Gitea, and friends iirc all didn't have page locking when I looked at those options ~2 years ago, so you overwrite each other's changes without noticing. Anyway, just some thoughts on implementation details. Wikis are definitely the way to go as compared to a set of documents on a drive!