Indiana welfare-eligibility system failure
Indiana's attempt to automate its welfare-eligibility system with IBM led to wrongful benefit denials and delays for tens of thousands of residents; the state cancelled the roughly $1.3 billion, 10-year contract early amid lawsuits and public outcry.
The damage was public. The root cause was preventable.
Indiana's attempt to automate its welfare-eligibility system with IBM led to wrongful benefit denials and delays for tens of thousands of residents; the state cancelled the roughly $1.3 billion, 10-year contract early amid lawsuits and public outcry.
What the software actually got wrong
The automated system removed caseworkers' direct relationships with applicants in favor of call centers and document scanning, and the underlying software could not reliably process the wide variety of individual circumstances that human caseworkers had previously handled, generating large numbers of erroneous denials.
The automated system removed caseworkers' direct relationships with applicants...
The automated system removed caseworkers' direct relationships with applicants in favor of call centers and document scanning
Requs AI Edge Case flags this exact pattern at the requirements and architecture stage — before a single line of code implementing it exists — so the assumption behind it gets challenged while it is still cheap to fix.
The underlying software could not reliably process the wide...
the underlying software could not reliably process the wide variety of individual circumstances that human caseworkers had previously handled, generating large numbers of erroneous denials
Requs AI Software FMEA traces this failure mode back to the system-level hazard it feeds, tagging it against the Common Defect Enumeration so it surfaces in review instead of in the field.
Beyond code coverage and "shall" testing
Root causes like this one rarely show up in code coverage or requirements-compliance testing, because nobody wrote a requirement anticipating the specific edge case that broke. Requs AI Edge Case and Requs AI Software FMEA are built to surface exactly this class of overlooked failure mode — before the software is written.
Surfaces this before code exists
Identifies edge cases like this one at requirements and architecture time, using the Common Defect Enumeration to catalog failure patterns seen across hundreds of real-world software failures — including this one.
Connects the failure mode to the hazard
Traces this class of root cause directly to the system-level hazard it can produce, so a defect pattern like this one gets flagged during design review instead of after it ships.
Find the overlooked root causes before they ship.
Schedule a demonstration, or explore how Requs AI Edge Case and Software FMEA use the Common Defect Enumeration.