A business book with a keynote date that could not move

The constraint

Desmond had a manuscript and a date. He was giving a keynote at a summit eleven months out, and the book had to be in the room. That is a fundamentally different scheduling problem from publishing when the book is ready.

Planning backwards

We built the schedule in reverse: copies in hand two weeks before the event, print run four weeks before that, files locked six weeks before print, proofread and corrections before that, and so on back to the developmental edit.

The exercise produced one uncomfortable output: the manuscript, at 94,000 words, could not be developmentally edited, revised, copyedited, typeset, proofed and printed inside the window. Something had to change, and the honest options were to cut the book or move the date.

The cut

The developmental read had already flagged the structural issue common to practitioner-written business books: the manuscript was organised around Desmond's framework rather than around the reader's question. Three chapters existed to complete the model rather than because a reader needed them.

Cutting them removed roughly 28,000 words and, according to the editor, improved the book independently of the schedule. Desmond disagreed for about a fortnight and then agreed.

Print and bulk

Because copies were being handed out at an event, we set up a short offset run alongside print-on-demand. Bulk pricing and invoicing were configured in advance, which turned out to matter — two attendee organisations ordered volume copies in the weeks after the keynote, and the process was already in place.

Hitting the date

Copies arrived sixteen days before the keynote. The margin existed because it was designed in, not because everything went smoothly — the proofread slipped by nine days when Desmond was travelling, which the contingency absorbed.