Specific, implementable operating practices extracted from the companies that have made distributed execution work at scale — not theory, operator-grade evidence. Each one covers what it is, why it works, where it fails, and what founders can actually copy.
Async communication is the practice of exchanging information without requiring simultaneous attention. It is not a tool choice — it is a design philosophy that reshapes how work is structured, how decisions are made, and how accountability is maintained across distributed teams.
Cross-time-zone collaboration is the set of practices that allow distributed teams to coordinate effectively when team members are 6, 10, or 16 hours apart. Companies that do it well have moved beyond 'overlap hours' as the primary mechanism and built async-first systems with intentional synchronous touchpoints.
Written-first culture uses written proposals and records as a starting point for coordination. These cases show how writing coexists with live discussion; their policies do not establish a universal improvement in decision quality.
Decision ownership makes authority and accountability explicit for a project or decision. GitLab's formal DRI model, 37signals' emphasis on self-direction and Shopify's human authority in an AI workflow offer distinct examples; they do not establish one universal model for distributed companies.
Documentation systems are the infrastructure that allows distributed companies to store, find, and act on institutional knowledge without relying on meetings, memory, or co-location. The companies that do this well treat documentation as a first-class organizational practice — not an overhead activity.
Compare 37signals’ fixed build cycles and cooldowns, GitLab’s nested planning horizons, and Linear’s continuous preparation of candidate projects. The cases show different ways to select work and revisit commitments; they do not establish one mandatory cadence or a measured reduction in coordination costs.
Remote onboarding is the structured process of integrating new employees into a distributed company without in-person orientation. The examples combine documented expectations, named support contacts, early participation and staged onboarding; the duration of the ramp varies by role and company.
Retreats are one way distributed companies invest in relationships and shared context. The examples use different combinations of company gatherings, team meetups and informal contact; their agendas and travel expectations should be read as company choices rather than universal requirements.
