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

Hacker News Discussion ↗

Remote-first startups are experimenting with a wide mix of tools and norms—Slack or Zulip for chat, wikis and docs for long‑term knowledge, and periodic video calls or virtual “office” spaces—to replace the coordination and social cues of a physical office. Many emphasize asynchronous, written communication that’s public-by-default and easily searchable, while still carving out time for focused sync sessions, pair programming, and occasional in‑person retreats. A recurring theme is that there’s no one-size-fits-all recipe: teams must balance documentation vs. chat, social contact vs. meeting fatigue, and openness vs. psychological safety based on their size, culture, and time zones.

Communication Channels & Tools

  • Heavy use of chat tools (Slack, Discord, Zulip, Teams, WhatsApp) plus video (Meet/Zoom/etc.) is common.
  • Strong split on email: some see it as the right place for “important” info; others avoid it entirely and prefer public chat channels.
  • Many advocate “public-by-default” channels for team/project topics to improve transparency, searchability, onboarding, and reduce repeated Q&A; others warn about noise and stress.
  • Opinions diverge on specific tools:
    • Zulip praised for topic-based threads and “evergreen” async discussion.
    • Slack seen as both an effective “internal Stack Overflow” and an ephemeral, FOMO-inducing “everything box.”
    • Teams is widely criticized for clumsy channel/chat concepts.

Async vs Sync & Meeting Practices

  • Strong push toward async-first communication: fewer required meetings, clear agendas, and documented outcomes.
  • Others argue synchronous calls (audio or video) are vital to avoid slow back-and-forth, miscoordination, and transactional feel.
  • Suggested patterns: weekly all‑hands, 2–3 dailies per week or technical huddles, office hours, ad‑hoc calls for complex issues.
  • “At least one video call a day” is seen by some as essential for connection and by others as excessive and draining.

Documentation & Knowledge Retention

  • Repeated emphasis on wikis/handbooks (Confluence, Notion, MediaWiki, DokuWiki, Discourse) as the real “source of truth.”
  • Recommended: design docs, RFCs, decision logs, good READMEs, code review notes, and linking chat discussions back into docs.
  • Concern that too much happens only in Slack/DMs/meetings, making context hard to find; some route nearly all discussion into forums/docs instead of chat.
  • Recording and transcribing meetings, then AI summarizing, is viewed as helpful by some; others distrust summarization accuracy.

Culture, Socialization & Psychological Safety

  • Remote work often feels transactional; many propose coffee chats, “watercooler” channels, Donut-style random 1:1s, and light humor to build rapport.
  • Virtual offices (Gather.town, Roam, Katmai, etc.) split opinion: some find them great for organic drop‑ins; others see them as infantilizing or surveillance‑like.
  • Debate over discouraging DMs: proponents cite transparency and shared knowledge; critics note it can intimidate quieter people and suppress questions.
  • Psychological safety is repeatedly cited: mockery or harsh leadership in public channels quickly kills open communication.

In‑Person Time & Cadence

  • Many recommend periodic in‑person offsites (from annually to quarterly) for trust‑building; others warn frequent travel conflicts with why people chose remote.
  • Broad agreement that at least occasional face‑to‑face time significantly improves collaboration, empathy, and long‑term culture.