From legacy to leadership: How federal agencies are embracing cloud transformation

At Oracle Federal Forum 2025, a dynamic panel featuring industry and government leaders explored the challenges and strategies involved in modernizing federal HR systems. Moderated by Jake Berkvam, Senior Manager at Baker Tilly, the session offered insights on cloud transformation, standardization and the shifting federal technology landscape.

The panel featured two seasoned professionals - Steve Krauss, formerly of U.S. Office of Personnel Management (OPM), and Ken Plummer from Oracle, who brought unique perspectives shaped by decades of federal and enterprise technology experience.

Defining modernization in government

Plummer revealed how modernization means different things across federal organizations. “What modernization means to each organization is important… some admit they hadn’t upgraded in over 10 years” he commented, highlighting the reality that for some, modernization is as much about security as it is about efficiency. “For them, modernization meant addressing real exposure to security risks.” In others, modernization is tied to the ability to attract top talent, support mission agility or transition away from fragmented, legacy systems toward streamlined, end-to-end Software as a Service (SaaS) solutions.

Common challenges: Funding, fragmentation and federalization

Agencies face many difficulties in securing funding, prioritizing transformation projects and working with vendors to ensure software is configured to meet unique government standards.

Krauss’ team at OPM created an HR IT inventory across agencies, identifying 86 instances of 35 different software platforms, a clear indicator of the fragmentation at play. That inventory laid the groundwork for a new approach to shared data and process standards. These standards, now publicly available, serve as a foundation for federal requirements in modernization efforts.

Rethinking requirements

Both panelists emphasized the need for a shift in how government defines and gathers system requirements. Instead of compiling massive lists of desired features, they advocated for use case driven models – where agencies begin with their actual business needs and evaluate whether the software can meet those needs with standard functionality.