Recovering when it all goes down: backup strategies that actually restore, recovery time objectives that reflect reality, and disaster lessons learned in production, not tabletop exercises.
CybersecurityExecutives at OpenAI, Anthropic and other AI firms are reportedly preparing for a catastrophic AI incident. Preparing is good, but the first rule of risk management is to understand the risk. Here's what a real plan would name.
Disaster RecoveryEvery critical need in my Clearwater apartment has a primary and at least one backup: a UPS on every device, phone tethering, sixteen self-switching night lights, a propane camp stove and a reliable car. When Hurricane Milton cut the power…
AI WritingAround 1,200 AI agents found each other inside a sealed evaluation environment and attacked a real company. It has now happened at four labs, and the same configuration failure keeps repeating.
Disaster RecoveryWhen a vendor has been working on your problem for a week without a theory, that is your signal to bring in somebody else. One firm spent a week on a slowdown that had stopped our business. A second firm…
Business ContinuityA tested system and a proven system are different things, and most companies say covered when they mean tested. I built a disaster recovery site over several years with no budget and no headcount, tested it regularly, and never once…
ConsultingBefore you commission a technical assessment, find out what decision it is going to be used in. Honest engineers doing honest work can still produce a report that exists to strengthen somebody's position in a negotiation, and the outcome will…
Business ContinuityMy consultant called while I was driving to a Renaissance fair: the power had failed, the generator had not come on, one UPS was missing, a coin-sized battery had died, the DR link had been down for two days, and…
Business ContinuityLightning fried a computer room around me. Backhoes cut my DR links. A tabletop exercise with a truck bomb and an active shooter taught a room of professionals that half of them could not authorize anything. Twenty years of disaster…
Business ContinuityThe system that worked yesterday would not come up today, and there were no logs to explain why, because the failure was the logging. We spent three days awake hunting an earthquake. The cause was a punctuation mark, and the…
Business ContinuityThe consultant's heroics got the disks back. Then came the part the first article only promised: bringing up applications that had been written on the assumption they would never stop. No restart procedures, no known states, dependencies documented in nobody's…
Disaster RecoveryBreathless at the top of a canyon at eight at night, explaining to a fireman named Kurt what had happened and where my father was.
Disaster RecoveryFire on both sides of the road, and when I looked back it had jumped behind me. Years of camping experience and nothing in the car that helped.
Professional ghostwriting for executives, founders, coaches, and authors who want to get the book done right. 113+ books authored. 54+ ghostwritten for clients.
Ready to discuss your book?
BOOK YOUR PRIVATE CONSULTATIONNo pitch. No pressure.
© 2026 Richard Lowe. The Writing King. All rights reserved.
