Big Government

On Being an IT Project Manager

by

My profession is much in the news at the moment, so I thought I would pass along such insights as I have from my career, mostly from a multibillion-dollar debacle which I and several thousand others worked on for a few years around the turn of the millennium. I will not name my employer, not that anyone with a passing familiarity with me doesn’t know who it is; nor will I name the project, although knowing the employer and the general timeframe will give you that pretty quickly too.
We spent, I believe, $4 billion, and garnered a total of 4,000 customers over the lifetime of the product, which was not aimed at large organizations which would be likely to spend millions on it, but at consumers and small businesses which would spend thousands on it, and that amount spread out over a period of several years. From an economic transparency standpoint, therefore, it would have been better to select 4,000 people at random around the country and cut them checks for $1 million apiece. Also much faster. But that wouldn’t have kept me and lots of others employed, learning whatever it is we learn from a colossally failed project.
So, a few things to keep in mind about a certain spectacularly problematic and topical IT effort:

  • Large numbers of reasonably bright and very hard-working people, who have up until that point been creating significant wealth, can unite in a complete flop. Past performance is no guarantee, and all that. Because even reasonably bright, hard-working people can suffer from failures of imagination, tendencies to wishful thinking, and cultural failure in general.
  • Morale has got to be rock-bottom for anybody with any degree of self-awareness working on this thing. My relevant moment was around the end of ’99 when it was announced, with great fanfare, at a large (200+ in attendance) meeting to review progress and next steps, that we had gotten a single order through the system. It had taken various people eight hours to finish the order. As of that date, we were projecting that we would be doing 1,600 orders a day in eight months. To get an idea of our actual peak rate, note the abovementioned cumulative figure of 4,000 over the multi-year lifespan of the project.
  • Root cause analysis is all very well, but there are probably at least three or four fundamental problems, any one of which would have crippled the effort. As you may infer from the previous bullet point, back-office systems was one of them on that project. Others which were equally problematic included exposure to the software upgrade schedule of an irreplaceable vendor who was not at all beholden to us to produce anything by any particular date, and physical access to certain of our competitors’ facilities, which they were legally required to allow us into exactly two (2) days per year. See also “cultural failure,” above; most of us were residing and working in what is one of the most livable cities in the world in many ways, but Silicon Valley it ain’t.
  • Not to overlook the obvious, there is a significant danger that the well-advertised difficulties of the website in question will become a smokescreen for the fundamental contradictions of the legislation itself. The overall program cannot work unless large numbers of people act in a counter-incentived (possibly not a word, but I’m groping for something analogous to “counterintuitive”) fashion which might politely be termed “selfless” and do so in the near future. What we seem likely to hear, however, is that it would have worked if only certain IT architectural decisions had been better made.

This thing would be a case study for the next couple of decades if it weren’t going to be overshadowed by physically calamitous events, which I frankly expect. In another decade, Gen-X managers and Millennial line workers, inspired by Boomers, all of them much better at things than they are now, “will be in a position to guide the nation, and perhaps the world, across several painful thresholds,” to quote a relevant passage from Strauss and Howe. But getting there is going to be a matter of selection pressures, with plenty of casualties. The day will come when we long for a challenge as easy as reorganizing health care with a deadline a few weeks away.

Where health care may be going.

by

UPDATE: I posted this as much for myself as for others to read. Today, Peggy Noonan weighs in. In case this is behind the paywall, here is her conclusion.

Even though it’s huge, and those who are reporting the story every day are, by and large, seasoned and have seen a few things, no one seems to know how it will end. Because it’s new territory. Does anyone believe the whole technological side can be fixed quickly? No. The president may eventually accept a brief delay in implementation—it is almost unbelievable that he will not—but does anyone think that the economics of the ACA, the content as set out and expressed on the sites, will flow smoothly, coherently, and fully satisfy the objectives of expanding health-insurance coverage while lowering its cost? You might believe that, but early reports of sticker shock, high deductibles and cancelled coverage are not promising. Does anyone think the president will back off and delay the program for enough time not only to get the technological side going but seriously improve the economics? No. So we’re not only in the middle of a political disaster, we’re in the middle of a mystery. What happens if this whole thing continues not to work? What do we do then?

