Latest
What You Have to Decide Before Anybody WritesWriting It Before You Need ItCross Training Covered Everything Except the Role That Mattered MostBehind the Book: You Don’t Own Anything AnymoreBehind the Book: The Woke VirusBehind the Book: Galactic InvasionWhat’s New at The Writing King: Week of November 8, 2026Alexander Zhidkov: Decision MakingJessi Szurek: Expand Your RangeYou Don’t Own Anything AnymoreThe Budget Decided How My Department Was ShapedWhy Your Competitor’s Book Is Working and Yours Would NotWhy Are These Guys Smiling? A Business Book That Became a Wrestling MemoirPangram Wants to Decide Who Gets PublishedWhat You Have Enough Material For Right NowWhen a Book Is the Wrong ToolThe Woke VirusGalactic InvasionChatGPT Turns Four: From a Free Research Preview to GPT-6What’s New at The Writing King: Week of November 1, 2026Diwali: The Festival of Lights and the Story Behind the LampsHow Much Water and Power Does Heavy AI Use Take? I Ran My Own NumbersBad Boys: Ride or Die (2024)Vesuvius Day: The Teenager Who Wrote Down Pompeii’s Last DayAnti-Communism Week: Remembering the Writers Communism SilencedVoyager 1 One Light-Day: Fifty Years to Travel One Day of LightVellum Added an Optional AI Feature. A Pile-On Killed It in a Day.Are AI Subscriptions Losing Money? The Gym Membership Math Says NoAI Terms Every Writer Should Know, and Why Each One MattersWorking While Sick: What 24/7 On Call Cost MeHe Banned AI From His Writing Group. His Own Cover Got Called AI Slop.Who Writes the Fake Fan Mail Authors Get? Inside the Scam CompoundsSMS Appointment RemindersJoe Rockey: Ghostwriting His BookDarrell Stern: Stop Being Invisible, Become UnmissableFree BooksHow to Turn Your Expertise Into a Book People Want to Read | The Expert MethodWhat’s New at The Writing King: Week of October 25, 2026Challenger Remembrance Day: The Engineer Who Wouldn’t SignJoel Salomon: The Truth About MoneyReddit Is Putting Up a Login Wall. Wikipedia Won’t Be Far Behind.Victoria Chemko: The Body Is the First TechnologySir Patrick Stewart: A TributeA Year in the Bank: ADHD, Face Blindness and the Freedom to Walk Out | The Impossible Puzzles Show, Episode 326A Yale Economist Says We Won’t Be Missed. He Forgot the Bread Line.Walter Koenig: A TributeAI Has Paid Off Outside Tech. Apollo Is Reading the Wrong Scoreboard.I Don’t Post Bad ARC Reviews. I Send the Author a Note.The Little Red Book of Stuff That Works!Your Kids Are Your Own Fault
The Writing King Your Ethical Ghostwriter. Your Story, Done Right.

What Ghostwriting Three Transformation Books Taught Me

TL;DR: I ghostwrote three digital transformation books for executives, and it taught me something running transformations did not. Each executive did it completely differently, at a scale far bigger than mine, Fortune 500 budgets, whole departments, agile and scrum where I used waterfall. Each had a methodology they wanted captured. Writing those books meant deep interviews and real understanding of what they meant. The lesson: there’s no one way to transform, and the best books preserve the specific way one leader did it.

I ran digital transformations myself for two decades. Then I ghostwrote three books about digital transformation for other executives, and that taught me something running my own never did. There’s no single right way to do this. There are as many ways as there are leaders, and the good ones each have a method worth preserving.

I ghostwrite books for technology leaders, and these three projects hardened my opinion of the firms that sell transformation as a packaged product. I came away irritated with anyone who hands a company a method built somewhere else, and with a lot more respect for executives who built their own the hard way.

What surprised me most was how differently each of them worked. All three wanted a book that described their methodology, their particular approach to transformation. And in all three cases, those approaches were different from each other and from how I’d done it.

