On Becoming a Published Author

I am a published author.

I have typed that sentence three times now, and it still has the slightly unreal quality of describing yourself as an astronaut because you once sat in the front row of a planetarium show. The word "published" carries a great deal of historical weight: garret apartments, rejection letters, editorial lunches, the long suffering of the unrecognised genius. None of that happened. What happened instead was considerably stranger, considerably faster, and considerably more likely to involve falling asleep in someone else's kitchen in France.

But I am getting ahead of myself. Let me describe how you write seven books.

 

The Pipeline

The first thing you learn when you approach book-writing as a technology problem rather than a literary one is that the traditional model is architecturally unsound. Write book one. Finish it. Publish it. Start book two. Repeat. This produces books, but it produces them slowly, and slowly is the enemy of a Kindle series, where the algorithm rewards frequent publication with the enthusiasm of a labrador that has discovered the biscuit tin.

The insight that changed everything was deceptively simple: all the books in a series are structurally identical. If you have designed the architecture correctly, every book has the same skeleton. Same number of parts, same number of chapters, same internal framework per chapter. What differs is the subject matter.

Which means the correct unit of production is not "book." It is "chapter section, across all books simultaneously."

Instead of writing Book 1 from front to back before touching Book 2, you write the opening paradox of Chapter 1 across all four books in the same session. Then the translation framework across all four books. Then the 7-day lab section. You are not writing four books sequentially; you are weaving four books in parallel, and the result is that tone, pacing, and cross-references between the books stay coherent because they were created coherently, not retrofitted.

This is not how most people think about writing. It requires bending the brain into an unfamiliar shape, the literary equivalent of patting your head while rubbing your stomach, except that both hands are typing and neither of them is entirely sure which book it is currently in. Once you make the shift, the books do not feel like four separate projects. They feel like a single multi-threaded project, which is a framing that will make complete sense to anyone who has spent time as a software engineer and none whatsoever to anyone who has not.

The other component of the pipeline was AI assistance, specifically Claude, which I use for essentially everything at this point. Not to write the books for me. To be the intelligence at the other end of the production line: holding the structural rules, maintaining the style guide, flagging when a cross-reference did not match the planned topology, and producing draft sections that I could review, edit, and approve at speed rather than composing from blank page. The distinction matters. A blank page is an invitation to procrastinate. A draft that is eighty percent right is an invitation to argue, which is something I am considerably better at and considerably faster doing.

 

Four Books in a Weekend

The series is called the 30-Day Micro-Pivot Playbooks. The concept emerged from a fairly systematic analysis of what actually sells on Kindle for first-time non-fiction authors: series, not standalones; urgent, specific problems, not broad guidance; a readership that has a burning question and wants an actionable answer, not a meditation on the question's philosophical underpinnings.

The target audience is mid-career professionals who are, in the memorable phrasing of approximately every management consultant ever, "at an inflection point." They are burnout, underpaid, or simply bored, and they want a 30-day roadmap to somewhere different. The books deliver this with what I can only describe as cheerful ruthlessness: here is what you need to do, here is why you are currently not doing it, here is a lab exercise to force you to actually try, and here, on the way out, is a pointer to the three other books in this series that you will also need.

Books one through four took a weekend. The 30-Day Learning Pivot (teacher to corporate instructional designer), the 30-Day Clinical Pivot (healthcare worker to health-tech consultant), the 30-Day Workflow Pivot (solopreneur automation), and the 30-Day Financial Pivot (how to stop using consumerism as a coping mechanism for burnout). Four books, four subtitles each more alarming than the last, one weekend, one very large amount of coffee.

The subtitles are where I permitted myself to enjoy the process rather than merely execute it. "Or, How to Supervise Adult Learners Who Won't Eat Glue." "Or, How to Fix Healthcare Systems from a Safe Distance." "Or, How to Make Zapier Do Everything Except Make the Tea." These are not the subtitles of a person approaching authorship with solemnity. They are the subtitles of a person who has read Douglas Adams approximately once too many times and has decided that this is, in fact, exactly the right number of times.

 

The Fifth Instalment of the Trilogy

Douglas Adams wrote five Hitchhiker's Guide books and described the collection as "a trilogy in five parts." This is funnier than anything I have written in this post, and I have made peace with that.

Book five, the 30-Day Developer Pivot, is subtitled "Or, How to Become the Person the AI Reports To." It arrived separately from the first four, not because the pipeline stalled but because it required a different kind of thinking. The first four books are about people leaving one profession and entering another. Book five is about a profession that is not leaving so much as being comprehensively reorganised around it, and the question of how a developer positions themselves on the right side of that reorganisation is not one that has a comfortable answer yet.

