COMPANY PLAYBOOK
Oyster
Oyster designs global distributed work around handoffs, documentation and asynchronous participation so time zones become an advantage rather than a barrier.
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
01
Meetings
No meeting when async will work
Synchronous time is avoided when the same outcome can be achieved asynchronously in time.
- How it works
- Before booking, the team tests the need for discussion, immediacy, attendance and focus interruption.
- Why it is used
- Preserves live time for relationships and genuinely synchronous creation.
- Trade-off
- The wrong async channel can stretch a small ambiguity across days.
- Best fit
- Multi-time-zone teams with disciplined written decisions.
02
Remote
Follow-the-sun handoff
A team ending its day hands work, context and the next action to a time zone starting its day.
- How it works
- A handoff note carries status, decisions, blockers and an explicit next action.
- Why it is used
- Reduces dependence on the working hours of one time zone.
- Trade-off
- Weak handoffs produce rework and unclear ownership.
- Best fit
- Complementary global operations and project teams.
03
Performance
Outcome-led distributed work
Work is organized around explicit outcomes, processes and documentation rather than visible online time.
- How it works
- Expected outputs and handoff points are written while people organize days in their own time zones.
- Why it is used
- Connects global flexibility with performance visibility.
- Trade-off
- Focusing only on measurable outputs can hide maintenance and relational work.
- Best fit
- Teams with explicit outcomes and written coordination.