Latest
The Money Appeared the Week After the DisasterHow a Stranger Decides You Are Credible in Nine SecondsWhat You Have to Decide Before Anybody WritesWriting It Before You Need ItCross Training Covered Everything Except the Role That Mattered MostBehind the Book: The Woke VirusBehind the Book: Galactic InvasionBehind the Book: You Don’t Own Anything AnymoreWhat’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 RemindersFree BooksDarrell Stern: Stop Being Invisible, Become UnmissableJoe Rockey: Ghostwriting His BookHow 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 TributeI Don’t Post Bad ARC Reviews. I Send the Author a Note.AI Has Paid Off Outside Tech. Apollo Is Reading the Wrong Scoreboard.
The Writing King Your Ethical Ghostwriter. Your Story, Done Right.

The Money Appeared the Week After the Disaster

TL;DR: Resilience spending is nearly impossible to justify before an incident and nearly impossible to refuse afterward. I asked for a large amount of money to rebuild a computer room and it went through without an argument, because it came after the disaster. Knowing the window exists, and having the proposal already written, is the difference between getting the work funded and watching the moment pass.

Write the proposal now, before anything goes wrong, so it is ready when somebody finally asks what it would take.

Why is it hard to get funding for prevention?

Because the return on prevention is an event that does not happen.

Every other request competes with a number. A new system will save this much time. A new hire will handle this much work. Somebody can build a case and defend it.

Prevention has no such number. The honest version is that spending this money reduces the chance of something expensive, by an amount nobody can calculate, at a time nobody can predict.

Against a request with a demonstrable return, that argument loses. It should lose, most of the time, which is the uncomfortable part.

A rational organization systematically underfunds prevention until it has evidence, and evidence only arrives as damage.

What happened after our safety nets failed?

We had a morning where six independent protections failed one after another, and I have written about that day in detail elsewhere.

The aftermath is what this piece is about.

We decided the computer room needed rebuilding. Everything triple redundant, especially the wiring, and a move from copper to optical throughout.

That meant more storage cabinets, each holding around five hundred disks. Larger uninterruptible power supplies capable of carrying the whole room. Another generator. More controllers. More of everything.

I had no trouble at all pushing that through. The funding went straight through.

Why does money become available after an incident?

Because the abstract argument has become a concrete memory.

Before the disaster, I would have been asking people to spend a large sum against a risk they had never experienced. Reasonable people would have argued it down, deferred it, or approved a fraction.

Afterward, everyone in the room had lived through the alternative. The cost of not spending the money had stopped being theoretical and become a day they remembered.

That is a real shift in information rather than a failure of nerve. The organization learned something it could not have learned any other way, and it acted on what it learned.

What I took from it was a lesson about how to use a disaster as a lever to get funding, and I want to be plain that I think it is a legitimate lesson rather than a cynical one.

How long does the funding window stay open?

Months, not years, and it narrows the whole time.

Immediately after an incident, almost anything related to preventing a recurrence gets approved. A quarter later the urgency has faded and requests get examined normally. A year later the incident is a story people tell rather than a thing that shapes decisions.

Companies with no memory of a disaster and companies two years past one behave almost identically toward prevention spending.

Which means the request has to be ready. A proposal that takes six weeks to assemble is arriving as the window is closing, and a proposal that needs vendor quotes and a design phase may miss it entirely.

What should you have written before anything goes wrong?

The proposal you would want to hand over on the worst morning of your year.

It does not need to be long. What would we fix, what would it cost roughly, how long would it take, and what would it have prevented. Four questions, a page or two, updated when something material changes.

Writing it costs an afternoon and it has a second benefit that has nothing to do with funding. The act of writing forces you to identify what you consider fragile, which is a question most technology leaders have never sat down and answered explicitly.

Then it sits in a drawer. Most of the time it stays there and the afternoon was wasted, which is a fair description of insurance.

Can you create the window without a disaster?

Occasionally, and it works less well than people hope.

A near miss is the best available substitute, and it has to be surfaced deliberately. Something almost failed, here is what would have happened, here is what it would have cost. That conversation lands far harder while the near miss is recent.

An incident at a similar company sometimes works, particularly when it is public and the details are recognizable. That borrows somebody else’s evidence, and the effect fades faster because it happened to strangers.

Neither substitute is as strong as the real thing, and the strong version costs you an outage. Nobody should want it, and when it arrives, having the proposal ready is the only part of the situation you control.

Is it manipulative to ask for money after an outage?

No, and the discomfort with it is worth examining.

The engineering does not change based on when you ask. The systems that were fragile before the incident are the same systems, the fix is the same fix, and the cost is the same cost. Only the audience’s understanding has changed.

What would be manipulative is overstating the risk, inflating the scope while attention is high, or slipping unrelated work into a resilience proposal because nobody is scrutinizing it.

The line is easy to hold. Ask for what you would have asked for anyway. If you would not have proposed it a month earlier, do not propose it now.

Frequently Asked Questions

How do you calculate the cost of downtime?
Revenue per hour is the starting point, and the larger costs are usually elsewhere: staff time consumed by recovery, obligations you cannot meet, and customers who leave. A rough figure beats no figure, because the absence of a number is what makes prevention lose the argument.
What belongs in a resilience proposal?
What you would fix, a rough cost, a rough timeline, and what the fix would have prevented. Keep it to a page or two so it can be handed over immediately rather than assembled while attention is fading.
How often should the proposal be updated?
When something material changes, and at least once a year. A proposal describing systems you no longer run undermines the credibility of the rest of it.
Should you report near misses to leadership?
Yes, with what would have happened and what it would have cost. Near misses are the only evidence available that does not require an outage, and they are usually invisible unless somebody deliberately surfaces them.
What is triple redundancy?
Three independent paths for a function, so that two failures still leave one working. It is expensive and appropriate where a single failure would stop the business, and unnecessary almost everywhere else.
How do you know what to make redundant?
Trace what stops if each component fails. Anything whose failure halts the business is a candidate. Anything whose failure produces inconvenience usually is not, and treating everything as essential is how resilience budgets get spent on the wrong things.

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