A remote operating system.
The rituals, defaults, and written contracts that make distributed engineering boring, in the best sense. Eight weeks.
If it isn't written down, it didn't happen.
Remote-first, not remote-friendly.
Most teams adopt the tools without the operating system. Same behaviours, different medium.
Move from desks to Zoom rooms, from in-person to video calls, from hallway conversations to Slack. The result: meeting overload, context loss, timezone pain, culture drift. Permanent fire-drill mode.
Remote-first means designing the operating system around asynchronous work. Remote-friendly means using Zoom instead of conference rooms.
If it isn't written down, it didn't happen.
Foundation, rituals, culture.
Build the foundation first. Add sync rituals intentionally. Make culture explicit.
Async foundation
Documentation · decision logs · knowledge management
The default mode of operation. Written communication, documented decisions, searchable knowledge bases. The system everyone reads before they ask.
Sync rituals
Intentional meetings · timezone-fair scheduling
Strategic synchronous time. Not default meetings, deliberate connection points. Scheduled with timezone fairness. Pre-reads in, summaries out.
Culture OS
Explicit values · structured onboarding · team cohesion
Culture doesn't happen by accident remotely. Written values, structured onboarding, intentional connection rituals that build trust across timezones.
Defaults, not tools.
The framework works because it changes defaults, not because it adds tools.
Async by default
Meetings are the exception. Before scheduling sync, ask: could this be a document, a recorded video, a threaded discussion? Sync time is expensive, spend it deliberately.
Write it down
Decisions, context, rationale: all written, all searchable, all discoverable by future team members. Oral tradition doesn't scale across timezones.
Timezone equality
Rotate the pain, don't concentrate it. Distribute the cost of unavoidable sync time fairly. Never let one timezone constantly accommodate the others.
Explicit presence
Status, availability, and working hours are visible. Not surveillance, clarity. When does someone work? When are they available? When should you expect a response?
Useful for, and not.
Async-first isn't always the answer. Be honest about whether your work needs real-time.
Use it when
- Your team spans three or more timezones.
- You're scaling from co-located to distributed.
- Meeting overload is killing productivity.
- Context is being lost between team members.
- You're willing to change process, not just add tools.
Don't use it when
- Your work requires real-time collaboration (trading desks, emergency services).
- Everyone is in the same timezone and co-location is viable.
- Leadership wants "office culture" remotely.
- You're unwilling to document decisions.
- You need immediate answers to everything.
Quiet distributed engineering is possible.
If timezones are taxing your team, the answer is rarely another tool.