TL;DR
The interview phase is over and the knowledge base is built. Now comes the hardest thing I do: turning everything into a structure that works. An outline for a business book is not a table of contents. It is the thinking itself, captured before a word of the manuscript exists, where every chapter gets tested against the central argument. Each chapter has to move the reader from one position to another. Joe Rockey’s book is written for a specific person, a line manager promoted without preparation, and the outline maps the path from the problem they live with to the solution, assigning each client story to the chapter where it lands at exactly the right moment.
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.
An outline for a business book is not 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 is where everything that came out of the interviews gets sorted, sequenced, and tested against the central argument of the book. Chapters that do not pass the test do not make it into the outline. They get set aside, folded into other chapters, or recognized as material that belongs in a follow-up project rather than 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 requires real discipline to apply: does this chapter have a specific job to do 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 does not 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 is always material that is genuinely interesting, that the author loves, that took real work to develop, and that simply does not have a job to do in this particular book. Cutting it is painful. But a chapter that is there because the material is good rather than because it moves the argument forward is dead weight, and 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 it gets written, when cutting it costs nothing.
Mapping the argument chapter by chapter
What I am 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 is 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 are frustrated in a low-grade ongoing way and running out of approaches to try. Joe named the core problem they are 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 individuals doing something until they go home.
The book has to meet that person where they are, which means the early chapters cannot start with the solution. They have to start with the problem, specific enough that the reader feels recognized, not processed. 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 is where books die
The middle of the book is where most business books fall apart. The middle is where the methodology gets introduced and explained, and explanation sustained over multiple chapters is where readers most often lose interest. It does not 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 is still deciding needs something different.
The solution is to weave explanation into story. Every principle gets demonstrated through a case, a real situation with real stakes where the methodology was applied 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 is 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 is happening in the case, but before they would 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 the path from the first quote to the last gets drawn. Every chapter earns the right to what comes after it. Once the outline is finished, Joe reviews it. He tells me what is missing, what is 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 has been agreed on. The structure questions are settled. The sequence is in place. The argument is mapped. What remains is to write it.
The Guides That Get Your Book Written, Published, and Sold
Four short, practical guides on writing, publishing, and selling your book, plus the occasional note when there's something worth your time. No fluff, no daily inbox clutter. Drop your email and they're yours.
We use MailerLite to manage our list and send these emails. Your address is used only to send you what you signed up for. We will not sell it, share it, or use it for anything else, and you can unsubscribe anytime.
Frequently Asked Questions
A table of contents is produced after the thinking is done; an outline is the thinking itself, captured before any manuscript exists. The outline is where interview material gets sorted, sequenced, and tested against the book’s central argument. Chapters that do not earn their place get cut, folded in, or saved for a future project.
Whether it has 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 does not belong in the book.
Because the middle is where the methodology gets explained, 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 the method was applied and the outcome mattered.
Because the reader has to feel recognized before they will 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.
Each case is assigned to the chapter where it lands at exactly the right moment, after the reader understands enough to appreciate it, but before the argument would start to feel repeated. A strong case in the wrong chapter is wasted. Placement is as much of the outlining work as selecting which stories to use.
Yes, and it is a genuine checkpoint, not a formality. The outline is the ghostwriter’s best understanding of the book built from everything the author said, and the author’s review is the first real test of whether that understanding is accurate. They flag what is missing, what is out of sequence, and where the book should spend more time.