The key lessons of the Healthcare.gov fiasco
One of the advantages ZapThink brings to the discussion of Enterprise IT is our global perspective. As we travel the world, we hear the opinions of many people across many countries and industries. From this context we can confirm that most of the planet believes the US government is the laughing stock of the developed world.
First, we allow a fanatical right wing minority to shut down our entire government because they didn’t want American citizens to get affordable healthcare – even though most other developed countries consider healthcare a right rather than a privilege. We finally resolve the shutdown (at least temporarily) only to find that the centerpiece of the Affordable Care Act (ACA) rollout – the Healthcare.gov Web site – suffered from severe flaws. Seriously, can’t we get anything right?
The embarrassing failure of the ACA Web site is even more ironic considering the federal government’s long history of expensive, “big bang” IT projects like the Navy Marine Corps Intranet and the FBI Sentinel case management system that time and again failed in spectacular fashion.
We were supposed to have learned some important lessons from such fiascos. In fact, the Obama administration has made substantial progress turning over a new leaf in the rollout of large IT initiatives, focusing on more Agile, Service-Oriented, and Cloud-centric efforts that lower both risks and cost.
Why, then, did the Web site at the center of Obama’s centerpiece legislation fail so miserably, and how can we avoid such failures in the future?
Placing Healthcare.gov into context
Compared to other high-profile, complex federal IT programs, the ACA healthcare exchange program may have racked up the most program missteps for leadership and management in today’s IT world. On the other hand, other major government consolidation Web sites, such as USAJOBS and USAspending, have had significant IT problems as well. Revelations from key IT sources illustrate how immense the technology architecture and design problems are: missing or bad data, duplicate records, lack of audit controls, insufficient testing, and inadequate Cybersecurity controls, to name a few.
According to Aneesh Chopra, the first US Chief Technology Officer, the site’s problems were due to heavy traffic. It was built for 60,000 concurrent users – an estimate based on the Medicare.gov site of 30,000 daily users. However, Healthcare.gov had to support one million simultaneous users out of the gate. Also, the former CTO points to a minor Private Cloud scalability issue and a few additional IT missteps.
In a similar vein, the Health and Human Services (HHS) Secretary’s comments focused on the huge success of the new program – success that caused unexpectedly heavy traffic each day and few glitches.
And yet, many insurance and technology leaders, analysts, Web developers, and contractors have pointed out serious IT methodology, architecture design and security flaws with the Healthcare.gov Web site as long ago as early 2012. These central IT challenges focus on leadership, management, architecture, cost management, IT workforce issues, and stakeholder decisions and roles.
This IT program appears to have fallen apart due to a number of requirement changes within two weeks of product launch from the administration. Such last minute changes introduce substantial risks into any IT project. All critical production systems should ideally have hard lead times and freeze dates, in conjunction with an iterative, Agile methodology for such changes to be successful. For example, the IRS has a similar IT playbook for new tax laws every year as many commercial firms do.
How to fix Healthcare.gov
The number of critical technology areas that have been failing and the risk of skipping full operational and Cybersecurity testing and review place this application at high risk. The exchange portal needs an IT rescue or reset, which would involve taking the site down for application overhaul.
It may require as many as 5 million lines of software code to be ripped out and replaced to avoid inaccurate enrollment data and improper payments for services, mitigating further costly recovery. It should also have a full architecture review and be retested for data quality with key stakeholders, security for accessing other federal databases, as well as security for citizen privacy and data protection from hackers for identity fraud and misuse.
Key IT takeaways on this effort for any organization, federal or private, include:
Executive teams should be flexible on critical product rollout dates and execute strong leadership using governance for accountability and transparency over requirement changes and risks to avoid program chaos on cost, schedule, Cybersecurity, quality, and usability.
Executive leadership must have common product communication messaging on the purpose and value to all levels of the organization, stakeholders, and customers for accepting the product with confidence and trust.
EA teams should have crafted an Agile Enterprise Architecture using a Cloud roadmap for driving the business needs today, as well as future requirements for improving customer satisfaction and usability.
Executive and IT leadership decisions to insource complex integration architecture must be evaluated with the right team level of skill mix, training and resources, and leadership must be willing to outsource resources for any skill gaps.
Procurement teams should use trusted partnerships with core domain, Agile Architecture, and project management (PM) skills as well as corporate or government-wide multiple award contracts with task orders for critical skills by best of breed contractors with key domain experience for Agile software development.
Agile IT PM teams should have a standard or tailored software development lifecycle including a prototype phase for proof of concept with field ops for network stress on the architecture and security testing using incremental releases for production.
IT PM teams should have leveraged key stakeholder sign-offs, domain tailored best practices, customers/users/advocacy testing groups, or other testing offerings to validate a new product.
Using a Web-based portal solution for a healthcare gateway to existing federal agencies’ databases and insurance interfaces for data sets with unpredictable scalability requirements are common IT challenges in today’s market that newer technologies, in particular, Cloud Computing, can address.
On Healthcare.gov, the key executive strategy teams lacked the technical skills and the proper executive governance framework for oversight on the program’s execution effort. A delivery mandate, regardless of the end state of the product and “deliver as is” wording, puts the citizens or other users in a dysfunctional IT service environment, which creates lack of trust and confidence in the healthcare portal going forward.
If we compared this project rollout with any large private sector organization rollout, it would have been shut down immediately to mitigate the unknown costs and risks, the damage to the brand and reputation of the organization, and the leaders who are accountable would have taken appropriate management actions. In fact, it should not have led to a rollout date using a “big bang” deployment in the first place.
The ZapThink take
The Administration’s 2012 OMB policy dictates the use of Agile software modular development using incremental releases to avoid the long delays for customer phase-in for smaller deployments (30 to 180 days), and early use of features and benefits to reduce risk from poor requirements, untested technology, software failures, and cost overruns. However, by all accounts, Healthcare.gov was executed as a waterfall project, an approach that almost always leads to failure – either by insufficiently delivering on requirements or by providing inadequate focus on quality.
And sure enough, these are just the problems that Healthcare.gov faced. We know the US government can succeed with Agile, even on large initiatives – ZapThink’s parent company, Dovel Technologies, has successfully leveraged Agile on sizable projects for the Food and Drug Administration (FDA), among others.
Why, then, did the government and its contractors not follow a best practice Agile approach? Fundamentally, Agile requires a rethink of the organizational aspects of planning, delivering, testing, and managing any IT project. The entire effort must be tackled iteratively. Stakeholders should be involved at every step. Testing must take place in every iteration, in order to lessen the testing burden as the initiative approaches delivery.
For larger initiatives like Healthcare.gov, the architecture must be Agile as well – both the software architecture as well as the broader Enterprise Architecture. However, the principles for Agile Architecture are only now being fleshed out, as ZapThink explains in Jason Bloomberg’s book, The Agile Architecture Revolution. As the word revolution would indicate, no band-aid fix will magically turn big-bang software fiascos into lightweight, Agile, customer-focused initiatives. Instead, we must entirely rethink how we go about software delivery to meet the IT challenges of the 21st century. There is simply no excuse for high risk waterfall initiatives any more, at the federal government or anywhere else.
Guest Author: Steve Hawald, Executive Partner/Analyst
Prior to founding HAWALD ADVISORY, LLC in 2013, Mr. Hawald was a former Gartner global IT research analyst, US Department of Education / SFA CIO, and United HealthCare HMO Divisional CIO. He was named to Hitachi’s Federal Data Systems advisory board in early 2010, and was appointed to Georgetown University’s CCPE adjunct faculty for graduate IT certificate programs in 2009. He teaches part-time on weekends at the DC campus with his advisory engagements. He currently attends Virginia Tech University for STS PhD studies in risk challenges and management.
- » How to improve supply chains with machine learning: 10 proven ways
- » What automation can learn from DevOps – and why the future is automation with iteration
- » AWS announces availability of Amazon Managed Blockchain service
- » Enterprises rethinking their Oracle relationships, argues Rimini Street
- » Re-host, re-platform or replace: Which public cloud approach is right for your business?