Subscribe
Share
Share
Embed
Compare each chapter’s purpose with its draft and track missing explanations before polishing.
You already explain your best ideas to clients, colleagues, and audiences. Join Mike Giannulis, founder of Dictate, for practical 10- to 15-minute episodes on turning that spoken expertise into a published book through conversations with an AI interviewer. Each episode gives experts, coaches, and business owners one clear step to capture their ideas, shape their message, and move their book forward.
Episodes of this show are narrated by an AI-generated voice.
Recorded ideas need a clear path for the reader. Today we will give each chapter a job, track what it promises, and check whether the draft delivers.
Welcome to Talk Your Book Into Existence with Mike Giannulis, founder of Dictate. Learn how to turn the ideas you already share out loud into a published book, one conversation at a time. Today, you will leave with one practical step you can use on your own book.
A quick note before we begin: this episode is narrated by an AI-generated voice.
Give Every Chapter One Clear Job.
Before you can turn your recorded conversations into a manuscript, you need a map. Not a complicated one. Just a clear answer to the question: what does each chapter need to do?
Consider a hypothetical business book with a strong opening. The author promises to explain a client acquisition process, but the later chapters shift to industry trends and motivation. The promised process never appears. The reader has a reasonable question: where is the explanation I was told to expect?
An author can overlook that gap because the connections already make sense in their own head. The reader only has what is on the page. A structural review helps you compare what you intended to teach with what the manuscript actually explains. It gives you a chance to supply the missing material before publication.
In my book, I offer a five-part planning model for practical nonfiction. Start with the promise: what will the reader learn? Then consider the proof: what relevant evidence, examples, or experience supports the explanation? The method is the process or framework you teach. Implementation shows how a reader might apply it, including the conditions and limits that matter. Finally, consider what sustained practice could look like. Describe realistic possibilities rather than guaranteeing a result after a fixed number of months.
These are planning questions, not mandatory section titles. Different books may arrange the material differently, and some chapters will combine several functions. Use the model to notice missing explanations. A memoir, reference guide, and step-by-step workbook will not need identical structures. The useful test is whether your arrangement serves the reader and the particular promise of this book.
Here's how to use this as a planning tool without getting rigid about it. Before you structure your chapters, write down what each section needs to accomplish. Not the topic. The job. There's a difference. "Chapter 4 covers hiring" is a topic. "Chapter 4 takes the reader from knowing they're overwhelmed to knowing exactly when it's time to make their first hire" is a job. One of those gives the chapter direction. The other just gives it a subject.
Pay attention to sequencing. What does the reader need to understand before the next idea makes sense? If a framework depends on a term you have not defined, add the explanation or move it earlier. A reader unfamiliar with your work can help identify those jumps. Ask where they needed more context, rather than assuming that a smooth paragraph proves the sequence works.
A useful addition to your planning document is a reader journey column. After each chapter, write one or two sentences describing what the reader should now understand and what remains to be explained. Compare that intended result with the actual draft. If the chapter names a process without showing how to use it, the reader may recognize the label but still lack the skill you promised.
This kind of upfront planning isn't about making your book formulaic. It's about making sure the structure holds the material together so your best ideas actually land.
If you want to work through this process in more detail, my book, Talk Your Book Into Existence, is at startdictate.com/talk-your-book. The link is also in the episode notes.
Track What You Promise and What You Deliver.
Once you have a structural plan, you need a way to track it as the manuscript develops. A book can involve many sessions and revisions. By Chapter 8, you may not remember exactly where you defined a term or promised to return to an example. A simple record lets you check those details without relying entirely on memory.
In my book, I call this record the Continuity Ledger. You can use a spreadsheet with four columns and update it after a chapter or dictation session. A document or notebook can work too, provided you can find and update the entries easily.
Column one: concepts introduced. Every time you define a term, name a framework, or introduce an idea for the first time, you log it here. You note which chapter introduced it and whether it's been fully explained or just mentioned in passing.
Column two: forward promises. Every time you say something like "we'll get to that in Chapter 7" or "I'll walk you through this in the next section," you log it here. You note which chapter made the promise and which chapter is supposed to fulfill it.
Column three: stories used. Every anecdote, case study, or personal story gets logged. You note whether it's been resolved if it was a setup, and whether you've called back to it later.
Column four: reader journey state. After each chapter, you write one or two sentences about what the reader now knows and what they expect next.
Keep the entries brief enough that you will maintain them. A short update after a session is a useful habit; the time required will depend on how much material changed. You do not need to catalog every sentence.
Let me show you what it does in practice with a hypothetical example. Say you're writing a book on financial planning for business owners. In Chapter 2, you introduce something you call the Three Bucket System. You explain Bucket One in detail, then mention that Buckets Two and Three are coming later. Your ledger now shows one entry in column one, and two entries in column two. Forward promises, both unchecked. When you get to Chapter 5 and you cover Bucket Two, you check it off. When you get to Chapter 7 and you realize you never covered Bucket Three, the ledger catches it before your reader does. The unchecked entry points to a specific gap you can now resolve. This is an example of tracking a book’s explanations, not advice about how anyone should manage their finances.
Here are four structural patterns to check. First, a chapter title may promise something the body does not deliver. Reading the title alongside the opening and ending is a quick screen, but inspect the middle as well. If the promised explanation is absent, either supply it or change the promise to match the chapter's actual purpose.
Second, look for unfulfilled promises. A reference to a later explanation can become outdated when chapters move or sections are cut. Check the destination, not just the chapter number. Mark the ledger entry complete only when the explanation is actually present, or remove the promise if it no longer belongs.
Third, check for stories whose relevance is unclear. A story might introduce a problem, illustrate a decision, or show a limitation. Ask what this particular story contributes. Sometimes a short bridge makes the connection clear. Sometimes the story belongs elsewhere. An anecdote can illustrate a point without proving that the same result will happen for every reader.
Fourth, review the ending against the kind of book you promised. For a practical guide, a useful close can help the reader choose a next step and recognize when to seek more information. It need not prescribe an exact week, month, and quarter for everyone. A reflective book may have a different ending. What matters is bringing the promised journey to a coherent close.
Before a new session, scan the ledger for open promises and unfinished examples. Choose one that the session can address. This can help you catch missing material before you invest time in polishing it. Keep the ledger responsive to the draft: it is a working aid, not another document that must become perfect.
Turn Your Transcripts into a Structured Draft.
Here's where a lot of people get tripped up. They finish their dictation sessions, they look at the transcripts, and they think the hard part is over. The stories are there. The frameworks are there. The language is there. So they clean up the filler words, add some headings, and call it a chapter.
A transcript can preserve useful language and still need substantial editing. Spoken explanation and written prose are related, but they serve different situations. Conversation can rely on a listener's question or shared context. A chapter needs to supply the context that a reader on their own will need.
So before you start refining sentences, you audit what you actually have. Compare your structural plan against the draft. Where the outline said the chapter would deliver a specific idea, did the draft actually deliver it? Where you planned to transition from proof to method, does the draft make that transition clearly, or does it drift? That comparison is where you find the gaps and the repetitions before a reader does.
When you find a gap, identify what is missing. It could be an example, a definition, a step in the process, or a transition. Repetition may come from explaining the same idea in several recording sessions. Sentence editing can improve clarity, but it cannot supply an explanation that was never captured. Decide what to add, move, or combine before refining every line.
Consider a hypothetical author writing about planning a workshop. In one recording, the author describes an overcrowded agenda, lists several exercises, and explains why the session needs a clear learning objective. The material includes a useful question: what should participants be able to do by the end? This is an invented illustration of organizing material, not a report of a client result.
In the transcript, those pieces might arrive in a tangled order. The agenda story appears halfway through a discussion of exercises, and the learning objective is explained near the end. You can preserve the idea while changing that sequence so the reader first understands the decision the chapter will help them make.
The first pass through that material is extraction. You pull the usable pieces and sort them. Story in one bucket. Framework language in another. Contrarian points in another. You're not writing yet. You're organizing.
The second pass is assembly. In the workshop example, the chapter's job is to help a reader connect an agenda to a learning objective. You might begin with the problem of an overfilled agenda, define the objective, and then show how to select exercises that support it. A short application could ask the reader to compare each planned activity with that objective and explain why it belongs.
The third pass is voice. You keep what sounds like the author. You cut the circular setup, the repeated phrasing, the five-minute detour that made sense in conversation but drags on the page. A good voice pass doesn't make the author sound more polished than they are. It makes them sound like the clearest version of themselves.
The fourth pass is continuity. You bring the ledger back in. What did this chapter promise? Did it deliver? Did it repeat a story from an earlier chapter? Did it introduce a question the next chapter needs to answer? This is the pass that keeps a collection of good chapters from being just that: a collection, rather than a single argument that builds.
Checking content and structure before detailed polishing can reduce avoidable rework. You may still move between these passes as you discover problems. The point is to avoid treating elegant sentences as evidence that a chapter fulfills its promise. A paragraph can sound excellent and still belong in a different chapter.
One practical step: before you draft any chapter, write the chapter promise in one sentence at the top of a blank page. Under that, list the three to five things the chapter must deliver. Then work from that, not from the full raw transcript. The transcript is your source material. The chapter packet is your target. Draft toward the target.
When a chapter promises something it does not deliver, make a specific revision note. Add the missing explanation or revise the promise. When material repeats, choose its main home and decide whether another mention is a useful recap or unnecessary duplication. A deliberate reminder can help readers; an accidental repetition may simply lengthen the book. Make that choice in relation to the reader's task.
Choose one chapter and write down its job in a sentence. Compare that promise with the draft. Mark one missing explanation and one repetition, then decide what to add, move, or cut. Update your continuity ledger so the next session starts with a specific task.
Take the next small step on your book today. For more guidance, find Talk Your Book Into Existence at startdictate.com/talk-your-book.
Visit startdictate dot com slash talk your book.
Next time on Talk Your Book Into Existence: Prepare Your Book for Readers: Cover, Proof, and Publication. Review the details between a finished draft and a book you are ready to share. Follow the show so the next episode is ready when you are.
Thanks for listening to Talk Your Book Into Existence. Follow the show for your next practical step, and share this episode with someone who has a book in them. Your next conversation could be the start of a chapter.