The Cobra Effect

Once upon a time in India, in a village (so the story goes), there was a problem with cobras. There were too many of them.

Cobras, those freaky little reptiles, have a bad rap but the unfortunate truth is they *can* kill you, so it’s understandable that the village wanted them gone. And so the village leaders instituted a bounty for every dead cobra. This would surely be successful, as everyone likes money, and no one likes cobras! Couldn’t miss!

Sure enough, tons of dead cobras were brought in…. but the overall cobra problem didn’t seem to subside. This is because just outside the village were people (you guessed it) breeding cobras, so they could kill them, so they could collect the bounty. Naturally the government didn’t want to pay for purpose-bred cobras, so they stopped the bounty. And the breeders, with no more financial incentive to breed cobras, let the cobras loose, thereby increasing the cobra population.

This would be the precise opposite of the desired solution of the bounty, and this sort of circumstance is called the “Cobra Effect”. You can read about it here (Wikipedia lists the village as the city of Delhi, but I’m not sure I buy that). Another example is the famous pigs of Fort Benning.

Essentially, the Cobra Effect is when your proposed solution actually makes the problem *worse* than it was to begin with. It doesn’t always have to be economic in nature, as I am seeing at work currently.

Fourteen months ago I took my current job and in the first couple of weeks I volunteered to work on a given project. The given project had been languishing for a few months and was on someone’s radar again, so it needed attention. The basic idea was to take 200,000 records and consolidate them into about 6 or 7 thousand, with minimal disrupt. We crafted a comprehensive plan to get the project done, executed it, and…

…it blew up in a horrific, ugly mushroom cloud. Everything that could go wrong did: bad data meant some emails went to wrong people. Emails that went to the right people invariably succeeded in pissing them off, and emails that had been declared not necessary to go out turned out to have been rather necessary, after all. Data was updated but not correctly, thanks to an artifact in code knowledge no one remembered (so the after effect was, “Oh, that’s why that was there.”). 112 Hours later it was fixed. 

After six distinct debriefs and detailed postmortems (“Fix the contact information”, “Vet it with this team in this other fashion even though they originally said the first way was fine”, “Avoid Excel”, “Use Excel”, “put a PM on it”, “Take the PM off of it”, “Let’s start from scratch”, “Let’s use what we had before and refine it”, “Take it out of this team”, “Give it back to that team”) it looks like the current plan is to…

… do nearly exactly what we originally did. Only now, we’re doing it with 30% more records, because the first reaction from the first go-around that went awry was the recipients of the new format/data/project went into the system and… created more records. 

Points:

1. Unintended consequences are everywhere, and the best intentions often create more of them, and

2. The Cobra Effect doesn’t just apply to economics, although given a few minutes I could probably monetize this project and it would make me cry, and 

3. You can have a fancy name and anecdote for something, and even have it written about in many management books, but it won’t prevent people from making ill-advised choices (despite best efforts at education).

Brand New Year, Now, With More Crazy!

As much as I’d love to blog about the FiscalCliff, Cliff 2, Cliff 3 First Blood, Child of the Fiscal Cliff, Return of the Fiscal Cliff, Fiscal Cliff Revolutions, etc., I’m not going to, as others have written much better prose and admonishment of it than I could ever hope to do. Suffice it to say that the “deal” currently discussed in the house (and passed by the Senate) doesn’t address any of the problems that need addressing, and the cliff itself is largely a fabrication of this broken legislature we have and so applauding any sort of garbage-pile-at-the-bottom-save they’ve managed to create is an exercise in self-delusion. I’ll save my self-delusion for better use.

(For really excellent writing and explanations of Why This Isn’t A Save and In Fact Is a Huge Ream of BS, Regardless of Which Side of the Political Spectrum You Are On, see: this and this and this. I also recommend following Heidi Moore and Ezra Klein on Twitter. Their play-by-play is excellent.)

Fiscal-political brinksmanship aside, I find myself as many do, the first day of the year, wincing in readiness for the email onslaught as brought by January 2nd; in full knowledge that school starts tomorrow (for both the boy and I, I get Macroeconomics and the last PreCalc class); bracing myself for the inevitable deluge of resoluters at the gym. All the classes will be full and the instructors will be randomized.

I’ve used the past few days off to catch up on my OCD; my rock collection is now digitized (I can look up rocks by family, size, or color), the undercroft is organized (2 thousand plus books are packed up to go to my parents house), the fridge is cleaned out (literally and figuratively), the study is reconfigured, I finished two knitting projects. In typical fashion, this is because I’m avoiding something.

I am avoiding my annual review.

Every year I am asked to write a series of paragraphs (or oblique sentences) about my performance, and every year I’m startled by two things: 1, how much I (and my team(s), when appropriate) have done, and 2, how it bears no resemblance to what we thought we were going to do. At the onset of each year we craft goals based on the plans of the company, and, in the form of companies everywhere, things change. Constantly. It’s got to the point where we should have t-shirts that say “the only constant is change” or “entropy always increases”. I may do that with my morale budget.

There has GOT to be a better way. 

This year, we have attempted to frame our goals in the context of the purpose of the exercise rather than the exercise itself; instead of talking about creating XYZ report or accomplishing ABC task, we’re focusing on the end result: how do we make the company more successful, which thereby (frankly) increases the bonus pool, which thereby (frankly) makes its way into our own microeconomics. That is the part of this exercise the company wants and needs, and that’s great.

It occurs to me however that a lot of us are thriving off of the variety, the change, and the volume of things to do for the sake of the variety, change, and volume. Each new email brings a challenge, almost baiting you: are you up to it? Some crisis has erupted, can you handle it? Can you delegate it? Can you deal with it? I’m happy to say that in the ensuing year I am confident I can do all of those things, this is the rare comfort of someone who has really excellent people to rely on at work. 

And with that, tomorrow officially brings the crazy for 2013. School, school, work, home, and all the entropy that can increase. There is no room for triskaidekaphobia, there is no room to wallow. And so I will write my review, take a deep breath, and acknowledge 2013.

Bring it!