New Posts
  • Hi there guest! Welcome to PoliticalJack.com. Register for free to join our community?

Question for Liberals

Arkady

President
I don't expect intelligent discussion of this from conservatives, so I'm directing it specifically at liberals. What went wrong with the Obamacare website? Has anyone followed it closely enough to have a feel for it?

I mean, it's not like the concept itself is unworkable: we have plenty of other working exchanges at the state level, including an extremely large one in California. Those state exchanges are mostly working with no more glitches than you'd expect for any complicated IS system. Nor was this the product of some sort of overly ambitious schedule -- the delay between passage of the law and opening of the website was considerably longer than a similar period when Massachusetts did pretty much the exact same thing at the state level (and Massachusetts didn't have a prior roll-out to learn from). So this isn't a failure driven by the extreme difficulty of the task. It seems like it must, then, have something to do with mis-management.

Although I think most of the criticisms of Obama, in relation to Affordable Care, are ideologically driven partisan horseshit, the fact remains that the website rollout was a very conspicuous belly flop, and I'd like to have a better idea of why. Was the wrong contractor used? If so, why was it selected? Were there ill-considered mid-stream adjustments? Active resistance by the private insurers (and, if so, why wasn't this highlighted early enough to scare them into line)? Was there insufficient oversight of the processes?

I have my own suspicions, just based on my personal experience with large IS-system roll-outs in the private sector, and what I've heard generally about management style within the Obama adminstration. I suspect that Obama laid out a vision then failed to get the dirt under his fingernails that would be needed to make sure that vision became a reality on time, and on-budget. But, I have no specific evidence to back that up, in the context of this particular screw-up, so I'm curious to hear from those who have studied it more closely.
 
Not really studied it that closely, but regardless of the details it appears to me that either Obama or Sebelius were asleep at the wheel - maybe both were.

Considering the controversial nature of the ACA and how big of a keystone it is to his legacy, it boggles the imagination that they took such a seemingly lackadaisical approach to it's implementation.

Hopefully the firestorm of bad publicity they've gotten since it's launch has added a sense of urgency to getting it fixed, and in six months to a year all this will be a footnote. However, their succes rate at launching the ACA so far does not instill an overabundance of confidence.
 
I don't expect intelligent discussion of this from conservatives, so I'm directing it specifically at liberals. What went wrong with the Obamacare website? Has anyone followed it closely enough to have a feel for it?

I mean, it's not like the concept itself is unworkable: we have plenty of other working exchanges at the state level, including an extremely large one in California. Those state exchanges are mostly working with no more glitches than you'd expect for any complicated IS system. Nor was this the product of some sort of overly ambitious schedule -- the delay between passage of the law and opening of the website was considerably longer than a similar period when Massachusetts did pretty much the exact same thing at the state level (and Massachusetts didn't have a prior roll-out to learn from). So this isn't a failure driven by the extreme difficulty of the task. It seems like it must, then, have something to do with mis-management.

Although I think most of the criticisms of Obama, in relation to Affordable Care, are ideologically driven partisan horseshit, the fact remains that the website rollout was a very conspicuous belly flop, and I'd like to have a better idea of why. Was the wrong contractor used? If so, why was it selected? Were there ill-considered mid-stream adjustments? Active resistance by the private insurers (and, if so, why wasn't this highlighted early enough to scare them into line)? Was there insufficient oversight of the processes?

I have my own suspicions, just based on my personal experience with large IS-system roll-outs in the private sector, and what I've heard generally about management style within the Obama adminstration. I suspect that Obama laid out a vision then failed to get the dirt under his fingernails that would be needed to make sure that vision became a reality on time, and on-budget. But, I have no specific evidence to back that up, in the context of this particular screw-up, so I'm curious to hear from those who have studied it more closely.

My own views are tied to private-sector experience, so maybe they need to be taken with a grain of salt. But often when I see something like this go so badly, it's a leadership failure, due to a bad conception of what leadership entails. Certain leaders take the attitude that their job is the "vision thing" -- laying out a vision, then expecting others to figure out how to make it work. They have a disdain for diving into the details, which they write off as micromanagement. But the result is that their projects frequently fail. The people who know the details are afraid to speak up and explain why the vision needs to be modified, so everyone marches ahead towards a cliff and it inevitably ends badly.... usually (in the private sector) with the leaders somehow dodging responsibility.