Each had real things to say. Each had built their method from their own scars. None of them was wrong, and none of them matched.

That alone was a lesson. The consultant-speak version of digital transformation pretends there’s one structure everyone should follow, one neat methodology you can buy and apply. The reality, from three people who did it at a high level, is that the method is personal and shaped by the company, the constraints, the leader.

One led with culture. One led with metrics. One led with a relentless focus on process. All three succeeded, because each method fit the person running it and the organization they were running it in.

I ghostwrote three digital transformation books. All three executives had a different method. None was wrong. There’s no one way to do this, whatever the consultants say.
Share on X

This is the same truth I reached from my own experience in people, process, technology: the order and the principles hold, but the specific method is always shaped by the people and the place. Anyone selling a one-size-fits-all transformation structure is selling the consulting equivalent of the security theater I describe elsewhere, something that looks authoritative and doesn’t survive contact with a real organization.

These executives worked at a scale beyond what I’d run.

I did transformations at a national retailer. That was considerable. They were working at Fortune 500 scale, with bigger budgets and the goal of transforming far more of their organization than I ever had to. The principles didn’t change at that scale, but the stakes and the complexity did. A misstep that would have been a bad week at my scale could be a catastrophe at theirs, so their judgment about sequencing and risk was carefully earned.

They also worked under more stringent standards and methods than we used.

My shop tended to run waterfall, the older sequential way. Plan everything, build it, ship it. They were using agile and scrum, the iterative modern approach where work happens in short cycles with constant adjustment. Seeing how those methods played out at that scale, through the eyes of the people running them, expanded my own understanding considerably. Neither approach is universally right.

Waterfall suited the predictable, infrastructure-heavy work I did, and agile suited their fast-moving, large-team environments. People who call one of them obsolete are wrong. A company that forces a method onto work it doesn’t fit pays for that in missed dates and worn-out teams, and the consultant who sold the method is long gone by the time the bill comes due.

How my transformations compared with the executives I wrote for
Factor My transformations The executives’ transformations
Organization A national retailer Fortune 500 scale
Budget and scope Considerable, but smaller Bigger budgets, far more of the organization transformed
Method Waterfall: plan everything, build it, ship it Agile and scrum: short cycles, constant adjustment
Work it suited Predictable, infrastructure-heavy work Fast-moving, large-team environments
Cost of a misstep A bad week Could be a catastrophe
Principles Same principles Same principles, more stakes and complexity

I’d be wary of any writer who tells a technology executive the subject matter doesn’t matter on a methodology book.

Ghostwriting those books wasn’t a matter of taking dictation. It required a lot of interviews and a lot of real effort to understand what each executive was talking about and what they meant. Even though I’d done transformations myself, theirs were bigger and different, and I had to learn each one deeply enough to write it in their voice, accurately. One of them, a digital transformation book for a client, was a bitch. I’ve done digital transformation, and I led one myself at a retailer, but that book was still very complicated. It took work, and boy, did we have fun with it.

That’s the main work of ghostwriting a technical book, and the typing is the smaller part of it. The understanding is the job. You have to grasp the methodology well enough that the expert reads the chapter and thinks yes, that’s exactly what I meant, better than I could have said it.

You can’t fake that. Having run transformations myself and being able to write made these projects work. A pure writer would have missed the technical substance.

A pure technologist couldn’t have shaped it into a book either. I’d be wary of any writer who tells a technology executive the subject matter doesn’t matter on a methodology book. The executive’s peers will read it, and they’ll spot a chapter that gets the vocabulary right and the method wrong within a page or two. The writer’s name isn’t on the cover. The executive’s is, and they’re the one who pays for it in credibility.

My take

There’s no single right way to transform a company, and anyone selling one is selling a slogan. Waterfall fit my infrastructure work. Agile and scrum fit the big, fast teams I wrote for. A transformation book is worth reading when it captures one leader’s specific method accurately enough that peers recognize it. That takes a writer who understands the subject. If yours shrugs at the technical substance, find another, because your name’s the one on the cover.

