In case you've been living under a rock or trying to avoid the NSA reading your email for the last couple of months, you've probably heard about the healthcare.gov "disaster". News flash for anyone who is not "in the business" or has never worked on an system anywhere near the scale of healthcare.gov -- this is normal. And it's not about technology, it's about process:
As Matt Asay points out in his post:
But it is important to note that while the implication here is that "operating in secret" is a "bad thing", it is also how most every private enterprise has the luxury of operating. I assure you, if every enterprise launch went through the same level of public scrutiny that healthcare.gov has seen lately we would see a lot less media hand-wringing going on about "technology failures" than we see today.
Title: I wanted a point application, I didn't mean one that assigns blame.
As Matt Asay points out in his post:
"HealthCare.gov failed not so much because of its code, but rather because of how it was assembled and rolled out: in secret."
But it is important to note that while the implication here is that "operating in secret" is a "bad thing", it is also how most every private enterprise has the luxury of operating. I assure you, if every enterprise launch went through the same level of public scrutiny that healthcare.gov has seen lately we would see a lot less media hand-wringing going on about "technology failures" than we see today.
Title: I wanted a point application, I didn't mean one that assigns blame.
Snarky: At least it doesn't make you testify in front of the Senate.
No comments:
Post a Comment