9 Comments

Summary:

Foundry Group managing director Brad Feld says that instead of bringing in more tech talent to fix the ailing HealthCare.gov, the government should take the site offline and launch it again with new leadership.

Brad Feld, Foundry Group Thumbnail

To fix the glitch-ridden website for the government’s new health insurance marketplace, President Barack Obama and the Department of Health and Human Services said they’re mounting a “tech surge” of talent to help address the problems. But in a blog post, investor and entrepreneur Brad Feld said he thinks this is “exactly the wrong thing to do.”

Citing engineer and The Mythical Man-Month author Frederick Brooks, he said adding more engineers to an already delayed project tends to only further stall progress. Instead, he suggests taking all of the health exchange sites offline, setting a new launch date for July 2014, firing all of the contractors and hiring former Obama for America CTO Harper Reed as CTO of HealthCare.gov.

Feld (who will be one of the speakers at a GigaOM meetup tonight in Denver) isn’t the only skeptic of the tech surge. Despite President Obama’s attempts to downplay the website’s problems as mere “kinks,” other IT experts have said they believe the site’s issues reveal deeper issues with its underlying architecture and that adding more programmers could slow things down.

  1. =) and all while mercury is retrograde. good. then maybe we can discuss the real issue no one really wants to discuss — the fact that the intention of the act is not to provide quality healthcare to americans. oh, sure, they may say that, but the design and structure of the Act belies that imprinted intention.

    Share
  2. Alchemy Tech Solutio Tuesday, October 22, 2013

    lol I think this maybe a conspiracy by the programmers to delay obamacare.

    Share
  3. New leadership? I don’t think it’s realistic to expect President Obama to resign. ;-)

    Share
  4. I wonder how all these “tech experts” know what’s wrong with healthcare.gov if they don’t work on the project, haven’t reviewed the code, seen the error messages, etc. Where I work, bugs are systematically diagnosed by technicians, not by customers or industry analysts. How about we let the engineers diagnose, report and repair. Then we can all play Monday morning quarterback and tell everyone what to do.

    Share
    1. I think it may be a conspiracy to avoid people getting the results!

      Share
    2. I’ve not seen much reporting yet. The obviously know what is wrong by now and are not sharing which of course will lead to speculation and Monday morning quarterbacking.

      Share
    3. You can review the front end code yourself. Just load the page in your browser. It is appalling. Brad Feld is correct. It needs to be put down and taken out of its misery.

      Share
  5. And I suspect if this wasn’t the biggest political hot potato of the last 25+ years there’s a chance that might follow Brad’s advice. However……

    Share
  6. This gigantic system was rushed into being. It’s 500 million lines of code by some 55 different suppliers and nowhere near enough integration. They basically (no pun intended) need to take it apart, test the pieces, then put it back together a piece at a time, making sure each piece is properly integrated. Each time they add a piece, the testing necessarily gets a little more elaborate and time-consuming — if they do it right. Most of all they need leadership with the authority to solve conflicts on the fly. Remember the FBI’s attempt to automate its internal information flow?

    It’s possible government doesn’t know how to think big enough to truly integrate a bureaucracy made up of entrenched fiefdoms, nodes of expertise and special applications, and an awkward mix of careerists and political appointees in management.

    Share

Comments have been disabled for this post