Skip to the stories
Windows & PowerShell

Getting Budget and Buy-In for Enterprise Resilience Plans

  • Joao-Pierre S. Ruth
  • 872 views

Equifax's Jeremy Koppen and Digital Commerce Bank's Paul Twigg explain how CIOs can win over CFOs and operations leaders for resilience strategies.

Getting Budget and Buy-In for Enterprise Resilience Plans

Resilience plans rarely fail because the technology is wrong. They stall because the person holding the budget can't see what they're paying for, and the person running operations is worried about what a cutover will do to sales. That's the tension at the centre of the latest InformationWeek Podcast, where Jeremy Koppen, executive vice president and CISO at Equifax, and Paul Twigg, CTO at Digital Commerce Bank, lay out how they get stakeholders to say yes.

Start with the cost question, because it's coming anyway

Any plan to reinforce software and IT systems raises two questions almost immediately. The first is how much it will take from the budget. The second is what it will take from everyone else's time. Finance wants a number and a rationale. Operations wants to know about training, and about the downtime needed to switch software or hardware without disrupting the business.

Here's the thing: those concerns are legitimate, and they're easier to address before the proposal is on the table than after. Tech leaders who walk into a budget meeting with a resilience strategy and no answer on disruption tend to find the conversation stuck on that one gap. The panel's central argument is that the job starts with anticipating these objections, not reacting to them.

Find the stakeholders before you need their signatures

The podcast spends time on how Koppen and Twigg identify the people who need to be in the first conversation. That's a practical question. A resilience plan touches finance, operations, security, and business units that own revenue-generating systems, and not all of them will carry the same weight in the final decision.

My read is that the stakeholder map matters more than the slide deck. If you only bring in the people who approve spending, you may discover late that operations has a veto in practice, because it controls the change windows. Mapping who feels the downtime, who signs off on training time, and who answers to the board tends to shape the pitch more than any technical detail does.

Resilience ownership has moved

The conversation also covers how responsibility for resilience has changed over time. In many organisations, continuity planning once sat largely with IT or with a narrow risk function. That arrangement makes less sense when a single outage can hit customer transactions, reporting, and partner systems at once. Responsibility tends to spread across the executive team, and the CIO or CISO ends up coordinating rather than owning every decision.

That shift changes the CIO's role in the room. Instead of defending a technical plan, the job becomes showing how the plan protects the things each executive already cares about. It's a different skill set, and it's one many technology leaders are still building.

How often the plan needs to change

Koppen and Twigg also address how frequently resilience plans should be updated. A plan written once and filed away goes stale quickly, especially as systems, vendors, and dependencies change. Teams in this position typically set a review cadence tied to real events, such as major platform changes, new services going live, or lessons from an incident, rather than relying on a calendar date alone.

That matters for the budget conversation, too. A plan that gets revisited regularly is easier to fund in increments than one that arrives as a large, one-off request every few years.

Adjusting the C-suite's own assumptions

The final theme is how C-suite tech leaders might need to adjust their own perceptions. That can mean recognising that a resilience investment won't look like a product win, or accepting that a plan which never gets tested isn't really a plan. It can also mean accepting that some stakeholders will judge the strategy by different criteria than the technology team does.

And yet, this is where many CIOs and CTOs gain the most ground. Treating finance and operations as partners in the risk decision, rather than as obstacles to get past, changes how the proposal lands.

A tabletop exercise with kobolds and goblins

After the panel, Twigg and Koppen took part in the Questionable Ideas tabletop exercise. They worked together as interim executives at a fictional company, where kobolds, gremlins, and goblins created considerable trouble for its resilience strategy. The exercise is a light-hearted format, but the underlying method is a serious one.

Tabletop exercises let a leadership team test decisions, communications, and dependencies without touching production systems. They surface the gaps that a slide deck hides: who makes the call at 2 a.m., which system nobody remembered was a dependency, and where the plan assumes a vendor will respond in a time frame the contract never promised. Running one before a budget discussion gives tech leaders concrete examples to bring to the table.

What to take into your next planning cycle

If you're preparing a resilience proposal, the podcast points to a clear sequence. Anticipate the cost and disruption questions. Map the stakeholders who will feel the impact. Be explicit about who owns which part of resilience. Set a review cadence tied to real change. And test the plan in a tabletop exercise before you ask for money to fund it.

The episode is part of the Enterprise Resilience in the AI Era series, which looks at how technology executives can set threat defence policies and maintain business continuity as digital services grow more interconnected. Expect the stakeholder problem to get harder as AI tools change how software gets built and maintained, and as more of the business depends on systems that IT doesn't fully control.

Source: Joao-Pierre S. Ruth · www.informationweek.com

Neighbouring cells