Framework

How do you make remote teams actually work?

A structured framework for building high-performing remote engineering teams through async foundations, intentional sync rituals, and explicit culture design.

Remote-first is not remote-friendly.

Most teams adopt the tools without the operating system. They move from office desks to Zoom rooms, from in-person meetings to video calls, from hallway conversations to Slack threads. Same behaviors, different medium.

The result: meeting overload, context loss, timezone pain, culture drift. Teams operate in permanent fire-drill mode. Engineers in Europe wake up to decisions made overnight by the US team. Managers schedule "quick syncs" across six timezones. Documentation becomes an afterthought because "we'll just discuss it on the call."

Remote-first means designing the operating system around asynchronous work. Remote-friendly means using Zoom instead of conference rooms.

The Remote Operating System framework rebuilds team coordination from first principles. Not as an office transplanted online, but as a fundamentally different way of working that leverages what remote enables while mitigating what it costs.

Three layers.

Build the foundation first. Add sync rituals intentionally. Make culture explicit.

1

Async Foundation

Documentation, decision logs, knowledge management

The default mode of operation. Written communication, documented decisions, searchable knowledge bases. If it's not written down, it didn't happen.

2

Sync Rituals

Intentional meetings, timezone-fair scheduling

Strategic synchronous time. Not default meetings, but deliberate connection points. Scheduled with timezone fairness. Always with written pre-reads and post-summaries.

3

Culture OS

Explicit values, onboarding, team cohesion

Culture doesn't happen by accident remotely. It requires explicit design—written values, structured onboarding, intentional connection rituals that build trust across timezones.

Five principles.

The framework works because it changes defaults, not just adds tools.

  • 1

    Async by default.

    Meetings are the exception, not the rule. Before scheduling sync time, ask: could this be a document, a recorded video, a threaded discussion? Synchronous time is expensive—spend it deliberately.

  • 2

    Write it down.

    If it's not documented, it didn't happen. Decisions, context, rationale—all written, all searchable, all discoverable by future team members. Oral tradition doesn't scale across timezones.

  • 3

    Timezone equality.

    Rotate the pain, don't concentrate it. If someone has to take an early morning or late night call, distribute it fairly. Never build a system where one timezone constantly accommodates others.

  • 4

    Explicit presence.

    Status, availability, and working hours must be visible. Not surveillance—clarity. When does someone work? When are they available for sync? When should you expect a response? Make it explicit.

  • 5

    Intentional connection.

    Culture doesn't happen by accident remotely. You won't build trust in the hallway—there is no hallway. Create explicit spaces for connection: virtual coffee chats, async social channels, team retreats.

When to use this.

This works when:

  • Your team spans 3+ 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

This doesn't work when:

  • Your team 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
← Explore all frameworks

Need help building your remote OS?

I help engineering leaders transition from remote-friendly to remote-first through operating system design, async workflows, and cultural transformation.

Let's talk about your team →