Latest
Does Explicit Sex Sell Books? An Answer to The Absolute Degeneracy of Modern WritingThe Mary Sue: How a 1973 Star Trek Parody Became a Writing TermWhat the AI Writing Survey Says About Jobs, Freelancers and Fiction AuthorsHow Long Does Google Take? Crawling, Indexing and Recovery TimesLife of Pi50 Years of Duty: One Police Officer’s Compelling Journey from State Trooper to County SheriffBreaking Rank: A Top Cop’s Exposé of the Dark Side of American PolicingBlack in Blue: Lessons on Leadership, Breaking Barriers, and Racial ReconciliationCalled to Rise: A Life in Faithful Service to the Community That Made MeVigilance: My Life Serving America and Protecting Its Empire CityCollaborate or Perish! Reaching Across Boundaries in a Networked WorldTurnaround: How America’s Top Cop Reversed the Crime EpidemicThe Profession: A Memoir of Community, Race, and the Arc of Policing in AmericaSTEP-UP and LEAD: A Guide for Dynamic, Innovative Leadership in Law EnforcementStriving for Justice: A Black Sheriff in the Deep SouthThe Diagram GalleryGar Travis: A Tribute to One of the Best Faire PhotographersReverse Tropes: Six Ways to Turn a Tired Trope Inside OutA Hiker Used AI to Find a Waterfall. The Forum Sent Her to Hell.Did We Miscount the World’s Population? What the Rural Undercount MeansFrankenstein’s Creature Has Worn Many Faces. Only One Is Mary Shelley’sIs Consciousness Quantum? Penrose Is Half RightPetty Motivations Make Characters HumanAI Companies Are Preparing for a Catastrophe. Which One?Anatomy of a Writer: The Parts That Do the Real WorkGuillermo del Toro’s Writing Advice: Love Your MonstersFree Book Marketing: Seven Ways That Cost Time Instead of MoneyShould Your AI Report You to the Police?My Sister Built the Family We Never HadAnthropic Bans Cruelty Toward Claude: What It Means for WritersWork-for-Hire Contracts: What the Asimov’s Cover Fight Teaches FreelancersGenre Fiction vs Literary Fiction: Don’t Confuse Taste With SkillFlorida Hurricane Prep Rituals: The Grocery Run, the Water Pallet and the Generator in the BoxThe Most Insulting Line of Dialogue Ever Written for the ScreenLoki Through the Ages: From Norse Myth to Marvel, The Mask and Dogma“You Are Utterly Disgusting”: A Book Festival, an AI Cover Ban and a Pile-OnWho Rewrote the Sligachan Legend: AI or the Tour Buses?Layers: How I Ride Out Florida Power Outages in My ApartmentWhy I Don’t Like Reedsy for Ghostwriting: The NDA ProblemThe Enshittification of AmazonPublishers Cancel Books Over AI While Using It in SecretI Was Getting 100 Spam Emails a Day. $4.50 a Month Fixed It.World Mental Health Day: Nothing Was Wrong With MeKessler Syndrome: How Space Debris Could Close Earth’s OrbitAmazon Is Blocking Real Readers From Book ReviewsShould a Novella Get a Paperback, or Go Ebook Only?BookFunnel Download Problems: Fixes, Scams and AlternativesOzana Giusca: Reflecting the Architecture of IdentitySir Sean Connery: A TributeHow to Find Plot Holes in Your Novel (Most Are Character Holes)

What the Outline Actually Does

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 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 appears at exactly the right moment.

Most people assume that turning the interviews into a structure that works is the easy part of the process. For me it’s the hardest thing I do, and it starts once the knowledge base is built, reviewed, and approved. I dread this stage a little, and it’s the one I’d never hand off. The interviews are the fun part, because the client does most of the talking. The outline is where I have to decide what their book is, and if I get it wrong, every chapter after it inherits the mistake. In this stage we bang our heads on the wall trying to figure it all out. Quick unscheduled calls with the client save a lot of heartache here, so I expect plenty of them during this analysis phase. On one complex outline, Claude helped me organize the interview material and the client’s comments, and work that would have taken me a couple of weeks took one day. It was a bitch still, even at one day.

How is an outline different from a table of contents?

A table of contents is the document you produce after the thinking is done, while an outline captures the thinking itself before a word of the manuscript exists. The outline is 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. The finished outline is short. It’s a few pages in a Word document, each chapter listed in order with a short description, and on a typical project I aim to have it done, and maybe approved, within about a month.

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 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.