What I've seen of Obama makes me suspect that's his style, as well -- what the Republicans ridicule as "leading from behind." I have trouble picturing him sitting through hours-long meetings of software engineers discussing the website's problems and testing protocols. As with Bush, before him, the accounts I've read suggest he doesn't have much appetite for that kind of nitpicky stuff.

I don't know if that's what actually went wrong here, but it sure would be consistent with what I've see in the business world.
 
it's what happens evidently when you use old classmates for such an import web site........that had already been fired by Canadian government
 
I don't expect intelligent discussion of this from conservatives, so I'm directing it specifically at liberals. What went wrong with the Obamacare website? Has anyone followed it closely enough to have a feel for it?

I mean, it's not like the concept itself is unworkable: we have plenty of other working exchanges at the state level, including an extremely large one in California. Those state exchanges are mostly working with no more glitches than you'd expect for any complicated IS system. Nor was this the product of some sort of overly ambitious schedule -- the delay between passage of the law and opening of the website was considerably longer than a similar period when Massachusetts did pretty much the exact same thing at the state level (and Massachusetts didn't have a prior roll-out to learn from). So this isn't a failure driven by the extreme difficulty of the task. It seems like it must, then, have something to do with mis-management.

Although I think most of the criticisms of Obama, in relation to Affordable Care, are ideologically driven partisan horseshit, the fact remains that the website rollout was a very conspicuous belly flop, and I'd like to have a better idea of why. Was the wrong contractor used? If so, why was it selected? Were there ill-considered mid-stream adjustments? Active resistance by the private insurers (and, if so, why wasn't this highlighted early enough to scare them into line)? Was there insufficient oversight of the processes?

I have my own suspicions, just based on my personal experience with large IS-system roll-outs in the private sector, and what I've heard generally about management style within the Obama adminstration. I suspect that Obama laid out a vision then failed to get the dirt under his fingernails that would be needed to make sure that vision became a reality on time, and on-budget. But, I have no specific evidence to back that up, in the context of this particular screw-up, so I'm curious to hear from those who have studied it more closely.

The lack of responses from your target audience is exactly what I expected...
 
culled from various online sources over the past month . . .

- the website "architecture" was obsolete; it was based on 3-5 year old java programming techniques which are no longer in vogue

- the day before the website went live, it "crashed" during load testing when a simulation involving 500 simultaneous users was attempted. they went live the next day with no repairs anyway, in order to meet the deadline and not incur any delay penalties.

- there is some feeling that in addition to the software being crap, the hardware capacity is also insufficient

- the federal government kept changing the system requirement right up through August 2013, as regulations were expanded and clarified. many later requirements conflicted with the initial ones.

- the principal contractor for the website has never completed any online project even remotely approaching the scope and complexity of the ACA. an analogy - like hiring the guys who re-coat your driveway to construct an interstate highway, then acting surprised when they screw it up.
 
I don't expect intelligent discussion of this from conservatives, so I'm directing it specifically at liberals. What went wrong with the Obamacare website? Has anyone followed it closely enough to have a feel for it?

I mean, it's not like the concept itself is unworkable: we have plenty of other working exchanges at the state level, including an extremely large one in California. Those state exchanges are mostly working with no more glitches than you'd expect for any complicated IS system. Nor was this the product of some sort of overly ambitious schedule -- the delay between passage of the law and opening of the website was considerably longer than a similar period when Massachusetts did pretty much the exact same thing at the state level (and Massachusetts didn't have a prior roll-out to learn from). So this isn't a failure driven by the extreme difficulty of the task. It seems like it must, then, have something to do with mis-management.

Although I think most of the criticisms of Obama, in relation to Affordable Care, are ideologically driven partisan horseshit, the fact remains that the website rollout was a very conspicuous belly flop, and I'd like to have a better idea of why. Was the wrong contractor used? If so, why was it selected? Were there ill-considered mid-stream adjustments? Active resistance by the private insurers (and, if so, why wasn't this highlighted early enough to scare them into line)? Was there insufficient oversight of the processes?

