When Craig Gauthier first sat down with me to talk about Rules: Optional, he said something I hear from a lot of founders. "I come from the speaking world, not the writing world. I'm a very good storyteller in person." The implication was the obvious one. Maybe he didn't have a book in him, because he wasn't a writer.

He had a book in him. The hundreds of keynotes he had given, the philosophy he had been refining in front of audiences for years, the clients he had taken from kids to CEOs, and the 150 people who would later read his draft and tell him what landed were all already in place. What he didn't have was a method for getting any of it onto the page.

This is the move I want to push back on. "I'm not a writer" feels like a verdict about whether you can write a book. It's actually a verdict about whether you can type one in long stretches alone at a desk. Those are different questions and they have different answers.

The Doubt Is About Typing, Not About the Book

A book takes four things, and three of them have nothing to do with writing skill.

The first is a reader you can actually picture. Not "founders" or "operators," but a specific person whose problems you've sat across from and solved. My pre-work question is the test: can you describe what that person believes before they hire you, and what they believe after they put your book down? If you can answer that in concrete terms, you have a reader.

The second is a position you'd defend in public. Not contrarian for its own sake. Just a clear take on the questions that matter in your field, and reasons you'd give if pressed. If you have been running a real business for a decade, you almost certainly have positions like this. You argue them at dinner, on calls, in your own marketing copy. You've just never thought of those positions as the spine of a book.

The third is stories. My standard for an Author.Inc author is 30 to 50 of them, drawn from three tiers: things you saw happen yourself, things that happened to your clients, and things that happened to public figures whose patterns illustrate the point. If you've been in your field long enough that someone could put you on a podcast and you'd never run out of examples, you've already gathered the third one.

The fourth thing, and the only one of the four that's actually about writing, is a process for getting the first three out of your head and into a structure that holds a reader's attention. That's the part that usually can't be solved alone, and it's the part Author.Inc was built around.

The Doubt Itself Is a Signal

The founders who don't have a book in them are rarely the ones worrying about it. The worry takes effort. It takes having read enough nonfiction to know what a good book reads like, and not wanting to write the other kind.

Geoff Woods had that worry. When he first came to us, he told me, "I don't know what I don't know." He had spent a decade running a strategy practice. He had hundreds of hours of executive conversations stored in his head. None of that felt to him like a book, because he had never sat down and typed 60,000 words. Thirty-nine days after we started, he had a manuscript, and what he had actually doubted was the typing rather than the having something to say.

Craig's path took longer than Geoff's, because Craig wrote his book three times before it became the book it needed to be. The first draft was rough enough that his honest friends ripped it apart. The second was over-corrected into academic territory nobody wanted to read. The third one worked. None of that was a problem of not having a book in him. It was a problem of getting the right book out of him, which is the next question after this one.

What to Check, Honestly

If you can name a specific reader and describe what they believe before and after they encounter your work, and if you have a position you'd defend in public, and if you could fill an evening telling someone the stories you've collected from your engagements, you have a book. The doubt is a misread of the situation. You are testing yourself against the wrong skill.

What you actually need is a process that pulls it out of your head and onto the page without costing you a year of your life.