That photo above is from this morning.
Â
Moving snow on the tractor before our family headed to the airport.
Â
(Because of course Vermont decided to dump a major snowstorm on us the night before we leave for Paris.)
Â
So while Tylene and the boys were packing suitcases, I was out on the Kubota at dawn, clearing the driveway in subzero temps so we could actually get out.
Â
One minute you’re pushing snow in Fjallraven pants. A few hours later you’re on a bus to the airport for an overnight flight to France.
Â
(Also in Fjallraven pants.)
Â
That’s the Return to Real life, bay-bee!
Â
But before we took off on our flight, I wanted to share something I’ve been obsessing over this past week…
Â
Because over the last few days, the first round of beta reader feedback came back on the manuscript for my upcoming book, Return to Real.
Â
And some of it was BRUTAL! (In the best possible way.)
Â
Over a thousand data points. 40+ readers. The first two chapters of the book. All collected through a tool called HelpThisBook which lets readers highlight specific passages in a manuscript and tag each one with a color-coded reaction.
Â
What the data revealed is something no friend, no editor, and no amount of self-editing could have surfaced on its own.
Â
Here are seven (7) brutal lessons I’ve taken away (so far) from the process.
Â
And whether you’re writing a book, building a course, launching a product, or testing a keynote, I think you’ll find these apply far beyond the world of publishing.
Â
Let’s dive in…
1 | How to See Trends No Single Comment Can Reveal
HelpThisBook uses color-coded reactions. Each reader can highlight any passage in the manuscript and tag it with one of five sentiments:
Â
-
Red = “Love this.”
-
Green = “Useful.”
-
Yellow = “Thought.”
-
Purple = “Confusing.”
-
Blue = “Feels slow.”
Â
Each dot on the reactions bar represents one reader, one passage, one reaction.
Â
Individually, any single reaction is just one person’s opinion.
Â
But when you zoom out and look at the full reactions bar across an entire chapter, patterns start to emerge that no single piece of feedback could ever show you.
Â
A thick cluster of purple and blue on one passage means that multiple unrelated readers, independently, found it confusing and slow.
These are people who don’t know each other. They’ve never spoken. They’re reading at different times, in different places, with different backgrounds. And they all stumbled on the same thing.
Â
A thick cluster of red and green?
That’s gold.
Â
Multiple people, unprompted, independently loving the same line. That’s a passage you protect at all costs. You never cut it, no matter how many other edits you make.
* * *
The lesson: Whatever you’re building, you need a system that turns individual opinions into visible patterns.
Â
One person’s confusion is an opinion. Five people’s confusion is a signal. Eleven people’s confusion is a fact.
Â
Speaking of which…
2 | The Most Confusing Sentence in the Book Was Simply Missing a Comma
Here’s the sentence that 13 different readers flagged as “Confusing”:
Â
“What I found when I arrived, you already know. A house so frozen and still you could see your own breath.”
Â
Can you spot the problem?
Â
There’s a missing comma after the word “still.”
Â
Without it, the reader’s brain tries to parse “still you could see” as a continuous phrase. Like “still, you could see” but without the pause. The entire meaning of the sentence changes. The brain stalls. The reader has to go back and reread. This is a classic “Eats, Shoots, and Leaves” scenario.
Â
Thirteen people stubbed their toe on this line.
Â
I ended up rewriting the sentence entirely. The difference between a sentence that works and one that confuses 13 people can come down to a single piece of punctuation.
Â
And here’s the thing: I never would have caught this myself.
Â
(When you’re inside the bottle, you can’t read the label.)
Â
I wrote that sentence. I knew what it meant. So my brain filled in the missing comma every single time. I read past the stumble without even noticing it was there.
* * *
The lesson: You will never catch this kind of thing in your own work. This is why beta customers, beta readers, and beta testers matter before you lock anything in stone.
Â
It doesn’t matter how many times you’ve read your own sales page, your own email sequence, your own slide deck. You need outside eyes on it. Structured feedback. Real humans reading real words on a real page.
3 | One Line, Nine Strangers, 100% "Loved" It.
“If you are not analog by design, you will become digital by default.”
Â
Nine different readers independently highlighted that sentence and labeled it “Love this.”
Â
Here’s the thing:
Â
I actually wasn’t surprised by this one at all.
Â
That line has been stress-tested in over two dozen keynotes I’ve delivered over the past year and a half. Every time, it’s one of the lines that gets the most visible audience reaction.
Â
People reach for their phones to take a photo of the slide.
Â
(BTW – We explored the concept of using live keynotes to road-test your content before locking it in to a product in [Issue #084] 5 Forms of Feedback to Gather Before Your Next Launch.)
Â
But the beta reader data confirmed it in a way that keynote reactions alone couldn’t.
Â
Live audiences are responding to you. Your delivery, your energy, the room, the moment. Beta readers are responding to the words on the page.
Â
When a line lands in both formats, you know it’s real.
Â
The flip side is equally telling. Some lines I thought were brilliant received zero highlights. Not a single reaction.
Â
Of course, this kind of silence stings.
Â
But I’ve learned to approach this part of the book process as a scientist (not as an artist). After all, it’s all just data :-)
* * *
The lesson: Whether it’s a headline, a hook, a tagline, or a keynote closer, you want to find the lines that resonate unprompted. Not the ones people politely nod at. The ones that get spontaneously screenshotted and highlighted. Ideally, you’re stress-testing them in multiple formats before locking them in.
4 | The AI Tell I Didn't See Coming
One beta reader wrote something that hit me hard:
Â
“The number of em-dashes used is over the top. Aggravating this AI red flag in a book on the return to real.”
I asked Claude to give me an em-dash count.
Â
The manuscript had roughly 170 em-dashes across 10,800 words. That’s one every 64 words.
Â
Yikes.
Â
The irony was not lost on me. Here I am writing a book about authenticity. About returning to what’s human. And the punctuation was triggering internal AI-detection alarms in readers.
Â
This was good to know before this book goes to print.
Â
It didn’t matter that I wrote the manuscript myself. Stylistic patterns now carry the scent of the machine whether you used one or not.
Â
The fix: I cut em-dashes by 75%.
Â
I tested the removal of each one in my “read-aloud” part of the process. Could it be a comma? Great. A period? Even better. A new sentence? Fan-flipping-tastic.
Â
I only kept the em-dashes doing absolutely essential rhythmic work.
Â
(Side note: You may have noticed this very newsletter is em-dash-free. Several readers flagged the same pattern in my newsletter writing, and so this issue is my first attempt at going cold turkey. You’re welcome. But I’m hanging onto my ellipses. At least for now…)
* * *
The lesson: In 2026, your audience has developed pattern recognition for AI-generated text and punctuation tells. If your writing, your emails, or your sales copy carries those stylistic patterns, your readers will feel it even if they can’t quite name it. Something worth keeping in mind any time you’re creating something that needs to feel authentically you.
5 | A Great Opening Is Not the Same as the Right Opening
The book opened with a dramatic story about driving through a snowstorm in Texas during the 2021 grid collapse.
Â
Readers loved the story. They were gripped. One called it “heart-pounding.” Another said it was “visceral.”
Â
Separately, readers were also compelled by the book’s central thesis.
Â
BUT…
Â
The open story didn’t lead to the thesis.
Â
There was a problematic GAP between them.
Â
The hook grabbed the reader, and the thesis grabbed the reader, but the two weren’t connected.
Â
As one reader put it:
Â
“The personal story and its connection to the thesis feels like a stretch.”
Another:
Â
“I was gripped to hear the connection. But there is no connection.”
Attention and connection are two different things.
Â
A great opening grabs the reader.
Â
But the right opening grabs the reader and pulls them toward the argument. I had the first without the second.
Â
I’ve spent the last few days obsessing over this one point.
Â
The single most important fix I need to make in this introduction.
Â
I went from considering dropping the opening story altogether, to adding a missing piece of the story that I didn’t include in the first version, which I believe is the key to tying it all together.
Â
I’ll know for sure when the next round of beta readers goes through it in a few short days…
* * *
The lesson: This applies to everything. Sales pages. Keynotes. Pitch decks. Your opening hook and your core argument need to be the same thread, not two threads you try to tie together after the fact. If your audience has to wait for the connection, you’ve lost them before you’ve even begun.
6 | A Thousand Specific Data Points Will Beat "Yeah, It Was Great" Every Single Time.
When you ask a friend to read your manuscript and they say “I really liked it,” that tells you almost nothing.
Â
When 40+ strangers independently highlight over a thousand specific passages, tag each one with a sentiment, and leave over 600 written comments…
Â
That tells you everything.
Â
Here’s one of the more interesting things I noticed in the data:
Â
Some of the most complimentary comments came from readers who, according to the completion data, stopped reading partway through the Introduction.
Â
They highlighted a few things they loved, left warm notes, and quietly disappeared.
Â
Meanwhile, some of the most critical readers read every single word of both chapters. They pushed back. They challenged. They flagged what wasn’t working for them. And they read all the way to the end.
Â
Now, I don’t say this to vilify the positive feedback. Both groups are enormously valuable. The readers who tell you what’s working give you confidence to protect what’s strong. Without them, you might cut the wrong things.
Â
But the critical feedback? The people who tell you your baby is ugly?
Â
That’s the hardest feedback to swallow.
Â
(Trust me, I know.)
Â
But it may be the most valuable.
Â
Because the readers who push you the hardest are often the ones who care the most. They’re investing their time and energy in making your work better.
* * *
The lesson: Don’t confuse compliments with conviction. In your business, the hyper-responsive customer who sends you a long, detailed complaint is often more valuable than the one who says “looks great!” and never buys. Structure your feedback systems to capture depth of response, not just frequency of response. ASK Method 101.
7 | Why the Introduction Is Always the Hardest Chapter
Here’s what the data made painfully clear.
Â
The Chapter 1 edits?
Â
All polish. Tightening a sentence here, swapping a word there. The structure is sound. The pacing works. Zero readers flagged it as “Feels slow.”
Â
As one reader put it:
Â
“This chapter’s pacing is great. It gives enough space for the reader to think.”
Another said:
Â
“This chapter flows so much better than the introduction. You’ve done a great job of introducing ideas that ‘tend to live in different rooms,’ and weaving them together.”
The Introduction?
Â
That’s getting open heart surgery and is on the operating table as we speak.
Â
And here’s why:
Â
The introduction of any book (or any piece of content, for that matter) is the MOST important, because it has more jobs to do than any other section:
Â
-
It needs to grab the reader’s attention…
-
Establish the author’s credibility…
-
Present the central thesis…
-
Make the reader feel seen…
-
Preview the roadmap for what’s ahead…
-
And bridge smoothly into the first chapter…
Â
All while maintaining emotional momentum and voice consistency.
Â
That’s at least six distinct jobs in a single chapter. And if even one of them fails, the whole thing wobbles.
Â
My Introduction started at 6,300 words. The current version I’m working on is down to roughly 4,500.
Â
It’s getting a revised opening, a new structure, and a fundamental rethinking of how the reader enters the book.
Â
Squeezing all those jobs into a tighter, faster-moving chapter is the single hardest editorial challenge in the entire project.
Â
The Introduction was also the last thing I wrote.
Â
Chapter 1 was written weeks earlier. It was road-tested in keynotes. Refined through dozens of iterations. Pressure-tested in front of live audiences over and over again.
Â
The Introduction?
Â
Assembled under deadline pressure after everything else was done.
Â
And the data shows the difference.
* * *
The lesson: Before you launch anything, ask yourself: which part of your work has gotten the most reps in front of real people? And which piece has gotten the fewest? The piece with the fewest reps is almost certainly where the biggest problems are hiding.
Â
And if you’re building something with an “introduction” of any kind, whether it’s a book, a course, a webinar, or a sales page, know that the opening is always doing the most work AND deserves the most attention…
* * *
One last thing before I sign off…
Â
I want to take a moment to thank every single person who has participated in this beta reader program so far. In Round One – 40+ amazing people so far have volunteered their time, their attention, and their honest reactions to help make this book better.
Â
Some readers left dozens of highlights. A few left hundreds. Many wrote comments that fundamentally changed how I’m approaching the next version of the manuscript.
Â
We all stand on the shoulders of giants…
Â
And self-made is a myth.
Â
I’m deeply grateful for all the contributions made to this project so far, with lots more to come…
* * *
So what’s next?
Â
Well, I’ll be spending the next week with my family in Paris. Hitting all the spots you’d expect. The Eiffel Tower. Versailles. Notre Dame (finally reopened after the fire). The Louvre.
Â
I’m also holding a Private 1:1 Client VIP Day while we’re there.
Â
And in between all of it, you might just find me at a Parisian cafe with my laptop open, writing the next version of the Introduction. Because the open heart surgery doesn’t stop for croissants :-)
Â
Round 2 of Beta Readers is coming.
Â
More chapters. More data. More uncomfortable feedback.
Â
And I can’t wait.
Next stop, Paris.
Â
Have a GREAT rest of your weekend…
Â
Remember to hug the ones you love…
Â
And until next week,
Â
Ryan :-)
Â
P.S. If you signed up to be part of my beta reader program but haven’t yet had your number called, keep your eyes peeled…
Â
Next round will be opening up as soon as I get back stateside and finish these Version 2 edits…
Â
Stay tuned!