I have my own suspicions, just based on my personal experience with large IS-system roll-outs in the private sector, and what I've heard generally about management style within the Obama adminstration. I suspect that Obama laid out a vision then failed to get the dirt under his fingernails that would be needed to make sure that vision became a reality on time, and on-budget. But, I have no specific evidence to back that up, in the context of this particular screw-up, so I'm curious to hear from those who have studied it more closely.


I don't think we should "over assume" anything, by comparing this one with the various state exhanges. For one thing, each state only needed to address the rules and data specific to that state. The national regime needs to cross-reference and accomodate, every which way. And of course, the state processes involved almost universally willing parties and partners. That's not the case with the federal regime.

The same cases could be made when comparing just about any private website startup, with that of the federal website. So.....designing the federal website was a "heavy lift" for sure...But, that doesn't mean it should've tuned out such a hash.

I think the hash goes to the fact of so many parties being involved. I've read that over 50 different contractors had a hand in this. That's probably not the best way of going about a task as complex as this one. I'm certain that Amazon, Fedex, or whom-private-ever wouldn't involve anywhere near that many players, and I seriously doubt that any of the states did.

So...why did the Obamans do it? I suspect that part of it had to do with avoiding charges of cronyism - especially as the "tech world" is more inclined towards the Democrats. And heck.....I'm sure it something to do with currying as much goodwill with as many disparate parties as possible.
 
I don't expect intelligent discussion of this from conservatives, so I'm directing it specifically at liberals. What went wrong with the Obamacare website? Has anyone followed it closely enough to have a feel for it?

I mean, it's not like the concept itself is unworkable: we have plenty of other working exchanges at the state level, including an extremely large one in California. Those state exchanges are mostly working with no more glitches than you'd expect for any complicated IS system. Nor was this the product of some sort of overly ambitious schedule -- the delay between passage of the law and opening of the website was considerably longer than a similar period when Massachusetts did pretty much the exact same thing at the state level (and Massachusetts didn't have a prior roll-out to learn from). So this isn't a failure driven by the extreme difficulty of the task. It seems like it must, then, have something to do with mis-management.

Although I think most of the criticisms of Obama, in relation to Affordable Care, are ideologically driven partisan horseshit, the fact remains that the website rollout was a very conspicuous belly flop, and I'd like to have a better idea of why. Was the wrong contractor used? If so, why was it selected? Were there ill-considered mid-stream adjustments? Active resistance by the private insurers (and, if so, why wasn't this highlighted early enough to scare them into line)? Was there insufficient oversight of the processes?

I have my own suspicions, just based on my personal experience with large IS-system roll-outs in the private sector, and what I've heard generally about management style within the Obama adminstration. I suspect that Obama laid out a vision then failed to get the dirt under his fingernails that would be needed to make sure that vision became a reality on time, and on-budget. But, I have no specific evidence to back that up, in the context of this particular screw-up, so I'm curious to hear from those who have studied it more closely.

Your asking liberals...what went wrong...liberal answer: Nothing

Here are some suggestions....look at how many websites are their that cost as much as the Obamcare website...you will find only a few perhaps 20 websites that come close to the cost of the Obamcare website.....But as long as your going to be a partisan hack you will never get any real answers...because yopu had been getting the reals answers all along...you just dint like the answers, because Republicans who read the bioll like Ted Cruz told you whta would happen......but you thought you kbnew more than a Law clerk for Chief Justice William Rehnquist....thus idiots thinking they know better is your problem...and they dont.
 
culled from various online sources over the past month . . .

- the website "architecture" was obsolete; it was based on 3-5 year old java programming techniques which are no longer in vogue

- the day before the website went live, it "crashed" during load testing when a simulation involving 500 simultaneous users was attempted. they went live the next day with no repairs anyway, in order to meet the deadline and not incur any delay penalties.

- there is some feeling that in addition to the software being crap, the hardware capacity is also insufficient

- the federal government kept changing the system requirement right up through August 2013, as regulations were expanded and clarified. many later requirements conflicted with the initial ones.

