Slow change is becoming Medicaid’s next big risk

I’ve spent much of my career between two worlds that don’t always speak the same language: the public sector, where the consequences of our decisions are deeply human, and the private sector, where we’re constantly challenged to move faster, rethink assumptions and build what comes next.

For years, Medicaid modernization work has focused on replacing legacy technology. That remains important, but newer technology doesn’t necessarily make a system easier to change. And today, that distinction matters. 

In 2026 alone, states are navigating new Medicaid Enterprise System requirements, evolving interoperability and prior-authorization obligations, and preparations for significant eligibility and operational changes taking effect in 2027. The details vary, but the challenge is the same: agencies must respond quickly while keeping critical programs and services running reliably. 

That’s why I believe quick change has become an important measure of modernization. Agencies need systems that can accommodate new rules, workflows and reporting requirements without turning every adjustment into a large-scale technology effort.  

Modernization shouldn’t simply help states replace what they have today. It should give them greater flexibility to respond to what comes next. 

Related: What's next is now: Medicaid’s new chapter has begun 

The value of quick change 

At MESC this year, while meeting with my public sector colleagues serving Medicaid, I heard variations of the same challenge again and again. States know more change is coming, but they may not know exactly what the next policy requirement, operational priority or technology shift will be, but they do know they’ll be expected to respond, and they will likely be expected to respond quickly. 

Our colleagues don’t wake up in the morning hoping only for more modularity. They want to make a change without setting off a disastrous chain reaction across the enterprise. They want to adjust a rule without beginning an 18-month technology project, and they want systems that move with them. 

That’s why my teams prefer a simpler phrase: quick change. 

To me, quick change is what modernization should ultimately deliver. It’s the ability to respond to a new policy, configure a process, change a workflow or introduce a new capability without unnecessary disruption to everything around it. 

As my colleague Shanker Balakrishnan recently discussed, the challenge for Medicaid is building systems that can respond quickly as policies, program requirements, compliance demands and technology continue to change. That requires a stronger foundation built around flexibility, trusted data, practical AI and governance that helps agencies adapt without creating unnecessary disruption. 

Related: AI - Powered Medicaid Service Authorization Module 

What quick change looks like in practice 

New Mexico offers a good example of what this approach can look like at scale. The New Mexico Health Care Authority serves nearly 900,000 Medicaid members through its Turquoise Care program and works with a provider community of about 94,000. As program demands grew, the state set out to replace a 24-year-old Medicaid Management Information System and create a more connected, responsive Medicaid enterprise. 

Earlier this year, our teams deployed Conduent Medicaid Suite, a cloud-based platform designed to allow capabilities to evolve incrementally as the state’s needs change. 

The results help illustrate why quick change matters. New Mexico can now implement some policy updates in days rather than months, while live dashboards provide greater visibility into claims, encounter data and budget performance. Real-time eligibility checks help accelerate claims processing and provider payments, and stronger third-party liability identification helps reduce unnecessary expenditures and protect funding for member care. 

And this flexibility is operating at significant scale, supporting more than 470,000 managed care encounters and 106,000 fee-for-service claims each week, with 234 integrations across the Medicaid ecosystem. 

We should expect more from our systems  

Some of the constraints Medicaid leaders deal with today have been part of the landscape for so long that they can begin to feel inevitable. A policy change may require extensive coding, a seemingly contained adjustment can affect multiple systems, and adding a new capability can turn into a lengthy technology effort. Agencies are often left trying to balance the need to move quickly with an equally important responsibility to protect stability, compliance and continuity. 

Those are real considerations, but we should be careful not to assume that the tradeoffs of the past have to define what is possible today. A more adaptable financial model, for example, should be able to respond as reporting, funding and oversight requirements evolve without forcing agencies into large-scale changes every time a requirement shifts. Claims systems should make it easier to adjust rules and processes without rebuilding substantial portions of the environment around them. And provider systems should simplify not only enrollment, credentialing, revalidation and ongoing management, but also the work required to change those processes as programs evolve. 

The provider model needs to evolve as well 

The same thinking should apply to the companies that serve government. We can’t talk seriously about building more adaptable Medicaid systems while assuming that the provider model itself should remain unchanged. A newer platform doesn’t automatically make a company future-focused, particularly if the way it works with customers still reflects the same assumptions about long timelines, difficult changes and rigid delivery models. 

The provider of the future needs to understand the complexity of Medicaid deeply, while also being willing to question whether that complexity always has to translate into slow or difficult change. Decades of experience are enormously valuable, but experience is most useful when it helps us distinguish between what truly cannot change and what has simply been done the same way for a long time. 

At Conduent, this is already how we are approaching the market. We’re applying decades of experience supporting complex government programs while building financial, claims and provider models designed for greater configurability, faster response and quick change as agency needs evolve.

Rethinking what disruption means 

We can’t know every policy, regulatory or operational change Medicaid agencies will encounter in the years ahead, and I don’t believe modernization should depend on our ability to predict them. What we can do, though, is design financial, claims and provider models around the reality that change will continue, and make it easier for agencies to respond when it does. 

For me, that is what quick change ultimately means: creating systems and partnerships that can evolve with the programs they support, without asking agencies to choose between moving forward and keeping what already works.