How They Do ItBETA
TREN

Collaboration · 4 COMPANIES

Async work is an operating system, not a communication preference

How do remote-first companies reduce meetings without sacrificing decision quality?
Short answer

Strong models do more than hold fewer meetings: they create information in writing first, maintain a durable record and reserve synchronous time for ambiguity and relationships.

Shared patterns

  1. 01

    Durable knowledge lives in searchable surfaces such as a handbook, P2 or Async rather than chat.

  2. 02

    Urgent communication and normal coordination use different channels.

  3. 03

    Success is evaluated through outcomes rather than online visibility.

Important differences

GitLab uses a handbook, Automattic P2, Zapier channel separation and Elastic flexible time and trust.

Trade-off

Written work creates equal access but can increase reading load, decision latency and social distance.

Put it into practice

First classify information as durable, rapid or urgent, then assign one default channel to each class.