Skip to main content
Back to the blog

SLED Digital Transformation

By Samantha Green

June 2, 2026
Updated: June 2, 2026

It Isn’t About Technology. It’s About Execution.

Across the country, state and local governments are under growing pressure to modernize systems that millions of people rely on every day. Agencies are replacing legacy platforms, rebuilding citizen-facing services, implementing accessibility standards, and experimenting with AI-driven tools designed to improve operations and public service delivery.

The scale of that transformation is significant. According to a 2025 survey from EY, 71% of state and local government IT decision-makers say modernizing legacy systems is a top challenge, while 61% worry their agencies will become obsolete if they do not partner more effectively with the private sector. At the same time, concerns around cybersecurity, funding, and skilled talent continue to slow implementation efforts.

What makes these initiatives difficult, however, is rarely the technology itself.

Most agencies already understand the need to modernize. Consulting firms help define roadmaps. Platforms like Workday, cloud infrastructure, GIS ecosystems, and AI tools are widely understood. The larger challenge begins after strategy is approved and implementation moves into live operational environments.

That is where transformation becomes significantly more complicated.

Large-scale government modernization efforts require coordination across agencies, consulting firms, procurement structures, technical teams, and systems that often cannot pause during implementation. Projects evolve over multiple years. Team structures shift. Priorities change. New technologies are introduced while existing services must continue operating without interruption.

From the outside, these initiatives can appear to be isolated technology upgrades, but inside state and local agencies, they are operational balancing acts.

Teams at IDR see this dynamic play out across multiple states and agencies. While every initiative has its own complexity, the underlying pattern can be remarkably consistent.

Transformation rarely breaks down because organizations lack vision; it breaks down in execution.

The Complexity Challenge

Most state agencies do not tackle these initiatives alone. Large consulting firms are often brought in to help define strategy, evaluate platforms, manage procurement processes, and oversee implementation. In many cases, firms like Deloitte, KPMG, and others sit at the center of large modernization efforts that can span multiple agencies and multiple years.

That layer of strategic oversight is important. But even the most well-designed roadmap eventually runs into a more practical question:

Who is actually going to execute the work?

This is where modernization efforts often become more complicated than they initially appear.

A large-scale migration from PeopleSoft to Workday, for example, is not simply a software replacement project. It requires teams capable of managing data migration, redesigning workflows, integrating systems, coordinating stakeholders, training users, and maintaining continuity while agencies continue operating in real time.

The technology itself is only one layer of the challenge. The larger issue is coordination.

Projects often involve multiple groups operating simultaneously:

Each group operates with different priorities, timelines, and constraints. As projects evolve, those relationships become increasingly interconnected.

From the outside, it can appear as though agencies are simply “upgrading systems.” Inside the organizations themselves, the reality is far more operationally complex.

Teams are balancing modernization efforts while maintaining services that millions of residents still depend on every day.

The Talent Gap

State and local agencies face another challenge that is less visible from the outside: many do not have the internal technical capacity required to execute these initiatives entirely on their own.

Hiring cycles can be slow and budget structures are restrictive within many agencies.  Additionally, specialized expertise is difficult to secure, particularly in areas like cloud architecture, enterprise migration, GIS, cybersecurity, and AI.

As a result, agencies often rely on a blended ecosystem of internal staff, consulting partners, and external technical resources to move projects forward.

That ecosystem can create tremendous momentum when it is aligned correctly. It can also create friction when teams are structured around requisitions rather than outcomes.

This is where the conversation around talent becomes more nuanced.

The challenge is not simply finding people with technical skills. It is understanding how teams should be designed to support the broader goals of the initiative.

In some cases, agencies initially focus on scaling headcount when the real need is strategic expertise.

One Southeastern state’s Department of Transportation, for example, originally planned to hire multiple network engineers to support a growing infrastructure initiative. But after a deeper discussion around how the systems would actually function together, the recommendation shifted. Instead of expanding the team broadly, the agency brought in a senior architect capable of designing the environment, guiding implementation, and reducing the coordination burden across multiple roles.

The outcome was not just a more efficient team structure. It was a better alignment between the technical resources and the actual goals of the project.   

That’s an important point because organizations navigating transformation initiatives increasingly need partners who understand not only the technologies involved, but also how execution environments function operationally.

A Model in Transportation

Transportation departments offer one of the clearest examples of how this shift is unfolding inside state and local governments.

Traditionally, departments of transportation were viewed primarily through the lens of physical infrastructure: roads, bridges, traffic systems, and construction projects.

Today, many of these organizations are becoming deeply data-driven operational environments.

Departments are collecting and analyzing real-time traffic data, modeling congestion patterns, evaluating tolling strategies, and using GIS platforms to guide infrastructure planning. In states like Texas, agencies are exploring AI-driven tools to improve traffic operations and customer service functions.

These systems require more than software implementation.

They require teams capable of integrating data systems, cloud infrastructure, GIS platforms, communication networks, and operational workflows into environments that remain functional around the clock.

Many states now operate sophisticated traffic operations centers that function almost like real-time command environments, bringing together infrastructure monitoring, communication systems, and transportation analytics in centralized operational hubs.

As these environments evolve, the technical demands become more interconnected. GIS analysts, cloud engineers, developers, architects, cybersecurity professionals, and operations teams all contribute to the same broader ecosystem.

That complexity changes the nature of execution.

Success depends less on isolated technical roles and more on how effectively teams operate together inside highly coordinated environments.

From Staffing Vendor to Operational Partner

As these initiatives become larger and more interconnected, expectations around external partners are changing as well.

State and local agencies are no longer simply looking for vendors who can fill open roles. Increasingly, they are looking for partners who understand the broader operational context surrounding the work.

That means understanding:

It also means being willing to challenge assumptions when necessary.

Sometimes the best solution is not adding more people. Sometimes it is restructuring the team entirely. Sometimes it involves identifying gaps that agencies or consulting partners may not initially recognize.

From IDR’s perspective, those conversations are often where the most value is created.

The goal is not simply to respond to a requisition. It is to understand what the organization is ultimately trying to accomplish and align execution around that outcome.

Over time, that approach changes the nature of the relationship.

The conversation shifts away from transactional staffing and toward operational partnership.

The Future of Modernization Will Be Defined By Execution

The next phase of government transformation is already underway.

State and local agencies continue to modernize enterprise systems, rebuild citizen-facing platforms, implement accessibility standards, strengthen cybersecurity programs, and explore AI-driven capabilities. The pace of change is unlikely to slow.

But the organizations that succeed will not necessarily be the ones with the most ambitious technology strategies.

They will be the ones capable of executing transformation effectively inside complex operational environments.

That requires more than funding and technology selection. It requires alignment across systems, teams, partners, and long-term organizational goals.

Technology may shape the direction of modernization, but execution determines whether it succeeds.

Back to our blog