A draft arrives and something is wrong with it.
Not a typo. Something structural. The chapter says what you said and it doesn’t sound like you, or it emphasizes the wrong part of a story, or it makes an argument you agree with in a way you’d never have made it.
That moment decides more about the project than anything before it. Handled well it produces a better book and a working relationship that survives another six months. Handled badly it produces a client who stops reading drafts, approves everything, and quietly loses interest in a book they’re still paying for.
The difficulty is that most people have no practice at this. Giving detailed critical feedback on somebody else’s writing about your own life isn’t a skill anybody develops in an ordinary career, and the natural instincts are mostly wrong.
Some people go quiet and hope the next chapter is better. Some rewrite the passage themselves, which solves one chapter and teaches the writer nothing. Some deliver a general verdict, saying it doesn’t feel right. That’s true and unusable.
There’s a version of this conversation that works, so check before the first draft lands.
Decide how you’ll handle the first chapter you dislike before you receive it, because your instinct in the moment will be to say something vague or nothing at all.
Why does a good first draft still feel wrong to the author?
Because you’re reading yourself described for the first time.
Everything you have ever said about your career, you said out loud, to somebody, in a conversation you were steering. Reading it back as prose is a different experience and the strangeness isn’t a quality judgment.
That reaction is strongest in the first two or three chapters and fades. Plenty of authors dislike a passage on Monday and find it fine on Thursday, having changed nothing.
Which is an argument for sitting with a draft for a day before responding. Not to be polite. Because the first reaction and the considered one are frequently different and only one of them is useful.
What kind of feedback on a ghostwritten chapter is usable?
Specific, located, and about effect instead of preference.
This paragraph makes it sound like the decision was obvious, and it wasn’t. That’s usable. It names a place, describes what the text does, and says why it’s wrong.
I don’t like this chapter isn’t usable. Neither is make it punchier, which is a request for an outcome with no information about the problem.
The most useful thing an author can say is what a reader would wrongly conclude from a passage. That points straight at the fix and it uses knowledge only you have.
What should you not do when you disagree with a ghostwritten chapter?
Rewrite it yourself.
It’s the obvious move and it feels efficient. You know what you meant, so you fix the paragraph and send it back, and the chapter is now correct.
What has happened is that the writer learned nothing about why it was wrong, so the same error appears in chapter nine. And a book with rewritten passages scattered through it develops two voices, which readers notice without being able to say what’s bothering them.
Describe the problem. Let the person whose job it’s solve it. If they cannot solve it twice in a row, that’s real information about the relationship and it’s better to have it early.
When is the disagreement about something else?
When it keeps happening in the same place.
A recurring objection to how a particular period gets written is rarely a writing problem. Usually there’s something about that period you haven’t said, or have said in a way that protects somebody, and every draft of it’ll feel wrong because the material is incomplete.
A good writer notices the pattern and asks. That conversation is uncomfortable and it normally produces the best chapter in the book.
If nobody asks, the section stays slightly false through every revision, and it’s usually the one readers find flat.
How should the conversation with your ghostwriter go?
In writing first, then out loud.
Notes in the document are better than a call for the specific objections, because they stay attached to the passage and the writer can work through them without reconstructing what you meant. Nobody remembers a verbal note about paragraph three of chapter six.
What the call is for is the pattern. Whether the voice is drifting, whether the structure is holding, whether something about the whole approach needs to change.
Doing it the other way round, a long call about specific paragraphs, produces a conversation that both parties leave with different notes.
How should author feedback change over a ghostwriting project?
The objections get fewer and more specific.
Early chapters draw a lot of feedback, much of it about voice, and that’s the calibration happening. By the middle of a book it should be down to a handful of points per chapter, mostly factual or about emphasis.
If the volume of objections isn’t falling by chapter six, something is wrong that more feedback won’t fix. Either the voice was never captured, or the two of you have different books in mind, and both of those are worth naming out loud instead of grinding through.
A project where the author is still rewriting the tone in chapter twelve is a project that should have had a difficult conversation at chapter four.
What if you are simply wrong about a chapter?
It happens, and a writer who never says so isn’t doing the job.
Authors sometimes object to something that’s working. A story that feels self-indulgent to the person who lived it’s frequently the most engaging passage in the chapter. An admission that feels exposing is often what makes the whole book credible.
You’re the worst-placed person to judge that, because you’re the only reader who was there.
So the exchange should go both ways. If your writer agrees with every objection you raise, you’ve hired somebody who’s managing you instead of making the book better.