This article is based on commentary originally published at Nextgov, authored by Mark Forman, former U.S. Administrator for E-Government and Information Technology at the Office of Management and Budget (2001–2003) and Vice President of Digital Government for Unisys Federal.
The Cloud Is Not a Magic Wand for Government IT
Public sector technology executives broadly agree on the need to modernize agency IT—improving cybersecurity, reducing operating costs, and meeting the expectations of digital-native workers and citizens. The challenge is that modernization discussions too often center on which technology to adopt rather than what outcomes that technology should deliver.
Cloud computing is the current candidate for that magical thinking. Agencies are migrating workloads at scale, but migration alone does not guarantee the hoped-for improvements in cost, security, or service quality. As a Government Accountability Office report noted, simply moving applications to the cloud does not automatically produce benefits. The scale at which government agencies operate—serving millions of citizens—makes the stakes of poorly managed cloud adoption exceptionally high.
Understanding How Cloud Technologies Deliver Value
Before CIOs can manage cloud adoption effectively, they need a clear-eyed understanding of the specific mechanisms through which cloud technologies create value. These include:
- APIs (Application Programming Interfaces): Dramatically reduce the need to build and maintain customized integration code between systems, lowering both development time and long-term maintenance burden.
- Containerization and virtualization: Allow applications to run on shared, elastic infrastructure at significantly lower cost than dedicated physical servers.
- Web services and microservices: Enable agencies to build, update, and maintain application components independently, at a fraction of the cost compared to monolithic architectures prevalent a decade ago.
- Data decoupling: Separating legacy code from underlying data formats unlocks the ability to apply data analytics, robotic process automation (RPA), and modern collaboration tools—critical for digitizing services and regulatory enforcement.
Each of these represents a concrete operational lever, not an abstract promise. CIOs who understand the mechanics can set realistic expectations, measure actual outcomes, and course-correct when results fall short.
From IT Silos to an Ecosystem Operating Model
The traditional government IT model is organized around silos: unique software and hardware stacks managed independently for each application. That approach made sense when applications were largely self-contained, but it creates duplication, rigidity, and runaway costs at cloud scale.
High-performing government IT shops are shifting to an ecosystem operating model focused on shared services and measurable outcomes. The key components of that model include:
- Secure hybrid cloud: A architecture that integrates on-premises infrastructure with public and private cloud services, giving agencies flexibility without abandoning compliance requirements.
- Cloud management platform: Positions the CIO as a trusted broker who can compare service options, manage ordering, and track usage, performance, and costs in a single pane of glass.
- IT service cost and performance transparency: Makes the real cost of each service visible, enabling data-driven decisions rather than budget guesswork.
- Web services and microservices adoption: Replaces inflexible, tightly coupled application components with modular, independently deployable services.
- IT process automation: Eliminates repetitive manual tasks across provisioning, monitoring, and compliance workflows.
- DevSecOps: Integrates development, security, and operations practices to digitize government processes—rather than simply automating outdated paper-based workflows (the so-called “cow paths”).
Three Core Strategies for Government CIOs
Rather than treating cloud as a technology destination, government CIOs should pursue three management strategies that translate cloud capabilities into agency outcomes.
1. Abandon the Capital Expenditure Model
The CapEx model—buying hardware and software assets on multi-year cycles—is fundamentally incompatible with the elastic, consumption-based economics of cloud computing. Agencies should transition to a service catalog model for hybrid cloud, one that documents and compares performance, security posture, and cost against the legacy siloed baseline. Day-to-day management through a cloud management platform provides the operational data needed to make that comparison credible and ongoing—not just a one-time procurement justification.
2. Apply Apps-Level, Outcome-Driven Thinking
Every cloud project should start with a clear question: What outcome am I trying to deliver to the internal user or citizen? This reframes technology decisions around user needs rather than infrastructure preferences. Agile development practices infused with security—DevSecOps—and genuine line-worker engagement are the practical tools for executing on that framing. Critically, leveraging microservices within applications delivers greater long-term benefit than simply containerizing existing legacy applications without rearchitecting them. Containerizing a monolith moves the problem; decomposing it into microservices solves it.
3. Address Behavioral Economics and Change Management
Cost and performance improvements may be obvious to the department CIO, but agency owners and system managers often perceive cloud migration as a loss of control. That perception is a real adoption barrier, and it will not be overcome by technical arguments alone.
Effective CIOs address this by building outcome-based value propositions tailored to the specific pressures each agency faces—for example, demonstrating the cost and time savings of implementing a regulatory change in a cloud-native system versus a legacy monolith. IT service catalogs must be continuously updated as cloud offerings evolve, balancing encouragement of adoption against the fixed costs that agencies cannot immediately shed.
Business process re-engineering is frequently necessary before digital services can be realized. Many government agencies have had measurable success using DevSecOps environments to demonstrate productivity and security improvements from digitized processes—compared to continuing paper workflows or merely automating those paper workflows as-is.
The Bottom Line
Cloud computing offers genuine, substantive benefits for government agencies. But those benefits do not materialize automatically from migration. Realizing them requires CIOs to replace magical thinking with concrete management discipline: understanding the technology mechanisms that create value, restructuring operating models around outcomes, and actively managing the human and organizational change that technology adoption demands. The agencies that get this right will deliver measurably better services; those that treat cloud as a destination rather than a tool will find themselves with higher bills and the same old problems.
About the author: Mark Forman served as the first U.S. Administrator for E-Government and Information Technology at the Office of Management and Budget (2001–2003) and was Vice President of Digital Government for Unisys Federal at the time of original publication.