Your privacy matters. We’ve updated our policies effective March 24, 2026.

LEARN MORE

IT modernization insights for government CIOs

A few of our team members attended the Beyond the Beltway 2022 – Virtual Event hosted by the Center for Digital Government. It was an incredible opportunity to hear directly from state and local government CIOs and CSOs. They discussed the initiatives they are working on, the tech trends important to their region, and the best ways the private sector can be a true partner in finding solutions to their problems.

One thing was certainly evident, government CIOs and CSOs have their work cut out for them. They have to balance federal directives with constituent service expectations within the constraints and protocols of the local governing body. The featured speakers from government organizations across the country were generous with their insights, and the sessions were expertly moderated by the staff at the Center for Digital Government. Here are a few things we learned about technology modernization at the state and local levels of government.

1. Strategic plans inform technology modernization considerations

Although the featured CIOs spoke to the specific needs of their region, they all stressed that their strategic plan, which is available to the public, guides all modernization considerations. Their projects reflect these overarching government directives heard throughout the event:

  • Keep our systems secure (cybersecurity)
  • Protect the privacy of our people (PII data)
  • Meet constituent expectations (digital engagement)
  • Support remote and hybrid workforces (secure cloud-based systems)
  • Prove compliance (tracking and reporting)

Any modernization project will advance progress towards the strategic plans and support the overarching directives.

2. CIOs use existing technologies, processes, people, and relationships wherever possible

The featured CIOs spoke passionately about being good stewards of taxpayer dollars. They always first evaluate and leverage existing systems and expertise wherever possible. Then, they review internal processes and skills and engage with partners they know and trust.

If a technology modernization initiative is needed, government CIOs reach out to each other looking for similar, successful projects. They want the highest probability of success with the least risk possible – and don’t want to re-invent the wheel.

3. Funding for technology modernization is only part of the solution

Yes, having money allocated for technology modernization is great. But the CIOs stressed that the funding is only a piece of the overall initiative. The more significant challenges lie in the execution of getting the project completed.

Government CIOs are looking for holistic proposals beyond the specific technology solution. The proposals must also include:

  • External experts assigned to the project
  • Internal IT resources required to support the project
  • Best practice frameworks and guides
  • Relevant case studies
  • Knowledge transfer plans
  • Long-term support considerations (maintenance fees, upgrades, training, etc.)

Comprehensive plans help give the CIOs confidence that the modernization project is successful and sustainable.

One final point stressed by several of the speakers – it’s challenging to retain internal IT talent within the government. It’s a very competitive job landscape, with many choosing employment in the private sector. Therefore, CIOs tend to give favor to external suppliers who will help upskill and reskill government employees to support the modern technology and processes

4. Technology suppliers need to do their homework

The public availability of contact information for government IT staff makes reaching out to the CIOs incredibly easy. While our speakers welcome the outreach, they are often disappointed that technology suppliers haven’t researched what matters for that specific CIO office. The cold outreaches are broad, generalized, and focused on selling to the CIO.

Government CIOs want the outreach, but they want to understand the pitched technology fits within the context of their strategic plan and the ecosystem of providers they already use. This information is publicly available, so they want suppliers to do their homework and frame the solution in the following ways:

  • Plan – what specific initiatives or directives does the technology modernization support?
  • People – who are the people involved, and how will others and the community benefit?
  • Process – what process improvements does the technology modernization support?
  • Technology – what are examples of it working for similar organizations solving like challenges?
  • Policy Implications – what are the policies considerations surrounding the technology?
  • Performance – how do we measure and share positive outcomes resulting from technology modernization?

The final thought one CIO offered to technology vendors was, “bring me leading edge, not bleeding edge, tech.” The agreement was while cutting-edge technology may be interesting, it doesn’t have a place in government until sufficiently proven.

5. Public CIOs want true partnerships with private sector technology providers

State and Local CIOs are operating to plans that extend years into the future. They also are tying every technology investment to the needs of their community, such as democratizing broadband access and keeping their citizens safe from cybercriminals. These challenges can’t be solved with a single technology or even within a single administration. And the balancing forces within the government mean technology modernization progress is slow compared to the private sector.

Therefore, government CIOs want partners with them for the long haul. They want partners committed to being a part of the solution beyond the technology they may provide. Partners who can bring ideas, best practices, and other partners and who take the time to build a personal and trusted relationship give the most value. Those are the partners who work on the government project.

