October 21st, 2013 10:10 pm by Vincent Flanders
Vincent Flanders’ comments: C’mon, you knew I had to do it even though the year isn’t over. How could I NOT name HealthCare.gov as the Worst Website of 2013?
If you can spell “web design,” you know you’re supposed to test your website before it goes live. Testing it for the first time one week before launch does not count as testing. Even my mother, who spent most of her career as a keypunch operator, knows better than to wait until the last minute to test a website and she’s been dead for 20 years.
If a corporate website sucks or fails to work, employees are the people who are usually hurt (I’m over-simplifying a bit). When a nonprofit website sucks or fails to work it hurts a larger group of people outside the company – the clients they’re trying to help – and these people are generally already hurting or they wouldn’t need the non-profit’s services. It’s more important for a non-profit website to “get it right.”
That’s why it’s so upsetting that HealthCare.gov doesn’t work. This website’s failure will hurt real people and, dammit, government is supposed to help people. (Yeah, yeah, yeah. We can argue about government’s role in helping people another day.)