How we think about remote work
Messaging
Slack is the primary operating system for messaging. If information should be retained, we move it to Notion.
We use channel prefixes so urgency and purpose are visible at a glance:
- bot-, alert-, cust-, int-, collab-
- proj-, all-, team-, review-, club-, inc-
If unsure where to post, default to #all-discussions.
When to thread, post, or DM
Threading
Good for focused topics and parallel conversations in one channel; weaker for fast responses and broad visibility.
Posting in channels
Good for informing everyone in that channel and starting broader discussion.
DMing
Good for direct collaboration and private conversations; weaker for discoverability.
Tasks
Linear is the task system. If you need another team to do work, create a Linear issue and avoid delegating non-immediate tasks only in Slack.
Perfect tickets are short in title, rich in details, include edge cases, can be split into sub-issues, and include severity.
Working hours
The team overlap window is generally 14:00–18:00 UTC for synchronous collaboration.
We do not expect routine evening or weekend work, except edge cases like launches or incidents. If extra hours become habitual, escalate with your manager.
Meetings
- Try async first; if it fails, schedule a meeting.
- For demos, prefer recorded videos in Slack.
- For pairing, prefer Slack Huddles.
- Default meetings to camera on; Huddles camera off.
- Cancel recurring meetings if value drops.
Handoffs
Strong handoffs reduce blockers and speed up validation. RFCs are central: they collect feedback early, reveal roadblocks, and reduce scope creep before implementation.
Good tickets and good RFCs are how a small remote team maintains shared context.