Distributed Teams — Start Here
John O'Duinn argues that distributed work succeeds or fails based on deliberate engineering-style design, not improvisation: documentation practices, communication infrastructure, and process design have to be built on purpose for a team that isn't co-located, the same way a technical system is architected rather than assembled by accident. His core claim is that treating distribution as a designed system, not a workaround for an office that doesn't exist, is what separates distributed teams that thrive from those that just barely function.
The whole book, in one line
John O'Duinn argues that distributed work succeeds or fails based on deliberate engineering-style design, not improvisation: documentation practices, communication infrastructure, and process design have to be built on purpose for a team that isn't co-located, the same way a technical system is architected rather than assembled by accident. His core claim is that treating distribution as a designed system, not a workaround for an office that doesn't exist, is what separates distributed teams that thrive from those that just barely function.
How the mechanism works
- Designing communication infrastructure and documentation practices deliberately, rather than letting them emerge by accident.
- Structuring meetings and collaboration around time-zone and asynchronous realities instead of assuming everyone is available at once.
- Building hiring, onboarding, and career-development processes that work without shared physical space.
- Measuring output and productivity fairly across a distributed team, without defaulting to visibility or hours as the proxy for contribution.
Who this was written for
A team lead or operations-minded professional who has been improvising their distributed team's processes and wants a more systematic, designed approach to documentation, meetings, and fairness.
ACT tier. John O'Duinn is a living author and consultant on distributed work with an active consulting practice. Safeguards for every persona edition: the author's real consulting business and any named client company must be excluded entirely; no real case studies reproduced from the book; no fabricated statistics; keep the systems-design framing general and process-focused rather than naming any specific tool or vendor as an endorsement.
Cross-book note
This is the systems/engineering-process-design title in the category, treating distribution as a deliberately architected practice. Distinct from Remote: Office Not Required (a broader philosophy/manifesto), The Year Without Pants (a single company's real story), Running Remote (scaling an entire company remote-first, more hiring/culture-at-scale focused), and Work Together Anywhere (a lighter, more tactical field guide of rituals and tools). Needs a cross-category check against New Manager and Team Leadership Skills and Job Search and Interview Skills.