My editor wants to cut stories that explain how I built the company. How do I decide which ones belong in the book?
Judge each story by the work it does for the reader, not by its importance to your personal history. Preserve stories that explain a decision, demonstrate a mechanism, establish a relevant limitation, or make an abstract idea understandable.
This is the purpose of big-picture editing, sometimes described as editing by chainsaw: remove material that obstructs the book's structure and flow before polishing individual sentences. It does not mean stripping the manuscript of personality.
Give each disputed story a one-sentence job description. Then ask:
- What does the reader understand after this story that they would not understand without it?
- Does another example already do that job better?
- Does the story support the chapter's argument, or merely share its subject?
- How much background must the reader absorb before reaching the useful point?
If the story has a clear function but takes too long, shorten the setup and retain the decision, consequence, and lesson. If its function belongs elsewhere, move it. If it adds only company history to a practical chapter, consider removing it or placing it in supplementary material.
Use AI as a redirectable coeditor: ask it to identify each story's apparent function and compare overlapping examples, without rewriting them yet. Review those judgments yourself. An apparently repetitive story may reveal an important exception.
Keep a separate cut-material document. Removing a passage from this book is an editorial decision, not a judgment that the experience was unimportant.
Category: Developmental editing