Behind that test sits the book’s unique selling proposition. Anything that meets it goes in the book, and anything that doesn’t stays out, with a few exceptions. It works as our promise to the reader about what the book delivers. The same statement becomes the online book page and the back cover, and we write the articles and the promo around it.

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 has no job to do in this particular book. Cutting it hurts. I have that conversation anyway, because the alternative is a reader skimming past the author’s favorite pages.

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. I tell clients to expect the audience to shift a little during the early interviews, because changing it costs nothing until the writing starts. We keep going over it until the clouds go away and we both feel we know who the reader is.

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 we’re writing Joe’s book for is a specific person: a line manager, one step above the frontline, who earned a promotion 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 structure. I put the heaviest effort into defining that audience and the book’s thesis before the outline exists, because if those are wrong, we head in the wrong direction. The outline can still change later. I don’t want to get to chapter 10 and find out that wasn’t our purpose at all.

Some of what they do works. Much of it produces results they can’t explain and can’t 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 can’t 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 establish that it understands the situation before it offers the solution.

The middle of the book is where most business books fall apart. That’s 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.

It’s the failure I see most in business books, and it frustrates me because the author usually knew the method cold. They explain it chapter after chapter as if the reader had already signed up, and the reader just stops.

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 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 book is repeating the argument. A great case in the wrong chapter goes to waste, arriving before the reader can appreciate it or after the book has already convinced them.

Placement is as much of the work as selection. Clients rarely notice this part of the work, and I don’t need them to. They hand me a story they’ve been telling for years, and my job is to find the one spot where it’ll hit hardest. Put it anywhere else and a great story reads like filler, and I take that kind of waste personally. 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 sets up 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 real checkpoint. 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. It’s a basic overview, so the client can tell me to take something out or move something up to the top. I need it to be true, because the outline becomes my basis of truth, and everything I write later is drawn from it.

I want pushback at this stage. A client who approves an outline to be polite is setting us both up for a rewrite at chapter eight, and I’d much prefer to hear what’s wrong now, while fixing it costs a conversation. I won’t start writing until the outline is finished, because it works as our agreement, though nobody has stuck to one 100% yet. Chapters get split in two a lot. Two chapters merging into one happens too, but much more rarely.

I tell clients to review the interview summaries just as carefully. AI helps me produce them, and AI’s going to screw up. Once the outline is done, it becomes the Bible, and I won’t accept more than minor changes after that. AI can’t see colored text or red-line edits, so I ask for changes in brackets, like code: [Delete this section] or [Add this section]. Most clients still don’t look, even when I tell them it’s the spec.

Everything after the outline approval is execution, and it’s hard work that needs sustained attention to voice and rhythm and the way Joe thinks about things.

Execution starts with another outline. Before I write each chapter, the client gets a page or two of bullet points for that chapter alone, lots of them. They turn it around quickly and tell me this is good, this is bad, I hate this. I adjust it, and the revised version becomes my spec for writing the chapter. That repeats through the whole project.

It’s built on a structure we’ve both agreed on, though. I don’t trust ghostwriters who skip this stage and start drafting to look productive. They’re spending the client’s money on chapters that’ll get torn apart later, and the client ends up paying for the book twice.

Frequently Asked Questions

What is the difference between an outline and a table of contents?

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.

What test does each chapter have to pass?

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.

Why do business books fall apart in the middle?

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. That 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.

Why does an outline start with the problem instead of the solution?

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.

Where should case studies go in a business book outline?

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’ve 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.

Should an author review a ghostwriter’s outline before writing begins?

Yes, and that review should be a real checkpoint. The outline represents my best understanding of the book, built from everything the client told me during the interviews, and 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.

About the Author
Richard Lowe, professional ghostwriter

Richard Lowe is a professional ghostwriter and author with 113+ books authored and 54+ ghostwritten. Before writing full time he spent 33 years in enterprise technology, including 20 years as Director of Computer Operations and Technical Services at Trader Joe's. He writes nonfiction, fiction and memoir, and works with executives and experts on books that build authority.

More about Richard Lowe →

Disclaimer

The views and opinions expressed in this blog post are solely those of Richard Lowe and are based on personal experience and research. This content is for informational purposes only and should not be construed as professional legal, financial, accounting, or business advice. Always consult with qualified professionals before making important business or legal decisions. Richard Lowe is not a lawyer, accountant, or licensed professional advisor, and this content does not establish any professional relationship.

0 comments

No comments yet. Yours can be the first.

Was this useful?

Leave a comment