Ghostwriting a technical book means understanding the method well enough that the expert reads it and thinks: yes, that’s exactly what I meant.
Share on X

What did three transformation books have in common?

What those three books captured would otherwise have been lost: the hard-won method of one leader who had transformed an organization, in their words and at their scale.

A good transformation book preserves how one person did it, including the parts that don’t fit the standard structure, and those are usually the most valuable parts. The pile of abstract models is high enough already. Too much of this knowledge walks out the door. An executive retires or moves on, and a method that took years of mistakes to build leaves with them because nobody sat down and got it on paper. The company loses it, and so does everyone who could have learned from it.

That’s exactly the kind of book worth writing, and exactly the kind I’m built to write, having both run transformations and written the books about them. You can see how I work on the technology ghostwriting page.

Frequently Asked Questions

Is there one right way to transform an organization?

That there’s no single right way to transform an organization. I ghostwrote three digital transformation books, and all three executives had completely different methods, one led with culture, one with metrics, one with process, and all three succeeded. The consultant version pretends there’s one structure. The method is personal and shaped by the specific company and leader.

How is a Fortune 500 digital transformation different?

Bigger budgets, broader scope, and higher stakes. The principles don’t change at that scale, but the complexity and the cost of a misstep do. The executives I wrote for transformed far more of their organizations than I did, and they used agile and scrum where my shop tended toward waterfall. The method follows the situation.

What is the difference between waterfall and agile?

Waterfall is the older, sequential approach: plan the whole project, then build it, then ship it. Agile and scrum are iterative, with work done in short cycles and constant adjustment. Neither is universally right. Waterfall suited the predictable, infrastructure-heavy work I did; agile suited the fast-moving, large-team environments of the executives I wrote for.

What is the core work of ghostwriting a technical book?

Understanding, before typing. You have to grasp the methodology deeply enough that the expert reads the chapter and thinks that’s exactly what I meant. It takes many interviews and real effort to understand what the person means. The combination of having run transformations and being able to write makes it work; a pure writer misses the substance.

What does a good transformation book preserve?

I think what a good transformation book preserves is the specific, hard-won method of a leader who transformed an organization, in their own words and at their real scale. It captures the parts that don’t fit the standard consulting structures, and those are usually the most valuable parts. I write these books to get down what an executive learned before it scatters, before they move on and the knowledge leaves with them. That’s what makes the book worth writing in the first place.

Who ghostwrites books on digital transformation?

Yes. I led transformations myself for two decades and ghostwrote three for executives at larger scale. That combination, having done it and having written others’ versions, is rare and is exactly what a technical book needs. You can see how I work on the technology ghostwriting page.

How do I start a transformation book?
With the audience and argument. The Book Discovery Intensive settles both before a chapter is written.

From the author
The Ghostwriting Advantage by Richard Lowe

The Ghostwriting Advantage
Executives who want a transformation book should know how the process works before they sign. The Ghostwriting Advantage explains how to get your book written for you by a professional.

Sources

About the Author
Richard Lowe, professional ghostwriter

Richard Lowe is a professional ghostwriter and author with 113+ books authored and 54+ ghostwritten. Before writing full time he spent 33 years in enterprise technology, including 20 years as Director of Computer Operations and Technical Services at Trader Joe's. He writes nonfiction, fiction and memoir, and works with executives and experts on books that build authority.

More about Richard Lowe →

Disclaimer

The views and opinions expressed in this blog post are solely those of Richard Lowe and are based on personal experience and research. This content is for informational purposes only and should not be construed as professional legal, financial, accounting, or business advice. Always consult with qualified professionals before making important business or legal decisions. Richard Lowe is not a lawyer, accountant, or licensed professional advisor, and this content does not establish any professional relationship.

0 comments

No comments yet. Yours can be the first.

Was this useful?

Leave a comment