Source-backed research on the operating systems behind durable distributed companies — how they communicate, plan, decide, and structure teams.https://remote.university/en-usAlex Karasyovhttps://remote.university/companies/automattic/https://remote.university/companies/automattic/Automattic stewards WordPress, the CMS behind ~42% of all websites, and runs WordPress.com with a fully distributed team across 81 countries — P2 blogs replace email, everyone does customer support, and new hires trial before they're hired.Tue, 05 May 2026 00:00:00 GMTCompanycompanyasynccommunicationonboardingritualsscalingculturehttps://remote.university/companies/basecamp/https://remote.university/companies/basecamp/37signals built the definitive async operating system — 6-week cycles, zero full-time managers, and 98% of all communication in one tool.Tue, 05 May 2026 00:00:00 GMTCompanycompanyasyncplanningcommunicationdecision-makingonboardingritualsleadershiphttps://remote.university/companies/buffer/https://remote.university/companies/buffer/Buffer has been fully remote since 2012 (last office closed late 2015) with 75 teammates across multiple continents, publishes all salaries on a public formula, runs profit share for the whole team, and explicitly documents that remote does not mean async-first.Tue, 05 May 2026 00:00:00 GMTCompanycompanycommunicationcultureasyncleadershipexecutionhttps://remote.university/companies/doist/https://remote.university/companies/doist/Doist builds Todoist and Twist with ~93 employees across 39 countries, no VC funding, no meetings by default, and Slack deliberately excluded — the most extreme async-first operating system in use at a real software company.Tue, 05 May 2026 00:00:00 GMTCompanycompanyasynccommunicationplanningcultureritualshttps://remote.university/companies/gitlab/https://remote.university/companies/gitlab/GitLab has 2,500+ team members across 65+ countries with no offices and a public handbook that runs well over 2,000 pages — radical documentation, async-first communication, and results over activity.Tue, 05 May 2026 00:00:00 GMTCompanycompanyasynccommunicationdocumentationonboardingscalingexecutionhttps://remote.university/companies/wolfram/https://remote.university/companies/wolfram/Wolfram Research has been distributed since the early 1990s with Stephen Wolfram as a remote CEO since 1991 — one of the longest-running distributed-CEO cases in software, running ~700 people across 29+ countries on audio-only meetings, livestreamed design reviews (975+ episodes), and no outside money.Tue, 05 May 2026 00:00:00 GMTCompanycompanycommunicationcultureleadershipexecutionfounder-modehttps://remote.university/companies/zapier/https://remote.university/companies/zapier/Zapier has been fully remote since 2011 and scaled to 800+ employees without a single office on two rules — default to action, default to transparency — plus a DRI system, single-page specs, and customer-centered annual summits.Tue, 05 May 2026 00:00:00 GMTCompanycompanyasynccommunicationdecision-makingscalingexecutionplanninghttps://remote.university/practices/async-communication/https://remote.university/practices/async-communication/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.Tue, 05 May 2026 00:00:00 GMTPracticeasynccommunicationpracticehttps://remote.university/practices/cross-time-zone-collaboration/https://remote.university/practices/cross-time-zone-collaboration/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.Tue, 05 May 2026 00:00:00 GMTPracticeasynccommunicationpracticeculturehttps://remote.university/practices/decision-ownership/https://remote.university/practices/decision-ownership/Decision ownership is the practice of assigning a single accountable person — not a committee, not a team — to every significant decision or project. The companies that operate well at remote scale all use some version of it, because distributed work makes diffuse ownership invisible until it becomes catastrophic.Tue, 05 May 2026 00:00:00 GMTPracticedecision-makingleadershipexecutionpracticehttps://remote.university/practices/documentation-systems/https://remote.university/practices/documentation-systems/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.Tue, 05 May 2026 00:00:00 GMTPracticedocumentationasynccommunicationpracticescalinghttps://remote.university/practices/planning-cycles/https://remote.university/practices/planning-cycles/Planning cycles are fixed, repeating periods of committed work followed by deliberate pauses for reflection and replanning. Companies that use them replace the endless roadmap backlog with a small number of explicit bets made at regular intervals — forcing real prioritization instead of perpetual refinement.Tue, 05 May 2026 00:00:00 GMTPracticeplanningexecutionpracticeasynchttps://remote.university/practices/remote-onboarding/https://remote.university/practices/remote-onboarding/Remote onboarding is the structured process of integrating new employees into a distributed company without in-person orientation. The companies that do it well share a common pattern: clear structured expectations from day one, multiple designated support contacts, real work beginning in week one, and a 90-day ramp — not 2 weeks.Tue, 05 May 2026 00:00:00 GMTPracticeonboardingculturepracticeremotehttps://remote.university/practices/retreats/https://remote.university/practices/retreats/Retreats are the primary mechanism by which fully distributed companies build the in-person relationships that sustain remote culture. The companies that do them well share a design principle: retreats are not about replicating office productivity in a hotel conference room. They are about creating the human connections that async work cannot.Tue, 05 May 2026 00:00:00 GMTPracticeritualsculturepracticeasynchttps://remote.university/practices/written-first-culture/https://remote.university/practices/written-first-culture/Written-first culture is the practice of defaulting to written communication for decisions, discussions, and direction — not because it is convenient, but because writing forces clarity, creates permanence, and scales across time zones and headcount in ways that verbal communication cannot.Tue, 05 May 2026 00:00:00 GMTPracticecommunicationdocumentationasyncpracticeculturehttps://remote.university/frameworks/20-30-person-fracture-point/https://remote.university/frameworks/20-30-person-fracture-point/Companies that scaled distributed work successfully — at least in this dataset — built explicit operating infrastructure before reaching 20–30 people. Companies that struggled at that scale hit a recurring set of failure modes: invisible ownership, fragmented communication, lost institutional knowledge, cultural drift. This framework states the pattern as a working hypothesis and lays out what to build before you hit it.Tue, 05 May 2026 00:00:00 GMTFrameworkframeworkscalingleadershipplanningcommunicationdecision-makinghttps://remote.university/frameworks/scrum-in-distributed-companies/https://remote.university/frameworks/scrum-in-distributed-companies/A source-backed audit of which Scrum elements strengthen distributed execution, which conflict with it, and how distributed-native companies (GitLab, 37signals, Linear, Doist) achieve Scrum's intended outcomes through adapted mechanisms. Triangulates the Scrum Guide 2020, Scrum.org and Scrum Alliance distributed guidance, the Scrum@Scale Guide, LeSS principles, and peer-reviewed empirical research.Tue, 05 May 2026 00:00:00 GMTFrameworkframeworkscrumagileplanningasyncmethodologyhttps://remote.university/frameworks/sync-vs-async-decision-matrix/https://remote.university/frameworks/sync-vs-async-decision-matrix/A practical decision matrix for choosing between synchronous and asynchronous communication — built from the operating practices of 37signals, GitLab, Doist, Buffer, and Zapier. Includes symptom checklist, situation-by-situation guidance, and a framework for setting team-level communication norms.Tue, 05 May 2026 00:00:00 GMTFrameworkframeworkasynccommunicationdecision-makingplanninghttps://remote.university/companies/github/https://remote.university/companies/github/GitHub built developer culture around 'optimize for happiness,' no managers, no meetings, and pull-request-as-artifact — and ran for 12 years that way before being acquired by Microsoft. The PR survived. The manifesto mostly didn't.Fri, 01 May 2026 00:00:00 GMTCompanycompanyasynccommunicationtoolingculturescalinghttps://remote.university/companies/linear/https://remote.university/companies/linear/Linear is the rare small distributed company that publishes its operating handbook — the Linear Method — and runs the entire product on it. Cycles, taste-as-hiring-filter, quality-as-binary, and async-first by default at exactly the scale most readers actually operate at.Fri, 01 May 2026 00:00:00 GMTCompanycompanyhandbookplanningcultureproducthiringhttps://remote.university/companies/shopify/https://remote.university/companies/shopify/Shopify pivoted to digital-by-default in May 2020 and held it through the post-COVID RTO wave. In January 2023 they cancelled every recurring meeting >2 attendees, eliminated ~76,500 hours of meeting time, and built an internal calendar tool that surfaces the dollar cost of meetings. The most public post-RTO operating-model case study in software.Fri, 01 May 2026 00:00:00 GMTCompanycompanycommunicationleadershipscalingculturerituals