How They Do ItBETA

COMPANY PLAYBOOK

Oyster

Oyster designs global distributed work around handoffs, documentation and asynchronous participation so time zones become an advantage rather than a barrier.
Operating system
  1. Written context
  2. asynchronous contribution
  3. cross-time-zone handoff
  4. only necessary sync
  5. documented decision.

System principles

  • Avoid a meeting when async can produce the same outcome.
  • Hand work to the next time zone at day end.
  • Evaluate contribution through outcomes rather than visible hours.

Tensions and trade-offs

  • Async work protects focus but can create decision latency and isolation.
  • Follow-the-sun creates continuity but magnifies context loss when handoffs are weak.

PRACTICES

How Oyster builds its operating system

Primary sources

The ReefHow We Do MeetingsIntroducing The Reef