recommended reading

Analysis: These Three Management Rules Helped Fix HealthCare.gov

Northfoto/Shutterstock.com

For weeks after its launch, HealthCare.gov could barely be accessed, let alone enroll Americans in health insurance exchanges. Its failure and rapid rescue, as detailed by Steven Brill in Time magazine, shows what a difference it makes when engineers are managed well.

On Oct. 17, a new engineering team—made up of external volunteers, temporary subcontractors, and engineers from contractor QSSI—started to form and the turnaround was remarkable. Mike Abbott, a Kleiner Perkins partner who was previously key in making Twitter reliable, was a volunteer present for the first critical week and participated in as many as two or more conference calls a day through December. It made a huge difference to have talent on board that had spent their career dealing with problems of this scale.

Some of the site’s six week turnaround was due to basic technology fixes, like adding a cache to speed up information requests. But many of the big changes were made in the culture of the work environment.

The team had a few rules posted on a wall outside their central operations center that guided their daily stand up meetings and approach, according to Mikey Dickerson, the Google engineer who lead the rescue squad:

Rule 1: “The war room and the meetings are for solving problems. There are plenty of other venues where people devote their creative energies to shifting blame.”

Rule 2: “The ones who should be doing the talking are the people who know the most about an issue, not the ones with the highest rank. If anyone finds themselves sitting passively while managers and executives talk over them with less accurate information, we have gone off the rails, and I would like to know about it.”

Rule 3: “We need to stay focused on the most urgent issues, like things that will hurt us in the next 24—48 hours.”

Six weeks after the turnaround was initiated, the site was up 95% of the time compared to just 43% in early November. It was eventually able to handle a massive traffic spike leading up to an important December deadline.

Many of the engineers who helped fix the site were private contractors who had helped create the disaster. All they needed was better management.

The problem, according to Brill, wasn’t with individual engineers, but rather the fragmented contracting companies that managed them. Silicon Valley gets a lot of flack for its occasionally inflated self-regard, but its people definitely know how to build big websites.

Republished with permission from Quartz. Read the original story here

(Image via Northfoto / Shutterstock.com)

Threatwatch Alert

Thousands of cyber attacks occur each day

See the latest threats

JOIN THE DISCUSSION

Close [ x ] More from Nextgov
 
 

Thank you for subscribing to newsletters from Nextgov.com.
We think these reports might interest you:

  • Featured Content from RSA Conference: Dissed by NIST

    Learn more about the latest draft of the U.S. National Institute of Standards and Technology guidance document on authentication and lifecycle management.

    Download
  • PIV- I And Multifactor Authentication: The Best Defense for Federal Government Contractors

    This white paper explores NIST SP 800-171 and why compliance is critical to federal government contractors, especially those that work with the Department of Defense, as well as how leveraging PIV-I credentialing with multifactor authentication can be used as a defense against cyberattacks

    Download
  • Toward A More Innovative Government

    This research study aims to understand how state and local leaders regard their agency’s innovation efforts and what they are doing to overcome the challenges they face in successfully implementing these efforts.

    Download
  • From Volume to Value: UK’s NHS Digital Provides U.S. Healthcare Agencies A Roadmap For Value-Based Payment Models

    The U.S. healthcare industry is rapidly moving away from traditional fee-for-service models and towards value-based purchasing that reimburses physicians for quality of care in place of frequency of care.

    Download
  • GBC Flash Poll: Is Your Agency Safe?

    Federal leaders weigh in on the state of information security

    Download
  • Data-Centric Security vs. Database-Level Security

    Database-level encryption had its origins in the 1990s and early 2000s in response to very basic risks which largely revolved around the theft of servers, backup tapes and other physical-layer assets. As noted in Verizon’s 2014, Data Breach Investigations Report (DBIR)1, threats today are far more advanced and dangerous.

    Download

When you download a report, your information may be shared with the underwriters of that document.