If there is one thing I learned serving as a state CIO, it is that pressure never arrives one problem at a time. Government technology leaders are usually asked to improve service delivery, strengthen cybersecurity, support agencies with limited staff, modernize aging infrastructure, and keep costs under control all at once.
That balancing act feels even harder today.
State and local leaders are operating in a very different budget climate than they were just a few years ago. Federal relief funding, including American Rescue Plan Act (ARPA)-related support, helped many governments move overdue projects forward, and in many cases that was the right call. Agencies used that window to improve infrastructure, expand digital services, address security gaps, and build momentum around modernization. But that window is closing. Temporary funding streams are winding down, inflationary pressure remains real, and jurisdictions are being forced to distinguish between what is desirable and what is sustainable.
That is the new fiscal reality for state and local IT.
From where I sit, this moment is forcing a healthier and more disciplined conversation. Modernization can no longer be framed as a broad aspiration or a technology refresh for its own sake. In the current environment, state and local leaders need modernization strategies that are directly tied to measurable operational and financial outcomes. That means reducing administrative complexity, shrinking infrastructure sprawl, improving system availability, lowering risk, and creating a clearer line of sight into long-term costs. The challenge is not simply finding money for innovation. It is ensuring that innovation does not create a new layer of financial volatility.
The end of the post-ARPA spending window is making that issue impossible to ignore. During the peak of federal relief funding, some organizations had the flexibility to move quickly on infrastructure, cloud adoption, security improvements, and digital service delivery. In many cases, that acceleration was necessary and beneficial. But now, leaders must determine what comes next when one-time funding is replaced by recurring budget accountability. Projects that were easy to justify under emergency or stimulus conditions are now being re-evaluated under a very different standard: Can the organization afford to operate and expand them over time?
That shift is changing infrastructure decisions in a fundamental way.
Instead of asking only what technology can do, agencies are asking what financial model best fits public-sector realities. Instead of optimizing for short-term project approval, they are thinking more carefully about lifecycle cost, procurement flexibility, staffing impact, and ongoing operational predictability. Infrastructure choices are no longer just technical architecture decisions. They are budget strategy decisions, too.
This is especially important because the wrong cost model can undermine even the right technology decision. A platform may appear attractive at the point of purchase, but if its cost structure is difficult to forecast, vulnerable to overconsumption or dependent on future spending increases, it can create the very instability agencies are trying to avoid. State and local IT leaders do not need more surprises hidden in usage patterns, support complexity, licensing changes or fragmented management overhead. They need models that help them plan confidently, defend investments clearly, and maintain service levels even when budget conditions tighten further.
Predictability, in this environment, is not a luxury. It is a requirement.
That is why cost transparency and operational simplicity are becoming central to infrastructure strategy. Technology leaders are under growing pressure to explain not just the value of a solution, but the durability of its economics. They must be able to answer difficult questions from budget offices, procurement teams, legislators, and executive leadership: What will this cost next year? What will drive that cost up? What risks are we removing? What inefficiencies are we eliminating? How does this decision protect us from future financial disruption?
Those questions are healthy. In fact, they may lead to better decisions than the public sector made during periods of looser funding. Scarcity has a way of clarifying priorities. It forces organizations to focus on investments that deliver resilience, efficiency, and strategic flexibility rather than simply adding tools or capacity. It also elevates the importance of platforms that reduce complexity instead of introducing more of it.
The strongest modernization strategies in this next phase will likely share a few characteristics. They will prioritize outcomes over buzzwords. They will account for both capital and operating realities. They will reduce the number of moving parts agencies must manage. And they will be designed around a simple principle: Technology should help government leaders sleep better, not wonder where the next budget surprise is coming from.
State and local IT is not entering a period of retreat. It is entering a period of sharper decision-making. The mission remains urgent. Communities still need secure, responsive, modern public services. But the path forward will belong to leaders who can align modernization with fiscal discipline and who understand that the most valuable infrastructure investments are not always the ones with the most features, but the ones with the clearest, most sustainable economics.
That is the new fiscal reality. Modernization still matters. But now it must prove not only that it can transform operations, but that it can do so without creating a new generation of cost uncertainty.
For state and local leaders thinking through what that looks like in practice, see additional resources on modernization, cyber resilience, and building a more predictable data foundation.
Jim Weaver is a former state CIO and nationally recognized public-sector technology leader with deep experience guiding government IT strategy, modernization, and cybersecurity initiatives. He served as Secretary and Chief Information Officer for the North Carolina Department of Information Technology, where he oversaw statewide IT strategy, procurement, cybersecurity, and broadband expansion. Prior to that, he served as CIO for the state of Washington, helping strengthen the state’s IT infrastructure and advance technology adoption across government. Jim also served as president of the National Association of State Chief Information Officers (NASCIO), contributing to IT policy and collaboration nationwide.
Leave a Reply
You must be logged in to post a comment.