Your Book Doesn't Need More Facts. It Needs a Better Story.
I've said some version of this to almost every business and personal development author I've worked with, so it's time I said it here too.
You know your material. That was never the question. The question is whether your reader feels it.
Here's what I mean: You can have a manuscript full of accurate, well-organized, genuinely useful information, and readers will still put it down halfway through. Not because it's wrong. Because it never became real to them. A concept stays a concept until a reader sees themselves in it. And that happens through story, not through explanation.
The misconception
Authors often worry a story will make the book feel less credible—less "expert," more anecdotal. Like the stories are the fluff around the real content.
It's the opposite. A well-placed story is what earns you the right to be believed. It's the moment a reader stops thinking "sure, in theory" and starts thinking "oh my gosh, that's me." or “She’s totally right; I’ve seen that happen.” Stories are what makes your point hit home.
Think about the personal development and business books that stayed with you. Chances are you don't remember the frameworks in isolation; you remember the moment a specific example made a framework click. The story is doing the real cognitive work: it lets a reader identify with what you're describing, relate it to their own life, and feel the weight of why it matters. Information tells a reader something is true. A story shows them it's true for people like them.
What this looks like on the page
Here's the same idea, told two ways.
Information version:
"Delegation fails most often because leaders don't trust their team to meet their own standards. This creates a cycle where the leader keeps taking work back, the team stops growing, and burnout follows."
True. Useful. Also completely forgettable ten minutes after you read it.
Story version:
"I used to rewrite my assistant's emails before they went out—every one, without fail. It took me twenty minutes a day and I told myself it was 'just being thorough.' Then I got the flu for a week and couldn't check anything. When I came back, her emails were fine. Better than fine—a client had replied to one of them, 'This is exactly what I needed to hear.' I hadn't been protecting quality. I'd been protecting my own discomfort with letting go."
Same lesson. Completely different experience for the reader. The first version tells them a fact about delegation. The second one lets them feel the specific, slightly embarrassing moment of realizing they're the bottleneck, and that recognition is what actually changes behavior. Readers don't act on facts they've been told. They act on moments they've recognized themselves in.
Connection is the whole point, not a bonus
This matters for more than the reading experience. It's also what determines what happens after someone reads your book.
The books that get recommended to a friend, that land the podcast invite, that turn a reader into a client—those are almost always the ones where the reader felt known by the author, not just informed by them. A reader who feels connected to you trusts you. And trust is what turns into a referral, a speaking invitation, or a "I have to work with this person."
Connection is what people remember and repeat.
The question to ask about every chapter
If you're deep in a draft right now, here's the test I'd apply, chapter by chapter: where's the moment my reader sees themselves?
If you can't point to one, that's usually the fix. Not more explaining. One true story, told well.
If you're staring at a draft that has all the right information but isn't quite landing yet, that gap is almost always smaller than it feels—and it's a lot of what I work on with authors in a developmental edit. If that's where you are, I'd love to talk.
