The best workflow we run today didn't come from a textbook. It came from a mistake — a small one, the kind that's easy to miss until it's sitting in a printer's proof. We fixed it, then we asked the more useful question: how do we make sure this specific thing never happens again, on this project or the next hundred? The answer usually isn't a rule someone remembers. It's a checklist someone runs.
That distinction matters more than it sounds like it should. Memory works fine on a single book. It breaks down at any real scale — a dozen publishing houses, hundreds of titles, seasonal peaks where an editorial and design team is reviewing pass proofs on several books at once. At that volume, ‘someone will remember to check’ is not a system. It's a hope.
So learning becomes a process. A project debrief that surfaces something worth fixing gets turned into a workflow template, not a note in someone's head. Client feedback that repeats across projects gets built into a briefing checklist. A printer's specific quirks, an imprint's particular house rules, an editor's known preferences — all of it gets documented once and reused, rather than re-discovered on every new title. Every quarter, we go back through debriefs, client feedback and internal retrospectives and refine the workflows based on what actually happened, not what should have happened in theory.
The value shows up in the unglamorous detail. The quality checklists we run across our clients cover pagination, folio numbering, margins against the grid, whether pages match the manuscript, consistent heading formatting, correct colour use in text, consistently formatted lists, bad breaks across pages or columns, and — for the clients publishing internationally — a line space left in every section to accommodate co-editions. None of those items is interesting on its own. Together, they're the difference between a book that reads as considered and one that reads as rushed, and the difference between finding a problem at pass one and finding it at the printer.
Breaking a project into smaller pieces does the same job from a different angle. Clear ownership on each task, visible dependencies between them, and a single place where project status actually lives — rather than scattered across email threads and chat messages — means blockers surface while there's still time to solve them, and nothing depends on any one person's memory holding up under seasonal pressure.
For a publisher weighing up a new publishing partner, consistency across a list is usually the whole point of asking. It's also the thing that's hardest to promise honestly, because consistency at scale was never really a talent. It's infrastructure. Every checklist we run — editorial as much as design, a check against the manuscript as much as a check against the grid — exists because something once went wrong, and turning that into a process is the only way we know of making sure it doesn't happen twice.