Modernization Is a Commitment, not a Purchase
When people think about modernization, they first think about technology: a new platform, upgraded infrastructure or an emerging capability. But every investment shapes the next five, seven or 10 years of operations. It has to be secured, monitored, maintained, upgraded and integrated with everything else. Vendors and contracts must be managed, and staff must learn to use, support and eventually replace it.
One or two new systems rarely feel overwhelming. The burden builds as state and local IT organizations accumulate more vendors, platforms, data silos and integrations across agencies with different missions and needs. Skilled employees spend more time keeping technology running, leaving less time to strengthen cybersecurity, improve resident services and prepare for what comes next.
That complexity quietly consumes government’s most limited resources: time, talent and budget. While those costs don’t appear as a line item in a budget, they’re real. They show up in duplicated effort, maintenance debt and stalled projects because the people needed to lead them are busy keeping old systems and projects alive.
READ MORE: Here is a guide to data governance for state and local agencies.
Fund Data Like a Mission, not a Maintenance Task
This is where I’d push CIOs and budget officers to change the conversation. Data governance, quality and integration shouldn’t be negotiated as part of whatever platform happens to generate the data, and it shouldn’t be the thing that gets deferred when a budget tightens. It should be its own line, defended on its own terms, because every mission outcome a state cares about — faster benefits delivery, better fraud detection, a cybersecurity program that can actually see its own environment, an AI initiative that doesn’t hallucinate policy — depends on the state’s data being trustworthy, integrated and governed.
To make that case credibly, leaders need to change how they evaluate technology investments. Instead of asking what a proposed investment would let the agency do, ask what it would let the agency stop doing. Will it eliminate a manual process, reduce the number of systems the team has to manage, or free skilled employees for higher-value work? That question should prompt a review of what’s already in place — whether an existing tool can meet the need, whether overlapping capabilities can be consolidated, and whether a process could improve without adding another system to support.
That discipline matters most as governments expand their use of artificial intelligence. AI has real potential to improve public services, but that value depends on the data foundation underneath it. Layer AI onto fragmented, ungoverned data and agencies get faster mistakes, not better outcomes. Strengthening that foundation isn’t a modernization nice-to-have; it’s the precondition for every AI investment a state is about to make, which is exactly why it belongs in the budget as a mission priority, not as operations and maintenance.
For today’s CIOs, I’d encourage evaluating every major technology investment against the goals of their modernization strategy by asking three questions:
- Are we fully using what we already have?
- What work or complexity will this help us eliminate?
- Does it strengthen the data our mission actually depends on?
Public sector technology leaders will always face difficult budget choices and rising expectations. The ones that succeed will be those who stop treating data as the exhaust of modernization projects and start funding it as the mission asset it is — because that’s what turns a modernization budget into lasting operational capacity.
