Almost every health and human services agency is carrying technical debt measured in decades. Eligibility engines written in COBOL, case management systems that predate the smartphone, integrations held together by nightly batch files. Everyone agrees it needs to change. So why do so many modernization programs stall, overrun, or quietly fail?
The trouble with big-bang replacements
The instinct is to replace the whole system at once. It feels decisive, and it's easy to put in a single procurement. But a multi-year, all-or-nothing rewrite concentrates risk at exactly the wrong moment — the cutover — when the people who depend on benefits can least afford an outage.
- Requirements drift faster than a multi-year build can absorb them.
- Value only arrives at the very end, so problems surface too late to fix cheaply.
- A single cutover means a single, high-stakes point of failure.
- Institutional knowledge walks out the door before the new system lands.
Strangle the legacy system, don't replace it
We favor the strangler-fig pattern: stand a modern platform up alongside the legacy system and migrate one capability at a time. Each slice — renewals, then notices, then appeals — runs in production and delivers value on its own. The legacy system shrinks until there's nothing critical left to retire.
Modernization isn't a destination you reach at go-live. It's a capability you build into the organization so the system never ossifies again.
Prove value in the first 90 days
A modernization program should put working software in front of real users within a quarter — even if it's a single workflow. Early delivery converts skeptics, surfaces integration surprises while they're still cheap to fix, and gives leadership something concrete to defend at budget time.
What good looks like
- A roadmap organized around resident and caseworker outcomes, not modules.
- Continuous delivery with automated security and accessibility checks.
- Open APIs so each new capability interoperates from day one.
- Knowledge transfer that leaves your team able to run and extend the system.
Done this way, modernization stops being a bet-the-agency gamble and becomes a steady, measurable march — one shipped slice at a time.
Modernizing a health or human services program?
We help agencies turn ideas like these into systems that ship. Let's talk about your mission.
Partner with us