Somewhere around chapter four you’re going to hate the book.
Not the whole project. One chapter, usually in the middle, and usually not the worst one. The prose will be fine and your objection will be real and it’ll have very little to do with the writing.
That’s the first of a set of things that happen to nearly everybody who writes a book with help, and that almost nobody mentions in advance. They’re not risks and they’re not warning signs. They’re stages, and every one of them is survivable if you know it’s coming.
The reason they matter is that people who are surprised by them tend to draw the wrong conclusion. A chapter that reads badly becomes evidence that the writer is wrong for the project. A schedule that slips becomes evidence that the thing is out of control. A flat week after the manuscript is finished becomes the reason a completed book sits in a folder for a year.
None of that is what’s happening. What’s happening is the ordinary shape of the process, arriving on time.
Here’s what to expect.
You will hate one chapter for no good reason
It’s usually somewhere in the middle and it’s usually not the worst chapter.
Something about seeing your own material written down by somebody else produces a strong reaction, and the reaction lands on whichever chapter you happen to read at the wrong moment. The prose is fine. Your objection is real and it’s rarely about the writing.
What’s happening is that the chapter contains a version of you that you haven’t agreed to yet. Reading it’s the first time you’ve seen yourself described instead of experienced yourself deciding.
It passes. What helps is knowing in advance that it’s coming, so that when it arrives you say this chapter is wrong and not this whole project is wrong.
Somebody else will know your career better than you do
By month three, the person writing has heard every story you tell and noticed which ones you tell more than once.
That’s a strange feeling. They can tell you which decision you keep circling back to, which year you skip over, and which person comes up in three different stories that you’d never connected.
It’s also the entire value of the arrangement. You cannot see the shape of your own career because you were inside it. Somebody who has heard all of it in a compressed few months can.
Most people find this uncomfortable for about a week and then start relying on it.
The interviews will go somewhere you did not plan
You’ll schedule two hours to cover the second company and spend ninety minutes on something that happened before it.
That’s not a failure of preparation. It happens because the material a book needs is rarely where you filed it, and a good interview follows what’s producing detail instead of what is on the agenda.
The correction is normally a better book. The cost is that the schedule you agreed to won’t survive contact with the actual conversations, and knowing that ahead of time prevents a month of feeling behind.
You will want to protect somebody
A story that matters to the book involves a person who comes out of it badly, and that person is real.
This arrives without warning, usually in the middle of a session where you were talking about something else. You’ll stop, and the room will go quiet, and you’ll say that you cannot put that in.
Sometimes you’re right and the story stays out. Sometimes the story can be told in a way that carries the lesson without the identification. What matters is having the conversation deliberately, in the middle of the project, instead of discovering the problem in a legal review at the end.
You will want to add things that do not belong
Usually late, and usually because the book has started to look thin next to your career.
Somewhere in the second half, most people notice that a significant piece of their history isn’t in the book. A company they turned around, a period they’re proud of, a set of results that matter. It’s missing because it doesn’t serve the argument, and it feels like an omission, not a decision.
The instinct is to add a chapter for it. That chapter is nearly always the weakest one, because it exists to be complete instead of to be useful.
A book isn’t a record of your career. It’s an argument that uses parts of your career, and the parts it leaves out aren’t being denied. They’re being saved.
Somebody will ask what your family thinks
And you’ll discover you hadn’t asked them.
Any book drawn from a life touches people who didn’t sign up for it. A colleague, a former partner, a parent, a child. Most of them appear briefly and harmlessly, and one or two of them are in a story that matters.
Authors handle this in one of two ways. Some talk to the people involved during the writing, which is uncomfortable and almost always goes better than expected. Others publish and find out afterwards.
The first group has an easier year.
The book will change what you think
This one surprises people who came in certain.
Explaining a decision to somebody who’s going to write it down forces a level of precision that ordinary recollection never demands. Halfway through describing why you did something in 2014, people quite often stop and say that they’d always told it differently.
That’s the process working. A career examined at that resolution rarely looks the way it looked from inside.
It also means the book you finish isn’t always the book you commissioned, and the difference is usually an improvement.
The week after the manuscript is finished is the hardest one
Nobody expects this and almost everybody experiences it.
For months there’s been a rhythm. Sessions, drafts, reactions, corrections. Then it stops, and what’s left is a finished object and a set of decisions about covers and printing and launch that feel administrative after what came before.
There’s also a small grief in it. The thing that was becoming is now fixed, and every version you didn’t choose is gone.
People who know this is coming handle it. People who don’t tend to stall exactly here. That’s how a finished manuscript ends up in a folder for a year.
You will read it later and want to change something
That’s a property of books, not a defect in yours.
Two years on you’ll know something you didn’t know when it was written, and the book won’t contain it. This bothers people more than it should.
A book is a photograph of what you understood at a particular moment, and that’s what makes it useful to somebody reading it. A book that contained everything you’d ever know would have to be written at the end of your career, which is the argument for writing one now.
The answer to knowing more later is a second edition or a second book. It’s not a reason to postpone the first.
What makes the difference between projects that finish and projects that stall?
Whether somebody said any of this out loud at the start.
Every surprise on this list is predictable. The chapter you dislike, the schedule that moves, the person you want to protect, the flat week at the end. None of it is unusual and all of it derails people who thought it was happening only to them.
A project where these were named in the first conversation treats each one as a stage. A project where they weren’t treats each one as evidence that something has gone wrong.
That’s the whole difference, and it costs nothing except a conversation nobody wants to have while everybody is still enthusiastic.