Large-scale government modernization efforts often begin with technology: a new platform is selected, funding is approved, and consultants are brought in to help define the roadmap. Agencies begin preparing for the long process of replacing systems that may have been in place for years or even decades.
Yet inside many state and local government initiatives, the more difficult challenge emerges after the strategy work is complete and implementation begins. Systems still need to remain operational, multiple stakeholders become involved, and technical teams are asked to execute against increasingly interconnected environments.
That reality became especially clear during a modernization initiative involving a Southeastern state’s Department of Transportation preparing to expand its network engineering capabilities. Leadership believed the next step was relatively straightforward: hire four network engineers to support a growing infrastructure environment tied to broader operational and technology initiatives.
At first glance, the request seemed reasonable. Expanding systems typically require additional technical resources, particularly in government environments where modernization efforts often unfold while agencies continue managing day-to-day public operations.
As conversations between the agency and IDR became more detailed, however, it became clear the initiative involved more than simply adding engineering capacity.
The systems being built were highly interconnected, and many of the most important decisions would revolve around architecture, integration, and long-term operational design. Expanding the team without stronger technical oversight would likely create additional layers of coordination, increase management complexity, and slow execution across the broader project.
Rather than moving directly into recruiting, the discussions shifted toward understanding how the initiative itself needed to function operationally.
“We are never just order takers,” said Samantha Green, Director of Government Services at IDR. “Our goal is to understand the end goal of the project.”
That perspective shaped the direction of the engagement.
As the project became more clearly defined, the conversations moved beyond individual job descriptions and into broader questions around how the environment would operate, where technical leadership would be most critical, and how decisions would ultimately be coordinated across the initiative.
The deeper the discussions became, the clearer it was that the agency did not necessarily need a larger engineering team as much as it needed stronger architectural leadership capable of guiding the broader modernization effort.
The recommendation that emerged reflected that shift in thinking.
Instead of hiring four network engineers, IDR recommended bringing in a Network Architect specializing in cloud infrastructure who could design the environment, guide implementation decisions, and provide centralized technical direction across the initiative. While the adjustment may have appeared relatively small on the surface, it significantly changed the operational structure of the project itself.
“The recommendation shifted the focus from headcount to capability,” Green explains. “This has helped focus on the true end goals of the project.”
The revised approach led to IDR placing two additional resources, a Cloud Engineer and a Network Engineer, helping to simplify communication across the project and giving the agency a clearer operational structure moving forward. Technical decision-making became more centralized, implementation priorities became easier to coordinate, and the broader team gained stronger alignment around the long-term goals of the initiative.
Just as importantly, the engagement changed the nature of the relationship itself.
Rather than functioning as a traditional staffing vendor responding to requisitions, IDR became a consultative partner focused on how the modernization effort would actually be executed over time.
That distinction has become increasingly important across state and local government.
Modernization initiatives today rarely involve isolated systems or standalone implementations. Agencies are simultaneously managing cloud infrastructure, cybersecurity initiatives, GIS platforms, operational data systems, accessibility requirements, and emerging AI-driven technologies, often while continuing to support live public services without interruption.
Large consulting firms may oversee strategy and implementation planning, while internal agency leadership manages operational continuity and external technical teams support execution across multiple workstreams. As these environments become more interconnected, the success of modernization efforts depends less on any individual technology decision and more on how effectively teams are structured to execute within increasingly complex operational ecosystems.
Transportation agencies provide one of the clearest examples of this shift.
Departments of transportation are no longer focused solely on roads, bridges, and traffic systems. Many now operate highly data-driven environments involving traffic operations centers, GIS ecosystems, cloud infrastructure, and real-time operational analytics designed to support everything from congestion management to infrastructure planning.
Supporting those environments requires coordination across multiple technical disciplines, including cloud engineering, cybersecurity, GIS development, operational infrastructure, and enterprise architecture.
“The challenge is not simply finding people with technical skills,” Green said. “It is understanding how teams should be designed to support the broader goals of the initiative.”
As modernization efforts continue to evolve, expectations around external partners are evolving as well.
State and local agencies are no longer simply looking for vendors who can fill open roles quickly. Increasingly, they are looking for partners who understand how transformation initiatives function operationally, where execution bottlenecks are likely to emerge, and how technical teams should be structured to support long-term outcomes rather than short-term staffing demands.
In this case, rebuilding the team structure ultimately became just as important as rebuilding the systems themselves, a reality many agencies are beginning to encounter as modernization efforts grow larger, more interconnected, and more operationally complex.