News Analysis
White Paper
The Future of Leadership Development: AI-Driven Manager Enablement
In March 2025, U.S. Secretary of Defense Pete Hegseth pulled the plug on a federal HR consolidation project that had been running for seven years.
It started in 2018 during the first Trump Administration as a $36 million, one-year proof of concept to consolidate roughly six DoD HR systems onto a single cloud platform. By the time Hegseth shut it down, it was 780% over budget. It failed due to familiar causes: scope creep from middle managers, a systems integrator running both the old and new platforms with a conflict of interest, and technology that moved faster than the program could move.
The vendor? Oracle.
Fourteen months later, the Office of Personnel Management awarded the same company an ambitious 10-year contract to do the same thing at a much larger scale.
One platform. 119 fragmented agency HR systems combined into one. Two million civilian employees. OPM's savings claim: A more than 90% reduction in HR platform costs. The base value of the contract is $395.8 million, though trade press put the real number north of $1 billion once task orders and licensing are counted.
Anyone running a large tech consolidation right now should be paying attention to the biggest HR transformation playing out in public. And as you might expect, it’s already off to a rocky start.
The Third Attempt at Starting HR Consolidation
OPM's first move, in May 2025, was a no-bid award to Workday, arguing only one vendor could do it. That attempt fell apart within days. A second attempt through a GSA schedule task order was also withdrawn. The award Oracle received was attempt number three.
The final phase came down to Oracle, teamed with Deloitte, against Workday, teamed with Accenture. IBM and Economic Systems, eliminated earlier, both filed protests. IBM had been a federal HR shared-services provider since 2008, handling operations for OPM, GSA and the VA.
One industry source described IBM as on solid ground and worried that picking a "shiny object" would force an expensive data cleanup from scratch. Before the award was announced, at least one federal agency had formally asked OMB for a waiver to opt out entirely.
You can bet more are coming.
An OMB memo from Director Russ Vought set a target to transition every major agency by July 4, 2027. Industry insiders were calling it unrealistic before the ink dried. Political deadlines rarely accelerate consolidations. They tend to produce shortcuts that generate the next protest or the next failure.
Oracle Didn't Necessarily Win on Innovation
Oracle has owned PeopleSoft since 2005 and just extended support through 2037. A significant share of federal HR already runs on it. Oracle controlled much of the existing backbone and the migration path off it, rather than reinventing the wheel.
A 50-person, multi-agency review team picked Oracle because, against the actual requirements and ability to perform them, it was likely one of the best two options.
Those requirements weren't exotic: core HR and personnel actions, payroll and benefits integration, time and attendance, audit-ready reporting, self-service. Table stakes, not a wish list. Oracle should be able to win these on boring fundamentals and proven delivery.
The rollout structure reflects the same logic. Stand up a single canonical instance first, prove it works, then migrate agencies in deliberate waves. No one is flipping 119 systems at once. Sustainment is a named phase in this contract, not an afterthought.
The giant leap forward in a decade (or more) will be to a place where a lot of enterprise organizations were years ago. That sounds a lot less impressive than it actually is if it actually goes to plan.
4 Universal Truths for Enterprise HR to Contemplate
Admittedly, most enterprise HR systems aren’t the tangled and politicized mess that the OPM finds itself in. So what can HR leaders looking to transform their own organizations possibly get from this? There are a few universal truths that we’ll all see play out in real time.
Can a consolidation-only software thesis work at scale?
OPM's case for this program wasn't about objectively better HR software or adding AI to their systems.
It was about tech consolidation. One system of record and data quality that 119 fragmented systems across more than two million employees can never deliver.
If your business case for transformation is primarily about consolidation, it’ll be interesting to watch how agencies react to basically being able to do the same sorts of things but on a different platform.
What savings can consolidation of this magnitude actually deliver?
As the OPM was selling this, the greater than 90% cost reduction was met with skepticism. The figure seemed tailor-made for an environment of increased scrutiny for government programs.
The steady-state savings from fewer licenses, integrations and maintenance overhead are real. The skepticism is about the level of savings promised. Without a doubt, that 90% figure will come back to haunt OPM when the project inevitably goes over budget.
Engaged, But Not Convinced: What's Eroding Beneath Your Strongest Engagement Numbers
Watch Now
Retention Is a Communication Problem: New Data from 6,000+ Employees
Watch Now
Do Learning Programs Really Work? How to Turn Education Into Engagement In Healthcare
Watch Now
Fuel Your Front Line: Workforce Trends Shaping 2026
Watch Now
The migration costs, change management, parallel systems during each wave and long tail of edge cases that become custom work typically don't make it into the model that got the project funded. Eventually, we’ll all see what savings actually got produced.
Will OPM draw a hard line against agency exceptions?
What happens when every requesting unit's legitimate exception gets approved? Eventually you've rebuilt the fragmentation you set out to eliminate — and that cost savings figure looks more like a mirage than a budget oasis. The agency that asked for a waiver before things got started is only the first.
It’s like watching a Christmas tree grow. It starts with a single trunk. Then one small branch appears and then another. Eventually, you have created a more consolidated complexity that might not deliver on any of the promises, much less the budget one.
How well can OPM anticipate challenges before they derail the program?
The most useful document in this entire saga was written before anything failed.
Three former federal executives imagined how the program would collapse and worked backward. Seven failure modes that are more behavioral and situational: governance that can't decide, funding that can't be obligated, scope creep from the field or sponsorship that evaporates as the program becomes one initiative among many rather than the one that matters.
"The risks are not primarily technical," they concluded. "They are mostly governance risks, capacity risks, and incentive-alignment risks." Before you sign the next SOW, run the same exercise.
These questions show up in nearly every large HR transformation post-mortem written in the last two decades. What makes the OPM deal worth watching is that the warning signs are visible in real time (and in public), before anyone can claim they didn't see them coming.
Not Doomed to Fail: What Success Looks Like
Cynics tell us a project of this magnitude is a boondoggle from the start. That something this ambitious without an obvious and immediate pain-point is politically doomed. And maybe it is.
But one large federal HR consolidation has already shown it can work. In the early-2000s, a payroll consolidation combined more than 20 systems down to four shared-service providers, with roughly $1 billion saved.
What it had was two senior leaders, the OMB director and OPM director, who treated it as a personal management imperative and held that attention long enough to beat institutional and political resistance. Two people refused to let it fail.
That variable doesn't show up in a bid like this.
As of now, the OPM deal is entirely a plan. No agencies have migrated. The procurement story, messy as it was, will be a memory by the time the switch gets turned on for the first wave of transitions.
What comes next is an execution story, and execution is where failure shows up. Enterprise HR leaders should be watching that part.
Editor's Note: What else can derail digital transformation?
- The Antipatterns Blocking Your Future of Work Transformation — Ready for the future of work? First, dismantle the antipatterns holding your organization back — from top-down control to metrics that reward busy work.
- Escaping the Cave: Lead Your Team Through Digital Transformation — Plato's allegory of the cave is thousands of years old, yet it still feels relevant today in light of change management and transformation initiatives.
- What Happens to Digital Transformation When Management Is Stuck in the '90s — Change is happening fast, and some leaders are reluctant to embrace new technologies. Some steps to help bring legacy managers into the modern digital era.