This is the Titanic, folks.

I have watched the failed rollout of Obamacare this past three weeks and wondered where it was going. I have some suspicions. There is a lot of talk about delaying the individual mandate, as Obama did with the employer mandate. Megan McArdle has a post on this today. I think it is too late to fix or delay Obamacare.

With Nov. 1 storming toward us and the health insurance exchanges still not working, we face the daunting possibility that people may not be able to sign up for January, or maybe even for 2014. The possibility of a total breakdown — the dreaded insurance death spiral — is heading straight for us. The “wait and see if they can’t get it together” option no longer seems viable; we have to acknowledge that these problems are much more than little glitches, and figure out what to do about them.

She has already described the insurance death spiral. I think it is here.

Am I exaggerating? I know it sounds apocalyptic, but really, I’m not. As Yuval Levin has pointed out, what we’re experiencing now is the worst-case scenario for the insurance markets: It is not impossible to buy insurance, but merely very difficult. If it were impossible, then we could all just agree to move to Plan B. And if it were as easy as everyone expected, well, we’d see if the whole thing worked. But what we have now is a situation where only the extremely persistent can successfully complete an application. And who is likely to be extremely persistent?

Very sick people.

People between 55 and 65, the age band at which insurance is quite expensive. (I was surprised to find out that turning 40 doesn’t increase your premiums that much; the big boosts are in the 50s and 60s.)
Very poor people, who will be shunted to Medicaid (if their state has expanded it) or will probably go without insurance.

Levin points out: It is now increasingly obvious to them that this is simply not how things work, that building a website like this is a matter of exceedingly complex programming and not “design,” and that the problems that plague the federal exchanges (and some state exchanges) are much more severe and fundamental than anything they imagined possible. That doesn’t mean they can’t be fixed, of course, and perhaps even fixed relatively quickly, but it means that at the very least the opening weeks (and quite possibly months) of the Obamacare exchanges will be very different from what either the administration or its critics expected.

The insurance industry is already reacting to Obamacare and this will quickly become irreversible. This article is from September.

IBM, Time Warner, and now Walgreens have made headlines over the past two weeks by announcing that they plan to move retirees (IBM, Time Warner) and current employees (Walgreens) into private health insurance exchanges with defined contributions from employers.

The article calls it “maybe a good thing” but that supposes the exchanges will function. What if they don’t for a year or more ? What will health care look like in November 2014 ?

What happens next — as we’ve seen in states such as New York that have guaranteed issue, no ability to price to the customer’s health, and a generous mandated-benefits package — is that when the price increases hit, some of those who did buy insurance the first year reluctantly decide to drop it. Usually, those are the healthiest people. Which means that the average cost of treatment for the people remaining in the pool rises, because the average person in that pool is now sicker. So premiums go up again . . . until it’s so expensive to buy insurance that almost no one does.

Will that be apparent a year from now ? I’m sure the administration, and the Democrats, will do almost anything to avoid that. What can they do ? They’ve already ignored the law to delay the employer mandates. It’s too late to delay the individual mandate because individual policies are being cancelled right now.

Read more

Landmark Case Possibilities With Detroit Chapter 9

by

Today, the trial begins to determine if Detroit can enter chapter 9 bankruptcy. I have been trying to read a lot about what this means for the muni bond markets. As of right now, not much. But in the future, possibly a lot.

Here is a great piece on the subject and one that I will refer to through this post. It is written by the Chicago Fed, and explains what is going on, and how the Emergency Manager, Kevyn Orr, is going about trying to right the ship. The document is short, but somewhat dense. I had to read it three times and making some notes helped me understand it better.

After making this diagram, I joked to myself that this is probably a better flow chart understanding of the City of Detroit’s debt than any sort of financial documents the city of Detroit had prior to the EM taking over. But I digress.

After the issue of letting Detroit go Chapter 9 is resolved (I guess I don’t really see any other option) there are several interesting issues that may affect the muni bond market moving forward.

The debt looks like this, in simplified form:

Water and sewer debt – $6bb

General Obligation debt (limited tax backed and unlimited tax backed) – $1bb

Pension Obligation Certificates and associated swaps – $2.3bb

