A federal CIO's exit note
Greg Barbaccia told the CIO Council he had made "the difficult decision to leave government," and his time as federal CIO ends August 31. Barbaccia joined the Trump administration in January 2025 as a former Army intelligence sergeant with a decade at Palantir behind him, and he held an unusually broad mandate for the role: federal CIO, chief AI officer, and acting director of the General Services Administration's Technology Transformation Services. GSA Administrator Edward Forst credited him with having "fundamentally reshaped" the government's approach to technology, largely by pushing agencies toward commercial technology adoption instead of custom-built systems.
His likely successor by default is Thomas Flagg, whom Barbaccia recruited from the Department of Education, where Flagg served as chief information officer, into the deputy federal CIO role earlier in 2026. Flagg stepping up to acting federal CIO would keep continuity of approach, but an acting leader inherits a mandate without the political capital the departing chief spent a year and a half building, and AI governance initiatives that depend on sustained sponsorship are the most exposed.
Barbaccia is not leaving alone
The Transportation Department will lose its chief digital and information officer, Pavan Pidugu, effective September 4. Pidugu was sworn in during February 2025 after nearly five years as CTO of the Federal Motor Carrier Safety Administration, and under his leadership DOT became the first cabinet-level agency to complete a full migration to Google Workspace, a project that touched more than 50,000 employees and required coordinating dozens of sub-agencies onto a single collaboration platform. Energy Department CIO Dawn Zimmer, commenting on the DOT turnover, noted the department "had lots of consolidation going on because they were so federated," a dynamic that made Pidugu's departure land harder than a routine staffing change would at a more centralized agency.
Pidugu's exit follows the earlier departure of Interior Department CIO Paul McInerny, a former SpaceX engineer whose tenure was marked by friction over technology consolidation efforts tied to the Department of Government Efficiency. Interior's acting CIO role passed to Matt Luby, a strategy official also associated with DOGE, continuing a pattern where departures get filled by internal reassignment rather than external search. That pattern keeps agencies staffed in the near term, but it also means each successive leader inherits an in-progress mandate rather than setting fresh direction, and the technology priorities agencies committed to under the departing chiefs now depend on successors who did not originate them.
What was actually built, and who inherits it
The substance of what these departing leaders built is real. Barbaccia's commercial-technology push, Pidugu's Google Workspace migration and T-Cloud environment, and the broader agency-level AI adoption agenda all represent multi-year commitments that outlive any single administrator's tenure on paper but depend on active sponsorship to keep moving in practice. Federal technology programs of this scale routinely stall when the executive who negotiated vendor relationships, budget requests, and interagency buy-in leaves before the work is institutionalized into policy or statute.
That risk is compounded when multiple departures cluster in the same window. Barbaccia, Pidugu, and McInerny leaving within months of each other means several agencies simultaneously lose the single person best positioned to defend AI and cloud modernization budgets in the next appropriations cycle, at precisely the moment those budgets face the most competition for attention from other priorities. New leadership, whether acting or permanent, typically needs two to three budget cycles to rebuild the same negotiating credibility with appropriators and agency heads that a departing executive spent years accumulating.
The lesson for enterprise leaders, not just government
Private-sector CIOs and CTOs running their own AI transformation agendas should not read this as a government-only story. The same failure mode shows up whenever a company concentrates its AI governance program, its cloud migration, or its agentic AI rollout under a single executive sponsor without building the layer beneath them that can carry the work if that person leaves. Board-level succession planning for the CEO is standard practice; succession planning for the executive actually driving a multi-year technology transformation is not, and it should be.
The practical takeaway is to pressure-test any AI or infrastructure initiative your organization is running against the question: does this survive if the sponsoring executive leaves in the next two quarters. If the answer depends on that individual's personal relationships with vendors, their specific technical judgment calls, or informal authority they built rather than documented governance, the program is more fragile than the roadmap slide suggests. Federal agencies are learning this in public; enterprise boards should learn it before they have to.
What to watch next
The near-term marker to watch is whether Thomas Flagg's transition from deputy to acting federal CIO happens smoothly or triggers a broader leadership vacuum at OMB's technology office. A prolonged acting-status period historically slows down cross-agency initiatives that require a Senate-confirmed or at least fully empowered federal CIO to sign off on policy changes, and AI procurement guidance is exactly the kind of initiative that stalls under an acting leader with limited authority to make binding commitments.
At Transportation and Interior, the test is whether incoming leadership, acting or permanent, continues the consolidation and cloud migration work already underway or uses the transition as an opportunity to reset direction. Vendors and contractors with active federal technology engagements should expect a slower decision cadence through the fall as new leadership gets oriented, and should plan procurement timelines accordingly rather than assuming continuity of pace from the outgoing team.
