How do distributed publishing teams work together?
- Three structures: shared single source of truth, async-first communication, weekly sync.
- Async tools: Slack, Discord, email, document comments.
- Sync tools: Zoom, Google Meet, Microsoft Teams.
- Across time zones: 80-90% of communication should be async.
- Weekly sync covers coordination, not decisions.
Distributed publishing teams work together through three structures: a shared single source of truth per book (manuscript, metadata, calendar), asynchronous communication for most decisions, and weekly synchronous meetings for coordination. Teams that span time zones lean async-first; teams in adjacent zones can balance async and sync.
Chapter i·Why it matters
Distributed teams that try to replicate in-office synchronous work overwork people in unfavorable time zones and slow down decisions. Async-first distribution lets each person work in their own time, with shared state replacing real-time conversation. The weekly sync exists for the 10-20% that genuinely needs it.
Chapter ii·What to include
- A shared single source of truth per book.
- Async-first communication norms: Slack, Discord, document comments.
- A "decisions in writing" rule: any decision worth making is worth documenting.
- A weekly synchronous meeting (30-45 minutes).
- Recorded video for context that cannot be written.
- Time-zone-aware scheduling: rotate meeting times so no one is always inconvenienced.
Chapter iii·Example
A small press with five staff across three time zones runs 90% async via Slack and WriteLoom. The weekly sync is a 30-minute Friday meeting at a rotating time. All editorial decisions live in WriteLoom comments; all marketing decisions in a Slack channel. Across two years they have shipped 24 books with zero scheduling conflicts.
WriteLoom is the shared state for distributed teams — every book’s manuscript, metadata, and calendar in one project, async-friendly by design.
See WriteLoom for teams