HealthCare.gov: The Crash and the Fix (A) Custom Case Solution & Analysis

1. Evidence Brief (Case Researcher)

Financial Metrics

• Project Budget: Initial estimates for the Federal Marketplace IT system were approximately $174M, eventually ballooning to over $800M by October 2013 (Source: Paragraph 4).
• User Traffic: The site was designed to handle roughly 50,000 concurrent users. On launch day (October 1, 2013), it received 2.8 million visits, but only 6 individuals successfully enrolled (Source: Paragraph 12).

Operational Facts

• Governance Structure: The project involved multiple agencies (CMS, HHS, White House) and over 50 contractors. No single entity held ultimate technical authority (Source: Paragraph 8).
• Development Methodology: The project shifted from a traditional waterfall model to an agile-like approach mid-stream, but without the cultural or structural support for iterative testing (Source: Paragraph 15).
• System Architecture: The system relied on an unproven identity-proofing service (Experian) that became a primary bottleneck (Source: Paragraph 19).

Stakeholder Positions

• Kathleen Sebelius (HHS Secretary): Publicly took responsibility for the failure while facing intense Congressional scrutiny.
• Jeff Zients (White House appointee): Brought in as a fixer to lead the tech surge. Focused on establishing a command-and-control structure.
• Contractors (CGI, Optum): Deflected blame to CMS requirements creep and lack of defined specifications.

Information Gaps

• Specific breakdown of individual contractor performance metrics versus CMS management failures.
• Internal documentation regarding the decision-making process behind the launch date (October 1) despite known testing failures.

2. Strategic Analysis (Strategic Analyst)

Core Strategic Question

How can a massive, failing government IT infrastructure project be stabilized while maintaining the political mandate of the Affordable Care Act?

Structural Analysis (Value Chain / Governance)

• Governance Fragmentation: The project suffered from the absence of a Chief Technology Officer. Decision-making was diffused across political appointees, leading to a focus on deadlines over system stability.
• Requirement Instability: Constant changes in CMS policy requirements prevented contractors from finalizing code, leading to late-stage integration failure.

Strategic Options

• Option 1: The Tech Surge (Selected): Assemble a strike team of private-sector experts to fix the code, centralize command, and stabilize the front-end. Trade-off: High political risk if the fix fails; requires ceding control to non-government personnel.
• Option 2: Staged Rollout: Shut down the site and re-open in phases. Trade-off: Avoids technical collapse but creates a massive political crisis regarding the viability of the ACA mandate.
• Option 3: Contractor Replacement: Terminate current contracts and bring in new vendors. Trade-off: Ensures long-term quality but causes immediate, irreversible delays in the enrollment window.

Preliminary Recommendation

Option 1 is the only viable path. The political cost of delay (Option 2) or the operational cost of vendor transition (Option 3) exceeds the risk of an aggressive, centralized repair effort.

3. Implementation Roadmap (Implementation Specialist)

Critical Path

• Phase 1 (Days 1-14): Establish a war room. Mandate daily stand-ups between CMS and contractors. Freeze all new requirements.
• Phase 2 (Days 15-45): Load testing and bottleneck elimination. Focus specifically on the identity-proofing service and account creation latency.
• Phase 3 (Days 46-90): Iterative deployment of fixes with automated monitoring to prevent regression.

Key Constraints

• Communication Silos: Contractors are not talking to one another. The war room must force transparency.
• Technical Debt: The codebase is brittle. Any fix risks breaking existing modules.

Risk-Adjusted Implementation

Success depends on the willingness of the CMS leadership to ignore political optics and focus on server stability. We must assume a 30% failure rate for initial code patches and maintain a rollback capability for every update.

4. Executive Review and BLUF (Executive Critic)

BLUF

The failure of Healthcare.gov was not a technical glitch; it was a governance catastrophe. The project lacked a single authority, clear specifications, and a culture of accountability. The recovery plan must prioritize the consolidation of technical authority under a single project lead who has the power to override political deadlines. The current path of the tech surge is correct, but the team must move from a project management mindset to an incident response mindset. If the system is not stable within 60 days, the political legitimacy of the administration will be permanently compromised. The primary goal is not perfection, but basic functionality to meet the enrollment mandate.

Dangerous Assumption

The assumption that the existing contractor base can be fixed without a change in incentives. The current model rewards status quo maintenance rather than performance-based delivery.

Unaddressed Risks

• Security Vulnerability: Rapid, uncoordinated patching may introduce severe data security flaws.
• Public Trust: Even with a fixed site, the initial failure has created a negative feedback loop that may depress enrollment numbers regardless of technical success.

Unconsidered Alternative

Public-Private Partnership (PPP) pivot: Directing users to existing, functional state-level exchanges while the federal site is rebuilt from the ground up as a secondary, rather than primary, enrollment tool.

Verdict: APPROVED FOR LEADERSHIP REVIEW