When an executive searches for a ghostwriter who understands digital transformation, one question sits underneath the search.
Will I have to teach this writer my field before they can write my book? With me the answer is no, and I’d be embarrassed to take the work if it were yes. A transformation leader’s time is too valuable to spend tutoring a writer on cutover weekends and change resistance. So I’ll give you the evidence the way I tell my own clients to give it: specifics first, claims after.
Which digital transformation books has Richard Lowe ghostwritten?
I have ghostwritten three books squarely on digital transformation, and between them they cover the range the subject demands.
I built one on people-process-technology, the classic frame, which I could write with conviction because my own transformation scars validate it. I built one around the client’s proprietary methodology, a different craft entirely: make an unfamiliar structure feel inevitable without flattening what makes it the author’s own. The third took the pure executive vantage, transformation as a leadership problem instead of an IT program.
The outcomes are the part a prospective author should weigh. One of those authors uses his book as the credential that pitches his consulting clients, the proof of authority his whole LinkedIn presence rests on.
Another rode his onto the speaking circuit. Past the transformation trio, my technical ghostwriting covers IoT, the metaverse, AR/VR, and AI, and my own catalog of 113+ authored books includes deep technical work under my name. The pattern across all of them is the one I detailed in the companion article: aimed above the technology, armored with it underneath.
Why does field time matter for a digital transformation ghostwriter?
What qualifies me more than the books is that when a client describes his transformation, I recognize it from the inside.
Ghostwriters who take on a transformation book after a weekend of reading are gambling with the author’s money.
I spent decades in enterprise technology, including infrastructure leadership at a major national retailer through two full transformations. One moved accounting, HR, and payroll off paper. The other was a platform migration that nearly rolled back on cutover weekend, and six months of specialist work made it whole. I owned disaster recovery through both. I fought the paper resistance and watched retraining dissolve it. I found the server under the desk.
That history changes the mechanics in ways a client feels immediately.
Interviews go faster, because nothing has to be explained twice. Questions go deeper, because I know which parts of a transformation story executives skip and readers want: the barely tolerable weeks, the political fights, the costs that showed up after go-live. And the manuscript never makes the errors practitioners spot instantly and hold against an author, because the writer has stood in the rooms the book describes.
Ghostwriters who take on a transformation book after a weekend of reading are gambling with the author’s money. The author ends up paying twice, once to teach the writer the field and again when a CIO reads chapter three, hits a term used wrong, and stops trusting everything after it. That CIO was exactly the reader the book was written to win.
Your best book material is in the things that went wrong.Share on X
What are transformation book interviews like?
Clients are sometimes surprised by what I ask, because the questions come from inside the experience instead of out of a research binder. I don’t ask “what’s your transformation methodology.” The methodology is in your slide decks, and I’ll have read them.
I ask where the near-rollback was. What you improvised at two in the morning. Which department kept its paper in a drawer for a year. What came up after go-live that the budget never saw. I know those things exist in every transformation, because I lived each one of them.
The answers become the chapters readers remember. Executives keep discovering mid-interview that their best material is what they’d written off as “things that went wrong.”
The interviews also protect you. Transformation stories implicate vendors, colleagues, and employers. Part of my job is knowing which specifics carry the lesson and which only carry liability. It’s the same discretion protocol I apply to security material, where the stakes of over-sharing run higher still. Your book should make you the authority on the transformation instead of the defendant in its retelling.
Vendor names are where I push back hardest. Naming the integrator that botched your cutover feels satisfying in a draft, and it’s the kind of passage that brings a letter from their lawyers. Readers learn the same lesson from “the integrator” as they would from the company’s name, and you keep a reference you might need someday.
My take
Insist that your writer has lived a transformation. A ghostwriter who learned the field over a weekend gets one term wrong in chapter three, and the CIO you wrote the book to win stops trusting the rest. Your best material is what you wrote off as things that went wrong, the near-rollback, the improvising at two in the morning, the paper in the drawer. Tell those stories. Call the integrator the integrator and skip the letter from their lawyers.
What does your transformation book require?
Three things, and they mirror what I demand of my own articles. An audience decision made before the outline: who funds, promotes, or hires you, and what they must believe on the last page. Stories with their specifics managed, anonymized where discretion demands it and vivid where the lesson is, because readers and AI answer engines both cite the concrete and skip the generic. And a writer who doesn’t need the field explained. A transformation book written from transcription reads like transcription, and your readers include people who were there.
If that’s the book you’ve been meaning to write, it starts with a conversation instead of a manuscript. What you did. What it cost. What you’d tell the executive about to attempt it. I’ve been on both sides of that conversation, and it’s a good one.
Too many transformation leaders retire with the only candid account of the work sitting in their heads, while the vendor case studies and conference slides keep telling the clean version. I think that’s a loss for every executive who has to attempt the same thing next, and it’s why I’d push you to write the book now, while you still remember what the two a.m. calls sounded like.
When you’re ready, the digital transformation ghostwriting process lays out how the engagement runs, and the ghostwriting service overview covers structure and investment. The first conversation costs nothing except the realization of how much book you’re already carrying.
For more from this series, see The Digital Transformation Hub: real transformations, lived from the inside, decades before the term existed.
Field time is one thing to look for in a ghostwriter. The Ghostwriting Advantage covers the rest of how to get your book written for you, drawn from 54+ books I have ghostwritten.
