Posted: October 28, 2013
Four easy steps to fix Obamacare
A "tech surge" isn't the answerBy Brad Feld
Now that our federal government is back at work and the short term debt ceiling thing is resolved, it should be no surprise that the news cycle is now obsessed with Obamacare and its flawed implementation. I must have seen a dozen articles about this online and in the New York Times, and then I woke up this morning to a bunch of new things about the Healthcare.gov site underlying tech, how screwed up it is, and what / how the Health and Human Services agency is going to do to fix it.
The punch line – a tech surge.
To ensure that we make swift progress, and that the consumer experience continues to improve, our team has called in additional help to solve some of the more complex technical issues we are encountering.
Our team is bringing in some of the best and brightest from both inside and outside government to scrub in with the team and help improve HealthCare.gov. We’re also putting in place tools and processes to aggressively monitor and identify parts of HealthCare.gov where individuals are encountering errors or having difficulty using the site, so we can prioritize and fix them. We are also defining new test processes to prevent new issues from cropping up as we improve the overall service and deploying fixes to the site during off-peak hours on a regular basis.
From my perspective, this is exactly the wrong thing to do. Many years ago, I read Fredrick Brooks iconic book on software engineering – The Mythical Man-Month. One of his key messages is that adding additional software engineers to an already late project will just delay things more. I like to take a different approach – if a project is late, take people off the project, shrink the scope, and ship it faster.
I think rather than a tech surge, we should have a “tech retreat and reset.” There are four easy steps.
- 1. Shut down everything including taking all the existing sites offline.
- 2. Set a new launch date of July 14, 2014.
- 3. Fire all of the contractors.
- 4. Hire Harper Reed as CTO of Healthcare.gov, give him the ball and 100 percent of the budget, and let him run with it.
If Harper isn’t available, ask him for three names of people he’d put in charge of this. But put one person – a CTO – in charge. And let them hire a team – using all the budget for individual hires, not government contractors or consulting firms.
Hopefully, the government owns all the software even though Healthcare.gov apparently violates open source licenses. Given that, the new CTO and his team can quickly triage what is useful and what isn’t. By taking the whole thing offline for nine months, you aren’t in the hell of trying to fix something while it’s completely broken. It’s still a fire drill, but you are no longer inside the building that is burning to the ground.
It’s 2013. We know a lot more about building complex software than we did in 1980. So we should stop using approaches from the 1980s, admit failure when it happens, and hit reset. Doing a “tech surge” will only end in more tears.
Brad has been an early stage investor and entrepreneur for more than 20 years. Prior to co-founding the Boulder-based Foundry Group, he co-founded Mobius Venture Capital and Intensity Ventures, a company that helped launch and operate software companies. Brad is a nationally recognized speaker on the topics of venture capital investing and entrepreneurship and writes widely read and well respected blogs at www.feld.com and www.askthevc.com. He holds bachelor's and master's of science degrees from from MIT. Contact him at firstname.lastname@example.org