The interview phase is over. The knowledge base is built, reviewed, and approved. Now comes the part of the process that most people assume is easy and is in fact the hardest thing I do: turning everything into a structure that works.
How is an outline different from a table of contents?
An outline for a business book isn’t a table of contents. A table of contents is the document you produce after the thinking is done. An outline is the thinking itself, captured on paper before a word of the manuscript exists. It’s where I sort everything that came out of the interviews, sequence it, and test it against the central argument of the book. Chapters that don’t pass the test don’t make it into the outline.
They get set aside, folded into other chapters, or recognized as material that belongs in a follow-up project instead of this one.
An outline is not a table of contents. It is the thinking itself, captured on paper before a word of the manuscript exists.Share on X
The test each chapter has to pass is simple to state and hard to apply. Does this chapter have a specific job in the arc of the book? And does completing that job create something in the reader’s understanding that makes the chapter after it possible? Every chapter in a business book should move the reader from one position to another. It should change something. If a chapter is only adding information without changing anything about how the reader sees the central problem, it doesn’t belong in the book.
That test is harder to apply than it sounds, because the chapters that fail it are often the ones the author is most attached to. There’s always material that’s interesting, that the author loves, that took real work to develop. And it’s no job to do in this particular book. Cutting it’s painful.
A chapter that exists because the material is good, instead of because it moves the argument forward, is dead weight. The reader feels the book slow down every time they hit one. Part of the outline’s job is to identify that material early, before anybody writes it, when cutting it costs nothing.
What I’m building for Joe Rockey’s book is a chapter-by-chapter argument map. For each chapter I need to know three things. What the reader believes when they enter. What they believe when they leave. And what that shift makes possible in the sequence that follows. The book as a whole is a series of those shifts, and the sequence has to be right. Get it wrong and the reader loses the thread. Put the most important argument too early and there’s nothing left to earn.
Put it too late and the reader gives up before reaching it.
The reader Joe’s book is written for is a specific person: a line manager, one step above the frontline, who got promoted because they were good at their individual work and found themselves responsible for a team of people with no real preparation for what leadership requires. They have natural instincts but no systematic framework. Some of what they do works. Much of it produces results they cannot explain and cannot replicate consistently. They’re frustrated in a low-grade ongoing way and running out of approaches to try.
Joe named the core problem they’re living with:
Talent isn’t the problem. Alignment is.
And the before state most of his clients are in when they first hire him:
Many companies, regardless of what they claim, are a collection of people doing something until they go home.
The book has to meet that person where they are. That means the early chapters cannot start with the solution. They have to start with the problem, specific enough that the reader feels recognized. A reader who feels recognized will follow you anywhere. A reader who feels like one of many will stop on page twelve. The book has to earn the right to offer the solution by first establishing that it understands the situation.
The middle of the book is where most business books fall apart. The middle is where I introduce and explain the methodology, and explanation sustained over multiple chapters is where readers most often lose interest. It doesn’t matter how sound the methodology is. A sustained explanation of how something works, without people and situations and stakes to make it concrete, is a tutorial. Tutorials are for people who have already decided to do the thing. The reader who’s still deciding needs something different.
The solution is to weave explanation into story. Every principle gets a case behind it, a real situation with real stakes where somebody applied the methodology and the outcome mattered. The book explains the system and then immediately shows the system at work in a context the reader can recognize. That’s how a person actually learns something: by seeing it applied, repeatedly, in situations where something is on the line.
Joe has the cases. Six sessions of interviews produced more usable client stories than the book will have room for. The outline’s job is partly to assign those stories to the chapters where they arrive at exactly the right moment, after the reader understands enough to appreciate what’s happening in the case, but before they’d start to feel the argument is being repeated. A great case in the wrong chapter is wasted, landing before the reader can appreciate it or after they have already been convinced.
Placement is as much of the work as selection.
The book needs to move the reader from the before state to the after state:
Instead of ‘everyone try harder,’ your team rallies around a visible target and a shared win.
The mechanism that makes the transformation sustainable:
Once you master retention, recruiting is really easy.
And the connecting thread that holds the whole arc together:
The victory comes from the small things, not from the mega things. And this is coming from a guy who does a mega one-off event of putting you on a cruise.
The outline is where I draw the path from the first quote to the last. Every chapter earns the right to what comes after it. Once the outline is finished, Joe reviews it. He tells me what’s missing, what’s in the wrong sequence, and what he wants the book to spend more time on. That review is a genuine checkpoint, not a formality. The outline represents my best understanding of the book, built from everything Joe told me. His review is the first real test of whether that understanding is accurate.
Everything that comes after the outline approval is execution. Hard execution, careful execution, execution that requires sustained attention to voice and rhythm and the specific way Joe thinks about things. But execution from a foundation that’s been agreed on. The structure questions are settled. The sequence is in place. The argument is mapped. What remains is to write it.
Frequently Asked Questions
A table of contents comes after the thinking is done; an outline is the thinking itself, captured before any manuscript exists. The outline is where I sort interview material, sequence it, and test it against the book’s central argument. Chapters that don’t earn their place get cut, folded in, or saved for a future project.
Whether it’s a specific job in the arc of the book, and whether doing that job creates something in the reader’s understanding that makes the next chapter possible. Every chapter must move the reader from one position to another. A chapter that only adds information without changing how the reader sees the problem doesn’t belong in the book.
Because the middle is where I explain the methodology, and sustained explanation over several chapters is where readers lose interest. Explanation without people, situations, and stakes is a tutorial, which only suits readers who have already committed. The fix is weaving each principle into a real case where somebody applied the method and the outcome mattered.
Because the reader has to feel recognized before they’ll accept a solution. Starting with the problem, specific enough that the reader sees their own situation, earns the right to offer the answer. A reader who feels recognized follows you anywhere; a reader who feels processed, like one of many, stops within a few pages.
I assign each case to the chapter where it lands at exactly the right moment, after the reader understands enough to appreciate what’s happening, but before the argument would start to feel repeated. A great case in the wrong chapter is wasted, landing either before the reader can appreciate it or after they have already been convinced. Placement is as much of the outlining work as selecting which stories to use. Six sessions of interviews can produce more usable client stories than a book has room for, so deciding exactly where each one lands matters as much as choosing it in the first place.
Yes, and that review should be a genuine checkpoint, not a formality. The outline represents my best understanding of the book, built from everything the client told me during the interviews. Their review is the first real test of whether that understanding is accurate. They tell me what’s missing, what’s in the wrong sequence, and what they want the book to spend more time on. Once that review is done and the outline is approved, everything after it is execution from a foundation that’s already been agreed on.