How do small presses organize book projects?
- One shared workspace per book.
- Each book has a named project manager.
- Explicit role assignments: editor, designer, marketer, project manager.
- A milestone-based timeline anchors deliverables to dates.
- 3-5 staff can ship 10-20 books a year with this structure.
Small presses organize book projects with one shared workspace per book containing the manuscript, metadata, calendar, and team roster. Each book has a named project manager (or "captain"), explicit role assignments, and a milestone-based timeline. Most small presses with three to five staff manage ten to twenty books a year using this structure.
Chapter i·Why it matters
Small presses fail when projects blur into each other. Without per-book workspaces, the editor working on book three forgets which manuscript version was approved; the designer working on book seven uses old metadata. Per-book organization replaces memory with structure, which is what scales from one staff member to five.
Chapter ii·What to include
- A shared workspace per book: manuscript, metadata, calendar, team roster.
- A named project manager per book.
- Explicit role assignments and accountability.
- A milestone timeline anchored to publication date.
- A weekly press-wide review covering all in-flight books.
- A "lessons learned" doc per book, reviewed quarterly.
Chapter iii·Example
A small press with four staff and twelve books a year keeps each book in its own WriteLoom workspace. Every Friday morning, the team reviews all twelve at a 45-minute meeting. Each book’s project manager reports status against the milestone calendar. Across two years, the press hasn’t slipped a launch — and the workflow improvement notes accumulate into a steadily better operations playbook.
Chapter iv·Related questions
WriteLoom supports shared per-book workspaces for small presses — manuscript, metadata, calendar, and team roles in one project.
See WriteLoom for teams