<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Remote University</title><description>Source-backed research on the operating systems behind durable distributed companies — how they communicate, plan, decide, and structure teams.</description><link>https://remote.university/</link><language>en-us</language><managingEditor>alex@karasyov.com (Alex Karasyov)</managingEditor><atom:link href="https://remote.university/rss.xml" rel="self" type="application/rss+xml"/><item><title>How Automattic Runs a Global Distributed Company With P2 Blogs</title><link>https://remote.university/companies/automattic/</link><guid isPermaLink="true">https://remote.university/companies/automattic/</guid><description>Automattic stewards WordPress, used by 40.3% of websites in W3Techs&apos;s September 12, 2026 snapshot, and runs WordPress.com with a fully distributed team across 83 countries — written project discussions, customer support rotations, and paid trials are part of its operating model.</description><pubDate>Sat, 12 Sep 2026 00:00:00 GMT</pubDate><category>Company</category><category>company</category><category>async</category><category>communication</category><category>onboarding</category><category>rituals</category><category>scaling</category><category>culture</category></item><item><title>How Basecamp Runs a Global Remote Company Without Full-Time Managers</title><link>https://remote.university/companies/basecamp/</link><guid isPermaLink="true">https://remote.university/companies/basecamp/</guid><description>37signals built the definitive async operating system — 6-week cycles, zero full-time managers, and 98% of all communication in one tool.</description><pubDate>Sat, 12 Sep 2026 00:00:00 GMT</pubDate><category>Company</category><category>company</category><category>async</category><category>planning</category><category>communication</category><category>decision-making</category><category>onboarding</category><category>rituals</category><category>leadership</category></item><item><title>How Buffer Runs a 75-Person Remote Company With Transparent Salaries and No Office</title><link>https://remote.university/companies/buffer/</link><guid isPermaLink="true">https://remote.university/companies/buffer/</guid><description>Buffer has been fully remote since 2012 (last office closed late 2015), with around 75 teammates in its early-2026 reporting. It publishes a salary system, shares profits, combines synchronous and asynchronous work, and now documents AI-assisted Build Weeks and candidate Q&amp;A guides.</description><pubDate>Sat, 12 Sep 2026 00:00:00 GMT</pubDate><category>Company</category><category>company</category><category>communication</category><category>culture</category><category>async</category><category>leadership</category><category>execution</category></item><item><title>How Todoist Runs a Distributed Company With Async Communication and Deliberate Meetings</title><link>https://remote.university/companies/doist/</link><guid isPermaLink="true">https://remote.university/companies/doist/</guid><description>Todoist, formerly Doist, has 108 team members across 38 countries. Its async-first model combines written communication, DO planning squads, a public handbook and deliberate recurring meetings.</description><pubDate>Sat, 12 Sep 2026 00:00:00 GMT</pubDate><category>Company</category><category>company</category><category>async</category><category>communication</category><category>planning</category><category>culture</category><category>rituals</category></item><item><title>How GitHub Preserved Async Engineering Practices Through Microsoft Ownership</title><link>https://remote.university/companies/github/</link><guid isPermaLink="true">https://remote.university/companies/github/</guid><description>GitHub&apos;s early culture emphasized autonomy and written collaboration. Its 2023 engineering guidance retained async communication after Microsoft&apos;s 2018 acquisition; the 2025 CEO departure and CoreAI transition show why organizational structure and working practices need separate evidence.</description><pubDate>Sat, 12 Sep 2026 00:00:00 GMT</pubDate><category>Company</category><category>company</category><category>async</category><category>communication</category><category>tooling</category><category>culture</category><category>scaling</category></item><item><title>How GitLab Coordinates an All-Remote Company With a Multi-Thousand-Page Handbook</title><link>https://remote.university/companies/gitlab/</link><guid isPermaLink="true">https://remote.university/companies/gitlab/</guid><description>GitLab reported approximately 2,580 team members in 60 countries as of January 31, 2026. Its public handbook supports an all-remote company through written context, named decision owners, and deliberate choices between async and synchronous work.</description><pubDate>Sat, 12 Sep 2026 00:00:00 GMT</pubDate><category>Company</category><category>company</category><category>async</category><category>communication</category><category>documentation</category><category>onboarding</category><category>scaling</category><category>execution</category></item><item><title>How Linear Combines a Published Method With Continuous Planning and Small Project Teams</title><link>https://remote.university/companies/linear/</link><guid isPermaLink="true">https://remote.university/companies/linear/</guid><description>Linear publishes its software-building principles and describes continuous planning, small project teams and remote-work rituals. Its August 2026 update reports $100M ARR passed and an employee tender at a $2.5B valuation.</description><pubDate>Sat, 12 Sep 2026 00:00:00 GMT</pubDate><category>Company</category><category>company</category><category>handbook</category><category>planning</category><category>culture</category><category>product</category><category>hiring</category></item><item><title>How Shopify Combines Digital by Design, Meeting Resets, and Shared AI Workflows</title><link>https://remote.university/companies/shopify/</link><guid isPermaLink="true">https://remote.university/companies/shopify/</guid><description>Shopify&apos;s operating record spans its May 2020 remote shift, a 2023 reset of 12,000 calendar series and events, and documented shared AI workflows in 2026. Its current Digital by Design guidance combines optional offices with planned in-person gatherings.</description><pubDate>Sat, 12 Sep 2026 00:00:00 GMT</pubDate><category>Company</category><category>company</category><category>communication</category><category>leadership</category><category>scaling</category><category>culture</category><category>rituals</category></item><item><title>How Stephen Wolfram Leads a Distributed Software Company Through Audio and Livestreamed Design Reviews</title><link>https://remote.university/companies/wolfram/</link><guid isPermaLink="true">https://remote.university/companies/wolfram/</guid><description>Stephen Wolfram has been a remote CEO since 1991 and favors audio with screen sharing. The privately held company reports over 700 employees; its public Live CEOing archive lists 991 videos as of September 12, 2026.</description><pubDate>Sat, 12 Sep 2026 00:00:00 GMT</pubDate><category>Company</category><category>company</category><category>communication</category><category>culture</category><category>leadership</category><category>execution</category><category>founder-mode</category></item><item><title>How Zapier Scales Fully Remote With Public Work and AI Capability Building</title><link>https://remote.university/companies/zapier/</link><guid isPermaLink="true">https://remote.university/companies/zapier/</guid><description>Zapier reports 800+ people across 38 countries and has worked remotely since 2011. Its published operating accounts emphasize action, transparency, contextual async communication, and an AI program that now extends into hiring, onboarding and performance expectations.</description><pubDate>Sat, 12 Sep 2026 00:00:00 GMT</pubDate><category>Company</category><category>company</category><category>async</category><category>communication</category><category>decision-making</category><category>scaling</category><category>execution</category><category>planning</category></item><item><title>Async Communication: How Distributed Companies Replace Real-Time Dependency</title><link>https://remote.university/practices/async-communication/</link><guid isPermaLink="true">https://remote.university/practices/async-communication/</guid><description>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.</description><pubDate>Sat, 12 Sep 2026 00:00:00 GMT</pubDate><category>Practice</category><category>async</category><category>communication</category><category>practice</category></item><item><title>Cross-Time-Zone Collaboration: How Distributed Companies Work Across the Clock</title><link>https://remote.university/practices/cross-time-zone-collaboration/</link><guid isPermaLink="true">https://remote.university/practices/cross-time-zone-collaboration/</guid><description>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 &apos;overlap hours&apos; as the primary mechanism and built async-first systems with intentional synchronous touchpoints.</description><pubDate>Sat, 12 Sep 2026 00:00:00 GMT</pubDate><category>Practice</category><category>async</category><category>communication</category><category>practice</category><category>culture</category></item><item><title>Decision Ownership: How Distributed Companies Assign Authority Without Hierarchy</title><link>https://remote.university/practices/decision-ownership/</link><guid isPermaLink="true">https://remote.university/practices/decision-ownership/</guid><description>Decision ownership makes authority and accountability explicit for a project or decision. GitLab&apos;s formal DRI model, 37signals&apos; emphasis on self-direction and Shopify&apos;s human authority in an AI workflow offer distinct examples; they do not establish one universal model for distributed companies.</description><pubDate>Sat, 12 Sep 2026 00:00:00 GMT</pubDate><category>Practice</category><category>decision-making</category><category>leadership</category><category>execution</category><category>practice</category></item><item><title>Documentation Systems: How Distributed Companies Build Institutional Memory</title><link>https://remote.university/practices/documentation-systems/</link><guid isPermaLink="true">https://remote.university/practices/documentation-systems/</guid><description>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.</description><pubDate>Sat, 12 Sep 2026 00:00:00 GMT</pubDate><category>Practice</category><category>documentation</category><category>async</category><category>communication</category><category>practice</category><category>scaling</category></item><item><title>Planning Cycles: How Fixed Cadences Replace Perpetual Roadmap Chaos</title><link>https://remote.university/practices/planning-cycles/</link><guid isPermaLink="true">https://remote.university/practices/planning-cycles/</guid><description>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.</description><pubDate>Sat, 12 Sep 2026 00:00:00 GMT</pubDate><category>Practice</category><category>planning</category><category>execution</category><category>practice</category><category>async</category></item><item><title>Remote Onboarding: How Distributed Companies Ramp New Hires Without an Office</title><link>https://remote.university/practices/remote-onboarding/</link><guid isPermaLink="true">https://remote.university/practices/remote-onboarding/</guid><description>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.</description><pubDate>Sat, 12 Sep 2026 00:00:00 GMT</pubDate><category>Practice</category><category>onboarding</category><category>culture</category><category>practice</category><category>remote</category></item><item><title>Retreats: How Distributed Companies Build Culture Without an Office</title><link>https://remote.university/practices/retreats/</link><guid isPermaLink="true">https://remote.university/practices/retreats/</guid><description>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.</description><pubDate>Sat, 12 Sep 2026 00:00:00 GMT</pubDate><category>Practice</category><category>rituals</category><category>culture</category><category>practice</category><category>async</category></item><item><title>Written-First Culture: Why the Best Distributed Companies Default to Writing</title><link>https://remote.university/practices/written-first-culture/</link><guid isPermaLink="true">https://remote.university/practices/written-first-culture/</guid><description>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.</description><pubDate>Sat, 12 Sep 2026 00:00:00 GMT</pubDate><category>Practice</category><category>communication</category><category>documentation</category><category>async</category><category>practice</category><category>culture</category></item><item><title>The 20-30 Person Fracture Point</title><link>https://remote.university/frameworks/20-30-person-fracture-point/</link><guid isPermaLink="true">https://remote.university/frameworks/20-30-person-fracture-point/</guid><description>A working hypothesis and diagnostic guide for growing distributed teams. Uses documented company practices to suggest what to inspect as coordination becomes harder, while separating those examples from unverified claims about headcount thresholds and founder histories.</description><pubDate>Sat, 12 Sep 2026 00:00:00 GMT</pubDate><category>Framework</category><category>framework</category><category>scaling</category><category>leadership</category><category>planning</category><category>communication</category><category>decision-making</category></item><item><title>Scrum in Distributed Companies: What Survives, What Breaks, What to Adapt</title><link>https://remote.university/frameworks/scrum-in-distributed-companies/</link><guid isPermaLink="true">https://remote.university/frameworks/scrum-in-distributed-companies/</guid><description>A source-backed comparison of Scrum and distributed operating practices. Distinguishes the official Scrum Guide from proposed adaptations, corrects Sprint timeboxes, and bounds what company examples can establish about cadence, retrospectives and scaling.</description><pubDate>Sat, 12 Sep 2026 00:00:00 GMT</pubDate><category>Framework</category><category>framework</category><category>scrum</category><category>agile</category><category>planning</category><category>async</category><category>methodology</category></item><item><title>Sync vs Async Decision Matrix</title><link>https://remote.university/frameworks/sync-vs-async-decision-matrix/</link><guid isPermaLink="true">https://remote.university/frameworks/sync-vs-async-decision-matrix/</guid><description>A practical decision matrix for choosing between synchronous and asynchronous communication — built from the operating practices of 37signals, GitLab, Todoist, Buffer, and Automattic. Includes symptom checklist, situation-by-situation guidance, and a framework for setting team-level communication norms.</description><pubDate>Sat, 12 Sep 2026 00:00:00 GMT</pubDate><category>Framework</category><category>framework</category><category>async</category><category>communication</category><category>decision-making</category><category>planning</category></item></channel></rss>