VA Software Governance Failures Linked to CIO Vacancy, GAO Finds

What happened

The United States Department of Veterans Affairs is struggling to manage its enterprise software assets effectively, and a leadership vacuum at the top of its technology function is partly to blame, according to a newly published report from the Government Accountability Office (GAO). The watchdog found that the VA's Enterprise Software Asset Management (eSAM) initiative and a related software licence inventory project both lack the governance frameworks and forward planning needed to function reliably.

The GAO's findings point directly to the absence of a permanent Chief Information Officer at the VA as a contributing factor. Without stable, accountable leadership in that role, the department has been unable to establish the oversight structures that large-scale software management demands. The eSAM programme — designed to give the VA a consolidated view of its software licences and associated costs — has consequently advanced without the strategic direction or accountability mechanisms a programme of its complexity requires.

Why it matters

For those working in customer experience and service design, the VA's situation is a pointed illustration of how internal governance failures translate directly into degraded service delivery. The VA serves millions of veterans across the United States, and the systems underpinning their healthcare, benefits and communications depend on well-managed, properly licenced software. When an organisation cannot accurately account for what software it owns, runs, or has allowed to lapse, the downstream effect is felt by the people who rely on those services — through slower processing, system outages, and inconsistent digital experiences.

From a behavioural economics perspective, the CIO vacancy represents a classic principal–agent problem compounded by present bias: without a permanent decision-maker who owns long-term outcomes, teams default to short-term workarounds rather than investing in the governance infrastructure that pays off over time. The result is institutional drift — and it is the end user, in this case the veteran, who absorbs the cost of that drift in the form of unreliable service touchpoints.

The Renascence take

Most commentary on stories like this focuses on the technology gap — the missing inventory, the ungoverned licences. The more consequential gap is the accountability one, and that is a service-design problem before it is an IT problem.

Governance frameworks are not bureaucratic overhead; they are the structural equivalent of a service blueprint — they make visible who owns what, who is responsible when something breaks, and who the customer ultimately is. The VA's predicament shows what happens when organisations treat CX infrastructure as a back-office concern rather than a front-line commitment. A customer-obsessed operator would treat the CIO role not as an administrative vacancy to be filled in due course, but as the single most consequential open position affecting veteran experience today. The lesson for any service organisation: leadership continuity is a CX asset, and its absence is a CX liability that compounds quietly until it fails loudly.