Remote work doesn’t “ruin culture.” Undisciplined communication does. If your team’s memory lives in Slack threads and meeting recordings, you don’t have culture — you have amnesia.
Make Writing the Default, Not Meetings
Real-time chat is great for urgency and terrible for clarity. Deep work dies in a calendar full of “quick syncs.” Treat synchronous time as a scarce resource: use it to resolve conflict, unblock ambiguity, or build trust — not to broadcast information.
Set a simple hierarchy and enforce it: decisions and rationale live in a doc; status lives in your tracker (Linear/Jira); lightweight coordination happens in Slack; meetings are for the few topics that truly benefit from live debate.
A hard rule that fixes a surprising amount: if the decision isn’t written down in the agreed home for decisions, it’s not a decision. You can’t build a distributed team on vibes and screenshots.
Docs Are a Production System
Most teams treat documentation like chores. That’s backwards. In a distributed org, documentation is operating infrastructure — the thing that lets new people ship, incidents get resolved fast, and architecture evolve without folklore.
At minimum, keep four doc types current:
Architectural decision records (ADRs) so the “why” survives team changes.
Runbooks so on-call isn’t a hero sport.
Onboarding guides so new hires don’t need a personal tour guide.
Living API docs so consumers don’t reverse-engineer behavior from source and guesswork.
Make docs part of the definition of done. If a project changes behavior, it changes documentation. If an incident teaches you something, it produces a runbook update.
| Tool | Category | Cost | Best for |
|---|---|---|---|
| Linear | Issue Tracking | Paid plans | Fast workflows, opinionated UX |
| Notion | Documentation | Paid plans | Docs + wiki in one place |
Manage Outcomes. Stop Policing Activity.
Remote work exposes bad management fast. If you need constant visibility into “who’s online” to feel in control, your system is built on supervision instead of outcomes.
Use OKRs or a similar method to define what success looks like in the real world: shipped behavior, reliability, customer impact, risk reduced. Then keep weekly check-ins brutally practical: what moved, what’s next, what’s blocked, and what decision needs to be made.
Rituals Aren’t Fluff — They’re the Glue
Culture doesn’t come from a mission statement. It comes from repeated behaviors people can predict. Schedule 1:1s that are about the human, not a disguised status meeting. If your 1:1 agenda is only tasks, you’re missing the point.
Rituals worth keeping for engineering teams:
Weekly show-and-tell to make progress visible across time zones.
Monthly tech talks to spread context without a meeting cascade.
Hack weeks to create room for experiments and cross-team work.
And yes, get people in the same room sometimes. Not to “collaborate better” — you can collaborate fine over text. Do it to compress trust-building: shared meals, longer conversations, the stuff video calls rarely produce.
Next action: open your team’s last big decision. Can a new hire find the rationale in under five minutes without asking anyone? If not, you don’t have an async problem — you have a memory problem.