- the principal contractor for the website has never completed any online project even remotely approaching the scope and complexity of the ACA. an analogy - like hiring the guys who re-coat your driveway to construct an interstate highway, then acting surprised when they screw it up.

I thought the principal contractor handled web implementation of Bush's Medicare changes. No?
 
I don't think we should "over assume" anything, by comparing this one with the various state exhanges. For one thing, each state only needed to address the rules and data specific to that state. The national regime needs to cross-reference and accomodate, every which way. And of course, the state processes involved almost universally willing parties and partners. That's not the case with the federal regime.

The same cases could be made when comparing just about any private website startup, with that of the federal website. So.....designing the federal website was a "heavy lift" for sure...But, that doesn't mean it should've tuned out such a hash.

I think the hash goes to the fact of so many parties being involved. I've read that over 50 different contractors had a hand in this. That's probably not the best way of going about a task as complex as this one. I'm certain that Amazon, Fedex, or whom-private-ever wouldn't involve anywhere near that many players, and I seriously doubt that any of the states did.

So...why did the Obamans do it? I suspect that part of it had to do with avoiding charges of cronyism - especially as the "tech world" is more inclined towards the Democrats. And heck.....I'm sure it something to do with currying as much goodwill with as many disparate parties as possible.

Why would the states involve only universally willing parties and partners? There was a lot of discontent among private insurers and employers in Massachusetts, for example, when we implemented Romneycare. Yet I don't remember any significant issues with the web page's roll-out.

I suppose your theory about divididing up the work too many ways makes sense. That's part of the explanation, after all, for how we manage to spend vast amounts of money on our military: military procurement is done not with an eye for efficiency, but rather with an eye to handing out valuable contracts to as many important political districts as possible, to get a critical mass with a vested interest in supporting the program. Perhaps something similar was done with Obamacare.

When I work on this kind of thing, in my job, I fight hard to have a single general contractor, with it being responsible for the subs on its own, rather than having multiple primary contractors having to interact, which is just a recipe for everyone pointing to everyone else when there's a problem. This is also one reason I've long been a fan of APPLE products: if something goes wrong, I complain to Apple, without having to worry about whether it's a component issue or cpu issue or software issue or OS issue, etc., the way one typically had to with a PC. It either worked, or it didn't, and if it didn't work, it was Apple's job to fix it.
 
Why would the states involve only universally willing parties and partners? There was a lot of discontent among private insurers and employers in Massachusetts, for example, when we implemented Romneycare. Yet I don't remember any significant issues with the web page's roll-out.

I suppose your theory about divididing up the work too many ways makes sense. That's part of the explanation, after all, for how we manage to spend vast amounts of money on our military: military procurement is done not with an eye for efficiency, but rather with an eye to handing out valuable contracts to as many important political districts as possible, to get a critical mass with a vested interest in supporting the program. Perhaps something similar was done with Obamacare.

When I work on this kind of thing, in my job, I fight hard to have a single general contractor, with it being responsible for the subs on its own, rather than having multiple primary contractors having to interact, which is just a recipe for everyone pointing to everyone else when there's a problem. This is also one reason I've long been a fan of APPLE products: if something goes wrong, I complain to Apple, without having to worry about whether it's a component issue or cpu issue or software issue or OS issue, etc., the way one typically had to with a PC. It either worked, or it didn't, and if it didn't work, it was Apple's job to fix it.

When I say "unwilling", I'm talking about the recalcitrant states that were almost by definition, the ones most likely to default to the federal outline.

Another problem occurs to me though. Which other website framework of this scope and scale (assuming there IS one) is expected to be all things to all people? I buy most of my clothes from L.L. Bean. I like their website just fine and use it as my exclusive Beans shopping modus.

Now of course, Bean's market isn't quite so broad and varied as that of Obamcare, to begin with. And, Bean's product line isn't nearly as complex, critical, personal, and state-specific as Obamacare's. And on top of that, I'm sure that a relevant share of Bean's market - especially their more traditional one, doesn't even use their website. They just pick up the phone and dial the 800 number, as they always have.