Synchrony Systems’ work in state and local government

We have been fortunate to serve several state and local government organizations such as Bay Area Rapid Transportation (BART), City of Atlanta Fire Department, Oregon State Judicial Department, and New York City Police Department. Through our trusted partnerships, we helped migrate and modernize their legacy applications to modern, cloud-based, and mobile-friendly applications and user interfaces.

Our automated migration and modernization technology allows our partners like IBM, Astadia, and TSRI to leverage our platform and expertise on government modernization initiatives efficiently and effectively.

ModOps: DevOps for legacy modernization

DevOps has revolutionized software engineering methodology by unifying development and operations to accelerate software delivery. The older-style waterfall approaches to greenfield application development are being put aside as DevOps principles of agility, iteration, continuous delivery, and automation take center stage.

Modernization must deal with the challenge of transforming millions of lines of existing legacy code, built over decades by dozens, if not hundreds, of engineers, most of whom have moved on or retired altogether. Yet outdated approaches such as “rip and replace” are still the default modernization methodology, employing manual rewrites and disjointed automation tools. This approach is costly, takes an enormous amount of time and resources, and introduces significant risk to the business.

At Synchrony Systems, we believe it’s time to apply the DevOps principles, adopted for greenfield development, to software modernization—or ModOps—to keep pace with the rapid digital transformation.

Accelerating modernization delivery

Modernization focuses on transforming existing legacy systems and applications to the latest platforms and architectures. Unlike greenfield development, where very frequent and incremental changes are made to small bodies of code, modernization requires making wholesale transformations of the entire body of code at once and en masse. Therefore, the traditional manual approaches to modernizations can no longer be justified in today’s rapidly moving digital economy.

As the chart illustrates, ModOps accelerates modernization delivery and does so at a fraction of the cost and with faster time-to-value. It balances the overall speed, cost, quality, and risk while creating a unified experience that addresses a complex modernization process in a predictable way.

Continuous modernization

Continuous Development (CD), along with Continuous Integration (CI), have become the cornerstones of DevOps— the way applications are being developed and released into production. By replacing CD with Continuous Modernization (CM), ModOps will achieve the same—the way existing applications are to be modernized. Continuous Modernization will bring a high degree of automation and a systematic approach to managing the entire modernization lifecycle.

The three main pillars of ModOps are:

  1. automation-driven modernization and transformation of legacy applications to modern programming languages and platforms;
  2. coexistence of modernization activities with ongoing development activities, without any code freezes; and
  3. functional and UX equivalency with no hidden costs or operational disruptions to the business.

ModOps is the answer for any company whose objective is to preserve its IP and its original investment in mission-critical legacy applications by adapting to and effectively competing in a rapidly moving digital economy.

As in DevOps, ModOps promotes agility, collaboration, and complete transparency. Project managers, migration engineers, testers, and other business stakeholders have full visibility into the overall status and progress of an ongoing modernization at every stage. With built-in planning, tracking, monitoring and dashboards, extensible workflows, automated testing and real-time feedback, a modernization is guaranteed to run smoothly and to be completed on time and on budget.

Tools for ModOps

The evolution of DevOps has spurred the development of tools to help teams more easily apply DevOps principles to the application development process. Modernization Lifecycle Platform (MLP) is doing the same for the application modernization process. It is a DevOps-driven, integrated, Modernization-as-a-Service platform that creates a unified approach to modernizing legacy applications. Whether it’s a modernization of COBOL to Java, PowerBuilder to C# or Smalltalk to Java, the underlying process, methodology, and user experience are uniform, no matter the chosen source and target platform combination. As a result, organizations are just months—not years—away from having their legacy applications transformed to the digital economy of web, mobile, and cloud.

No more legacy applications

We see a future where the application software is never “left behind” or lost to obsolescence. The major business challenges created by legacy applications—growing technical debt and shrinking technical talent—would themselves become obsolete.

Adding Continuous Modernization (CM) alongside CI/CD would give developers the ability to systematically and incrementally apply new software updates, adapt new APIs, or any other software components to in-house applications, thus doing away with any future wholesale modernization initiatives. By embracing ModOps and adopting a platform like MLP, businesses will become more agile, competitive, efficient, and responsive in addressing the demands of today’s digital economy.