The launch of healthcare.gov has brought a tidal wave of criticism. Some say the code was buggy, others blame the servers, and still others blame the user experience. While we may not be able to pinpoint exactly what went wrong, one thing is certain: What should have been a great day for many Americans became the worst day for the technology providers behind healthcare.gov.
But healthcare.gov isn’t the only site to experience a bad launch day; it just happens to be the latest example of how a site that goes live before it’s ready can cause more harm than good. When we only look at technology projects in terms of code and hardware, we are setting ourselves up for failure. Technology projects should support the people, the projects, and the objectives of the mission they are being built to support.
With that in mind, Jessica Richmond, senior director of Government Professional Services at Acquia, has put together some tips for site developers to ensure that when a site gets the green light to go live, it’s ready for peak performance, regardless of the amount of traffic it may experience.
The median for the top 500 e-commerce home pages took 10 seconds to load. In spring 2012, the median loaded in 6.8 seconds, a 47 percent slowdown. ... More >>
IoT examples can be categorized into four basic usage scenarios, each of which presents clear business opportunities for end-user organizations. ... More >>
The use of social engineering to distribute malware continues to account for the bulk of cyber attacks against consumers and enterprises, thereby making a browser's ability to protect against these kinds of attacks an important criterion for personal or corporate use. ... More >>