Why US government IT fails so hard, so often
The rocky launch of the Department of Health and Human Services' HealthCare.gov is the most visible evidence at the moment of how hard it is for the federal government to execute major technology projects. But the troubled “Obamacare” …
Context & Ripple Effects
HealthCare.gov's botched debut is not an isolated stumble: two weeks earlier, TechCrunch documented the Obamacare websites failing amid the government shutdown, so the portal's collapse landed while the program was already a political target. Ars Technica's framing treats it as a symptom rather than a bug — the latest instance of a confirmed pattern in which the federal government repeatedly fails to execute major technology projects.
That pattern has history in the corpus: back in May 2010, the government tapped ChallengePost to help launch its open-government initiatives, an early attempt to import outside building practices into federal work. The story's reach signals how far the frustration travels — the New York Times ran its own account of financial, technical and managerial missteps behind the health-portal troubles, and the rollout drew commentary from a broad set of high-profile voices across social platforms.
First-order effects
- HHS faces immediate pressure to stabilize HealthCare.gov during the open-enrollment window, with the site's technical failures now directly blocking the policy's core sign-up mechanism.
- The contractors and managers behind the build come under public scrutiny, as the New York Times' parallel reporting attributes the troubles to financial, technical and managerial missteps rather than a single point of failure.
Second-order effects
- Every agency planning a large citizen-facing system inherits a harder approval environment, as a visible failure of this size makes officials more cautious about monolithic outsourced builds.
- Vendors competing for federal work face a market repricing: buyers who just watched a flagship portal fail have stronger incentives to demand staged delivery and proven execution over long fixed-scope contracts.
Third-order effects
- If repeated megaproject failures keep producing political damage, pressure builds toward restructuring how Washington acquires software — smaller increments, in-house capability, and accountability tied to working systems rather than milestones.
- A persistent execution gap between federal ambition and federal delivery capacity risks becoming a standing constraint on policy design itself, with agencies shaping programs around what their IT machinery can reliably ship.
The trend: Federal technology delivery is becoming a recurring political liability, with each high-profile portal failure adding pressure to overhaul how the government buys and builds software.