Abstract:

This presentation analyzes the initial failure of Healthcare.gov, the online marketplace launched under the Affordable Care Act (ACA), and its subsequent recovery. It begins by providing context on the US healthcare system and the ACA's goal of providing subsidized insurance. The core of the discussion focuses on the systemic issues leading to the website's disastrous October 2013 launch, including a severely compressed timeline, a lack of end-to-end testing, and a dysfunctional attempt at implementing an Agile software development model. Constant changes in policy requirements, a fixed launch date despite development challenges, and leadership's failure to grasp the project's poor status are highlighted as critical factors. The presentation then details the recovery efforts, which involved high-level political intervention, a "Silicon Valley team" rescue, and a significant shift in workplace culture to prioritize quality, simplified processes, and collaboration, ultimately leading to the establishment of the US Digital Service.

Summarizing the Healthcare.gov Launch Failure and Recovery

• 0:00:05 Introduction to Healthcare.gov: Staca Roberts from Yale College introduces the topic, focusing on Healthcare.gov and its initial launch failures.
• 0:00:20 Healthcare Context & ACA:
  • Explains various healthcare payers in the US: private, employer-provided, social safety nets (Medicare/Medicaid), government-provided (veterans), and out-of-pocket.
  • Introduces the Affordable Care Act (ACA) as a reform act providing subsidized insurance to the uninsured.
  • Healthcare.gov was designed as a marketplace for individuals to purchase ACA insurance.
• 0:01:13 Initial Launch Issues: A news clip highlights that the entire Healthcare.gov system was not tested "end-to-end" until just two weeks before its public launch on October 1st, 2013.
• 0:01:44 Project Timeline Problems:
  • 2011: Funding allocated.
  • Early 2013: First system requirements created.
  • October 1, 2013: Product launch, giving only about 9 months for development.
  • Key Takeaway: There was virtually no stress testing, and the end-to-end testing was critically delayed. The timeline was fixed, allowing no flexibility for development issues.
• 0:02:24 Failed Agile Implementation:
  • Healthcare.gov attempted an Agile model but failed due to constant changes in business and technical requirements by policymakers, often rendering completed components outdated.
  • Key Takeaway: The Department of Health and Human Services (HHS) failed to enforce a "done is done" principle, leading to constant re-visiting of components and developer desensitization.
• 0:03:26 Launch Day Failures:
  • Experienced five times the expected traffic, with 250,000 attempts to log on.
  • Only six successful sign-ups on the first day.
  • By end of October, only 26,794 sign-ups were achieved, 10% of the goal.
• 0:03:59 Detailed Issues (OIG Report - Feb 2016):
  • Agile model's flexibility led to frequent and late changes.
  • Compressed timeline (9 months for technical build) was insufficient.
  • Attempts to resolve issues were "too little and too late," exacerbated by delayed end-to-end testing.
  • Leadership failed to grasp the poor status of the website and alter course.
  • Contractors prioritized on-time delivery over crucial testing and issue resolution.
  • Key Takeaway: Delaying the project was never seriously considered, which was identified as the biggest issue preventing adequate testing.
• 0:05:33 Aftermath and Recovery:
  • Daily meetings involved President Obama and the Secretary of HHS.
  • A "Silicon Valley team" was brought in to rescue the website.
  • Workplace Culture Shift:
    • Moved to a "badges culture" (more horizontal structure without rigid leadership chains).
    • Prioritized quality over meeting deadlines, enabling more thorough testing.
    • Simplified overall development processes.
  • 0:06:21 US Digital Service (USDS): The Office of Management and Budget established the USDS in 2014 to simplify digital services delivery, a direct outcome of the Healthcare.gov experience.
• 0:06:31 Conclusion: Emphasizes the critical importance of planning and organization in large software projects, not just coding.