It is also, if I am honest, the most personally interesting of the seven. I have spent thirty years at the intersection of technology and the people who use it. The question of what skilled technical work looks like when AI can produce competent code on demand is one I think about most days, and having an excuse to write about it at length, with full use of the Douglas Adams stylistic toolkit, was something I enjoyed more than I had expected to.

It is the fifth instalment of the trilogy. I stand by this.

 

The Kitchen in France

Books six and seven have a different origin story.

There is a particular quality of tiredness that arrives at a family gathering in a foreign country when you have been talking to people in a combination of languages for several hours and the kitchen is warm and there is nothing specifically requiring your attention. It is not the dramatic exhaustion of overwork. It is the quiet, cumulative exhaustion of being a functioning adult in a complex social situation, and it has a predictable outcome.

I fell asleep in the kitchen.

I am told this was not especially alarming to anyone present, which is either a testament to the relaxed atmosphere of the gathering or to how often it happens, and I am choosing not to investigate which. What matters for our purposes is what happened when I woke up: a clear head, a quiet house, and approximately three hours before anyone would require anything of me.

Books six and seven were written in that window. The 30-Day Writing Pivot ("Or, How to Make Software Sound Like It Was Designed by Humans (Which It Wasn't)"), aimed at the strange and underserviced market of people who can write but cannot make their writing sound like it came from a human organisation rather than a specification document. And the 30-Day Management Pivot ("Or, How to Attend the Same Meetings but Invoice Them"), which is targeted at the senior manager who has realised that their value is in judgment and relationships rather than presence in a building, and that fractional executive work exists and is paid accordingly.

Two books, one post-nap window, one family party that will henceforth be referred to in my biography as "the France sessions," assuming I ever have a biography, which at current sales velocity is approximately as likely as me becoming an astronaut.

 

The Part Where the JK Rowling Money Arrives

I should address the financial dimension of this, because intellectual honesty demands it and because it is funnier than pretending otherwise.

The market research was sound. Kindle self-publishing does produce real income for the right series, with the right launch strategy, targeting the right readership with the right organic search intent. The analysis underpinning the series was not invented; it reflects how first-time authors actually make money on the platform, and the structural decisions (series format, templated production, cross-promotion between volumes, price point calibrated for review velocity) were made with a clear understanding of what the data said.

One copy has been sold. It was purchased by a friend, who described the price as "cheaper than a large latte," which is technically accurate and spiritually deflating in a way that no benchmark data quite prepared me for.

This is not a failure of the strategy. The books are written, formatted, and published. The launch campaign is a separate project and has not yet been executed with the same focused energy as the production phase. This is, if I am being generous to myself, a sequencing issue. If I am being accurate, it is the classic pattern of a person who finds the making of things considerably more engaging than the selling of them, and who has now produced seven books' worth of evidence in support of this assessment.

The JK Rowling income has not arrived. I have not spent it. I have, however, spent a weekend, a separate afternoon, and a post-nap window in someone else's kitchen in France thinking about things I would not otherwise have thought about, writing in a voice I did not previously know I owned, and building something that did not exist before I sat down. Seven books. Seven sets of subtitles that make me laugh when I read them back. A framework for helping people think differently about their careers that is, I believe, genuinely useful even at the price of a large latte.

 

What It Actually Did to the Brain

The part I did not anticipate was the cognitive effect of the process itself.

I have spent thirty years thinking about technology: how it works, how it fails, how organisations adopt it, how it changes what is possible. This is a particular mode of thinking, and it is deeply grooved. The parallel-production book pipeline forced a different mode: not "what is true about this technology" but "what does this reader need to hear, in what order, at what level of abstraction, with what emotional register." These are not the same question. The second one is harder, in the specific way that communication is always harder than comprehension.

I also discovered, somewhere around the third book's second chapter, that I find it significantly easier to write in a voice that is not entirely serious. The Douglas Adams approach to difficult subjects, treating professional catastrophe with the mild concern one reserves for over-steeped Earl Grey, turns out to be not merely a stylistic affectation but a genuinely useful frame for thinking. If you can describe a problem with precision and wit simultaneously, you have understood it better than if you can only describe it earnestly.

The books may or may not generate the income the market research suggested was available. What they definitely generated was a new way of thinking about how I communicate, seven mildly alarming subtitles, and the knowledge that if you fall asleep at a family party in France, you should probably check that nobody needs you before you open a laptop. Nobody did. I checked.

The author photo, should anyone require one, will be taken at a time when I have had more sleep.

All Posts