Pensions – $3.5bb

Other Post Employment Benefit Obligations – $5.7bb

First, Orr has decided that the only things that he will be treating as secured debt will be the water and sewer system bonds (backed by a pledge of revenues from the utility system) and the “double barreled” UTGO (unlimited tax general obligation) and LTGO (limited tax general obligation) bonds. Double barreled means that these certain bonds have separate income streams derived from the State of Michigan. This is significant because no General Obligation bond in the muni universe in any Chapter 9 filing has ever been impaired (with the exception of the disastrous Jefferson County, Alabama filing in 2011). Basically, Orr is offering ten cents on the dollar to EVERYONE that is not secured. This includes pensions, OPEB (other post employment benefit) plans, pension obligation certificates, swaps, and all the rest. In the middle of this, the fact that Orr treated the UTGO debt (which can be funded by unlimited property tax levies) just like all of the other debt is a first. This will also be settled in court, and will affect the perception of a lot of other cities’ GO debt as relates to the backing by property tax levies.

The next Big Deal to the muni bond universe is that there is a conflict between state and federal law as to if Orr can pound down the pensions and OPEBs. Law in the State of Michigan says he can’t but federal law has no issue with it. There is no law on record that addresses this and I am sure it will be a bitter battle to the end. If there is some sort of sweeping Tenth Amendment ruling that says that you can’t touch the pensions, this will affect the debt of a LOT of large cities that have similar state laws in place, such as Chicago, LA and others that have giant unfunded pension obligations. But to me, winning this in court is one thing for the pensions, actually getting the money out of the city of Detroit, that has none, is quite another. I am sure that they would at that time try to get preferred secure status over the utility bonds, but I don’t think that will really happen.

So far, the markets have just shrugged their shoulders at this whole affair, with the small exception of punishing the bonds slightly from places in the State of Michigan. I am sure that as this disaster winds its way through the courts, that this may change. Being an investor in the muni market, I will be keeping a close eye on how this plays out, as well as the soon to be crisis in Puerto Rico.

Cross posted at LITGM.

Dick Bove: DC Wants the Dow to Fall 1000 Points

by

Watching CNBC. Bove says that because the stock market isn’t in a major sell-off the pols can’t get away with the kind of bad deal (my interpretation) that they want. He warns investors: “The only good strategy at the moment is to get out of the way. The politicians will get the panic they seek.”

CNBC spins this as: lawmakers need a reason to act to avoid gridlock. What Bove is actually saying is that there is a conflict of interest between the pols, particularly the Democrats, who want to bust the sequester and force the full implementation of Obamacare as scheduled, and American taxpayers. This is why Obama says, “this time I think Wall Street should be concerned”. Nice stock market you’ve got here, pity if something were to happen to it.

It appears that Obama is trying to do with the markets the same thing that he did with the national parks: make the government shutdown costly for ordinary Americans, whom he hopes will then find new cause to support him. The media will keep trying to reframe this crass partisan shakedown as Obama working to prevent disaster, but what he’s really doing is transparent to anyone who pays attention.

Why the Obamacare site is not working.

by

I hadn’t thought of this situation, only because I didn’t have enough imagination to see that politics trumps all with Obama.

A growing consensus of IT experts, outside and inside the government, have figured out a principal reason why the website for Obamacare’s federally-sponsored insurance exchange is crashing. Healthcare.gov forces you to create an account and enter detailed personal information before you can start shopping. This, in turn, creates a massive traffic bottleneck, as the government verifies your information and decides whether or not you’re eligible for subsidies. HHS bureaucrats knew this would make the website run more slowly. But they were more afraid that letting people see the underlying cost of Obamacare’s insurance plans would scare people away.

This just didn’t occur to me. It should have. After all, what was Benghazi about ?

This political objective—masking the true underlying cost of Obamacare’s insurance plans—far outweighed the operational objective of making the federal website work properly. Think about it the other way around. If the “Affordable Care Act” truly did make health insurance more affordable, there would be no need to hide these prices from the public.

It is just amazing that the politicians know so little about technology (this was the guy with the Blackberry who made fun of McCain) that they did not understand that saying something doesn’t make it happen.

Read more