Even Penguins Need to Surface
Yesterday did not go well.
Not one big disaster — a series of small ones that stacked up until I closed the laptop and walked away. Last night was a chance to come up for air. A penguin can hold its breath for a remarkably long time, but eventually it has to surface. And when it does, it isn't just breathing. It's looking around, getting its bearings, checking it's still heading somewhere worth going.
So here's what I saw when I surfaced.
What went wrong
Scope creep got me, and I of all people should have seen it coming. "A couple of simple images" sounded quick and they would add value — but they're not core. One of them (a moon, of all things) ate an evening's energy on its own, and then every image wanted a fight about formatting and position. They're cut. They can come back later if time allows.
I was also fighting three book formats at once — paperback, Kindle and Apple — each with its own quirks. The Apple EPUB in particular was swallowing hours over what looked like simple page breaks, and the honest fix was learning a whole new editing tool. On top of writing and editing a book, that's a tool too far.
And underneath it all: I was experimenting too much. New tools, new workflows, new formats — all layered on top of the genuinely hard job, which is making the content good enough. Meanwhile the one process that was working — reviewing Sam's feedback in Word — kept getting lost in the noise.
The course correction
In the book I talk about the iron triangle: resource, quality and speed. You can't hold all three rigid. My resource is fixed — there's no holiday left to throw at this. So the corner that has to be solid is quality, and the corner that gives is time.
Here's the new heading:
One format first. The paperback, built in Word, published to PDF. When the content is locked, Kindle follows. Apple is a future consideration, not a current battle.
One master copy. The book moves to Word. I edit there, with quality-control help from CoPilot, and Sam's feedback flows in the way it already works. The old files get archived as backup — not deleted, just out of the swimming lane.
Fewer roles per teammate. My AI editor had accumulated too many jobs, and confusion crept in — edits happening when I'd asked for none. That's not the tool's failure so much as mine: I'd built a role no one could hold clearly. Claude steps back from editing the book and focuses where it genuinely helps — project management, publishing advice, running the website and blog, and catching ideas before they escape.
Less experimenting. The clever stuff can wait. The words can't.
The point
None of this is a setback story, really. It's the book's own argument, tested on its author. Pressure narrows your vision; surfacing restores it. The plan you correct is worth more than the plan you defend.
One day on
I can already tell you the correction was the right one, because today went the way yesterday didn't. There was setup cost in moving to Word — there always is — but it started paying back almost immediately.
And it taught me something about myself I hadn't quite put into words. Content-driven writing only takes me so far. I need to see the structure to write inside it. Give me a document with visible bones — headings, sections, a shape I can point at — and I push back, I tighten, I deliver what I believe are clear and useful messages. Take that scaffolding away and I spiral: ideas scatter in every direction, each one fine on its own, but with connections only I can see. What some people would kindly call rambling.
That's not a flaw to apologise for. It's just how my particular head works, and the whole book is about building the conditions each person needs to do their best work rather than forcing everyone into the same posture. Turns out the author needed to take his own advice. The visible structure of a Word document is, for me, a thinking tool — not just a formatting one.
Back under the water now. But breathing better, and swimming in a straighter line.
← All posts