RESEARCH ANSWER

Remote is an operating system, not a location policy.

GitLab reduces time-zone dependency through handbook-first processes, Automattic through P2-based written communication, and Elastic through flexible time and intentional distributed design.

Questions

How do remote-first companies operate?

How are decisions made across time zones?

How do distributed teams build social connection?

CROSS-COMPANY SYNTHESIS

Evidence-linked practices

Remote

Separate permanent and transient knowledge

Permanent methods live in Notion while discussions and updates for active work live in Linear.

The Remote Flow

Supabase

Asynchronous flexible work

The team works fully remotely and asynchronously, and people choose where they work.

Supabase Careers

GitLab

Handbook-first work

A living handbook is used as the single source of truth for processes and decisions.

GitLab Handbook

Automattic

Written work through P2

Project context and decisions are made durable in internal blogs.

How We Work

Elastic

Home, Dinner

The workday can flex around personal life and care responsibilities.

Source Code

Mattermost

Preserve retired terms with tombstones

Changed or deprecated terms are retained as tombstones to preserve the meaning of old links.

List of terms

Sparksuite

Variable start and finish times

Full-time team members may start between 7:00 and 10:00, complete eight hours, and change the choice day by day.

Flexible working hours

Hardal

Async-first communication

The distributed team uses a working principle that prioritizes asynchronous communication through writing, Slack and Linear.

How We Work at Hardal