None of the organizations I work with have a head office. The Canadian Philosophical Association is a bilingual society whose board, committees, and members are scattered from coast to coast. IREAD runs early childhood education programs across 19 partner schools in Uganda and northern Pakistan. IxDA, from earlier in my career, is a global interaction design community spread across 60+ countries. There’s no boardroom to walk down the hall to for any of them — every committee meeting, board meeting, annual meeting, and large event has to be coordinated into existence from scratch, across time zones, languages, and (for IREAD) very different levels of connectivity.

The Problem

Coordinating a distributed organization isn’t the same problem as running a remote team inside a company. There’s no shared calendar culture, no default meeting cadence, no office norms to fall back on. Board meetings for CPA need to run bilingually, coast to coast, with no physical head office to anchor them. IREAD’s Community Management Committees, accountable for 19 schools, are coordinating from a context with a different baseline of connectivity and English fluency than the Canada-based board they report into. IxDA’s local leadership spans dozens of countries.

The Approach

The throughline across all three is the same: meetings, governance, and events for organizations like this don’t happen by default — they have to be built and rebuilt every time. That means owning the full mechanics of coordination: scheduling across time zones and calendar systems that don’t always talk to each other, preparing bilingual materials where needed, keeping governance moving (minutes, motions, policy, recruitment) without a shared physical rhythm to anchor it, and scaling the same coordination instincts up to a large annual congress or conference when the calendar calls for it.

The Throughline

A “head office” isn’t really a place — it’s the set of defaults an organization doesn’t have to think about: what room, what time, what language, who’s in the loop. Distributed organizations don’t get those defaults for free. Building and running that infrastructure, meeting by meeting and event by event, across organizations with very different missions and geographies, is what makes their governance and community work possible at all.