A Question That Can Reframe How You Think About IT

“I honestly have no idea if we’re spending our IT budget well. I don’t even know what question to ask.”

That’s the kind of thing some leaders say when they’re thinking about their IT setup. No crisis. No systems on fire. Just a quiet, hard uncertainty that a lot of leaders share but rarely say out loud. And there’s one simple question that can reframe the thinking productively:

“What percentage of the work your team or IT provider does for you is reactive versus proactive?”

One question. But the answer reshapes how you think about the effectiveness of your IT budget, and it gives you a sentence you can take straight to your board or leadership team: “Right now, 70% of our IT spend is keeping things from falling apart. 30% is building stability, capacity, and new capability. Here’s our plan to shift that over the next twelve months.” Decision-makers understand that framing instantly.

The distinction that matters

Reactive work is everything that happens after something breaks: tickets, outages, emergency calls. It’s necessary, but it’s pure expense. You’re paying to get back to where you were before the problem happened.

Proactive work is the other side. Most people assume that means patching, backups, and hardware planning — the defensive layer that prevents future fires. That matters. But usually the bigger value comes from aligning technology with where your organization is heading, redesigning a workflow that’s costing your staff hours every week, surfacing opportunities you didn’t know were available because you’ve been too deep in the day-to-day to look up.

Proactive work that only prevents problems is optimization. Proactive work that opens up new capacity or improves how your organization operates is opportunity. If your IT function is only doing the first kind, you’re leaving a lot on the table.

What the answer tells you

If the work is mostly reactive, that doesn’t necessarily mean your team or provider is failing. Some organizations have years of accumulated technical decisions creating a heavy reactive load, and the environment needs to be stabilized before proactive efforts can gain traction. But now you know, and knowing gives you a starting point: what would it take to shift the ratio? What proactive work has been deferred? Where should you invest intentionally instead of absorbing whatever comes?

If the answer is mostly proactive, ask whether that work maps to your actual strategic priorities or just a standard checklist applied regardless of context. If your team or provider can’t draw that line, the work needs to be revisited.

Turning the ratio into a tool

Here’s what this can look like in practice. Imagine an organization sitting at roughly 80/20, reactive to proactive. That’s not unusual. After about eighteen months of intentional work — stabilizing the environment, retiring old systems, putting monitoring in place — an organization like that could realistically get somewhere between 50/50 and 20/80. Total monthly IT spend might go up significantly, but the number of disruptions staff deal with could drop dramatically. In practical terms, that often looks like an administrative team reclaiming dozens of hours a month that had been eaten by workarounds, manual processes, and waiting on broken systems.

That recovered capacity is where the real story is. It’s what lets a team finally launch the program expansion they’ve been deferring, or redirect staff time toward work that actually moves the mission forward.

That’s a fundamentally different budget conversation than “we need more money for IT.”

Knowing the ratio also creates accountability in a healthy way. If you agree together that the goal is to shift from 70% reactive to 50% reactive over the next year, you’ve got something concrete to track. Not as a gotcha, but as a shared objective — something both sides can look at quarterly and make decisions around together.

You don’t need a fancy assessment to start. Just ask this fundamental question. See what your team or provider says. If they can answer clearly and specifically, that’s a good sign regardless of the ratio. If they can’t, that tells you something too.