Whatever, LL. Bean's essential obligation to a functioning website, is to L.L. Bean. The fellow who buys all his camo "with cash money", "down at the WalMart" can call and berate Beans for a potential software misunderstanding all day long and...what, Beans worry?

Obamacare doesn't have that "luxury" and EVERY American is a critic.
 
Love this remark by facebook founder, Mark Zuckerberg.. he sums it up in a nutshell.. imo..
~~~~
Mark Zuckerberg Smacks Down the Media Myth That The Website Rollout Has Doomed the ACA
Excerpt:

WRIGHT: And there’s the program where the president himself admits the government blew it, big time. The troubled website, health care.gov. What advice would you have for the president on his poor website?

ZUCKERBERG: You know, sometimes stuff doesn’t work when you want it to. We’ve certainly had plenty of mistakes and things that haven’t worked the way that we want to. The right thing here is just to keep on focusing on building the service that you think is right in the long-term.

Well, that certainly wasn’t the answer that ABC News was looking for. Notice the bias in the ABC News piece. ABC called the website troubled without admitting that most of the problems have already been fixed. ABC was hoping that Zuckerberg would feed into their narrative that website is a horrible disaster, but instead the Facebook founder told them the truth.
http://www.politicususa.com/2013/11...ks-media-myth-website-rollout-doomed-aca.html
 
Last edited:
I don't expect intelligent discussion of this from conservatives, so I'm directing it specifically at liberals. What went wrong with the Obamacare website? Has anyone followed it closely enough to have a feel for it?

I mean, it's not like the concept itself is unworkable: we have plenty of other working exchanges at the state level, including an extremely large one in California. Those state exchanges are mostly working with no more glitches than you'd expect for any complicated IS system. Nor was this the product of some sort of overly ambitious schedule -- the delay between passage of the law and opening of the website was considerably longer than a similar period when Massachusetts did pretty much the exact same thing at the state level (and Massachusetts didn't have a prior roll-out to learn from). So this isn't a failure driven by the extreme difficulty of the task. It seems like it must, then, have something to do with mis-management.

Although I think most of the criticisms of Obama, in relation to Affordable Care, are ideologically driven partisan horseshit, the fact remains that the website rollout was a very conspicuous belly flop, and I'd like to have a better idea of why. Was the wrong contractor used? If so, why was it selected? Were there ill-considered mid-stream adjustments? Active resistance by the private insurers (and, if so, why wasn't this highlighted early enough to scare them into line)? Was there insufficient oversight of the processes?

I have my own suspicions, just based on my personal experience with large IS-system roll-outs in the private sector, and what I've heard generally about management style within the Obama adminstration. I suspect that Obama laid out a vision then failed to get the dirt under his fingernails that would be needed to make sure that vision became a reality on time, and on-budget. But, I have no specific evidence to back that up, in the context of this particular screw-up, so I'm curious to hear from those who have studied it more closely.

No great mystery. They chose incompetent contractors and the fed employees overseeing them were in over their heads. I also think the problems were compounded by the dithering of some Red states as to whether they would operate their own exchange websites, but that was likely only a small factor.

There is no real excuse in this day and age - it was just incompetence.
 
Given that there's really nothing unusual about the "failures" http://www.businessinsider.com/heal...ents-innovation-problem-2013-11#ixzz2l7m5Xlhy I've thought from the beginning that a great deal of fault lies with "outsourcing" http://www.rawstory.com/rs/2013/10/...t-woes-is-out-of-control-private-contractors/ problems and a "too many chiefs..." situation that arises that could be cured if it was all done inhouse by a fed IT department with complete control over the whole ball of wax. http://wordofpie.com/2013/10/22/healthcare-gov-fiasco-shows-the-problems-in-federal-it/ This is a problem begging for a long term solution.

I don't think that there's any question that BHO coulda cracked the whip/"gotten his fingernails dirty" a bit more perhaps, but I'd argue that systemic difficulties woulda muddled things anyway. And of course, we also can't exclude the chicanery of the repubs in the matter either. http://www.politicususa.com/2013/11...ely-sabotaged-aca-website-hoping-implode.html
 
Back
Top