How do publishing teams collaborate?
- Three structures: shared source of truth, explicit role assignments, weekly sync.
- Slack or Discord for communication; shared workspaces for content.
- A weekly Friday review covers all in-flight books.
- Role clarity is the single biggest predictor of team success.
- Small presses with 3-5 staff ship 10-20 books a year using this model.
Publishing teams collaborate through three structures: a shared single source of truth (manuscript, metadata, calendar), explicit role assignments per task, and a weekly sync to resolve open questions. Most successful small-press teams use Slack or Discord for communication, a shared workspace for the manuscript and metadata, and a weekly Friday review covering all in-flight books.
Chapter i·Why it matters
Publishing teams fail more often from coordination problems than from creative ones. Two people editing the same manuscript without coordination produces version chaos. Designer and editor working without shared deadlines miss launches. A simple coordination structure — shared truth, role clarity, weekly sync — solves more problems than any tool.
Chapter ii·What to include
- A shared single source of truth for each book (manuscript, metadata, calendar).
- Explicit role assignments per task: editorial, design, metadata, distribution.
- A weekly all-hands sync covering every in-flight book.
- A communication tool: Slack, Discord, or Teams.
- A decision log: who decided what, when, and why.
- A backup/handoff protocol if a team member leaves a project.
Chapter iii·Example
A small press with four staff and ten books a year runs a 30-minute Friday meeting covering every book’s status. Each book has a named editor, designer, and project manager. The shared workspace is WriteLoom; Slack handles day-to-day questions. Across three years they have never missed a launch and the team turnover has been zero.
Chapter iv·Related questions
WriteLoom supports shared projects with role-based access, so editors, designers, and managers work on the same book without emailing files.
See WriteLoom for teams