recommended reading

Analysis: These Three Management Rules Helped Fix


For weeks after its launch, 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 /

Threatwatch Alert

Stolen laptop

3.7M Hong Kong Voters' Personal Data Stolen

See threatwatch report


Close [ x ] More from Nextgov

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

  • It’s Time for the Federal Government to Embrace Wireless and Mobility

    The United States has turned a corner on the adoption of mobile phones, tablets and other smart devices, outpacing traditional desktop and laptop sales by a wide margin. This issue brief discusses the state of wireless and mobility in federal government and outlines why now is the time to embrace these technologies in government.

  • 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.

  • A New Security Architecture for Federal Networks

    Federal government networks are under constant attack, and the number of those attacks is increasing. This issue brief discusses today's threats and a new model for the future.

  • Going Agile:Revolutionizing Federal Digital Services Delivery

    Here’s one indication that times have changed: Harriet Tubman is going to be the next face of the twenty dollar bill. Another sign of change? The way in which the federal government arrived at that decision.

  • Software-Defined Networking

    So many demands are being placed on federal information technology networks, which must handle vast amounts of data, accommodate voice and video, and cope with a multitude of highly connected devices while keeping government information secure from cyber threats. This issue brief discusses the state of SDN in the federal government and the path forward.

  • The New IP: Moving Government Agencies Toward the Network of The Future

    Federal IT managers are looking to modernize legacy network infrastructures that are taxed by growing demands from mobile devices, video, vast amounts of data, and more. This issue brief discusses the federal government network landscape, as well as market, financial force drivers for network modernization.


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