Archive for September, 2008

A Geek’s Guide To The Financial Melt-Down

Monday, September 29th, 2008
How Did We Get Into This Financial Mess?

How Did We Get Into This Financial Mess?

Man – what a mess! I’m almost afraid to unwrap the paper each morning because the font size of the headlines seems to be getting bigger and bigger as the financial news gets worse and worse. Stock trading firms are going belly up, others are getting bought. Fannie Mae and Freddie Mac (who are they?) got taken over by the government and now WaMu just failed. Clearly this is the end of the world. Maybe.

As a reasonably gifted technical person, I thought that I knew how the world of finance worked (and so to apparently did a lot of people who worked in finance); however, with the wheels coming off of the truck, now I’m not so sure. I really needed someone to explain to me just how so much could go so wrong so quickly. And that’s where Stephen stepped in.

Stephen Schwarzman is a true Master of the Universe in financial circles. First off, he’s a billionaire. Secondly, he’s the chairman and co-founder of the Blackstone Group private-equity firm. In case you aren’t aware of it, Blackstone is HUGE and they only play with numbers that end in “Billion”. So when the Wall Street Journal and the Yale School of Management hosted a round table of important people in finance, he was there.

Stephen started what was intended to be a Q&A session with an (almost) all-in-one-breath summary of just what the heck has happened to the financial markets. For geeks who like their technical information short & sweet and preferably from a guru, you’re not going to get much better than this. Here’s the whole quote:

It’s a perfect storm. It started with Congress encouraging lending to lower income people. You went from subprime loans being 2% of total loans in 2002 to 30% of total loans in 2006. That kind of enormous increase swept into a net people who shouldn’t have been borrowing.

Those loans were packaged into CDOs rated AAA, which lead to the investment-banking firms [buying them] to do little to no due diligence and the securities were distributed throughout the world where they started defaulting.

When they started defaulting, out of bad luck or bad judgment, we implemented fair-value accounting… You had wildly different marks for this kind of security, which led to massive write-offs by the commercial-banking and investment-banking system.

In the face of those losses… you needed to raise new equity…which came from sovereign-wealth funds, in part, which then caused political resistance to sovereign-wealth funds, who predictably have withdrawn from putting money into the system… It seemed pretty obvious that would have to happen. We now find ourselves with a liquidity crisis where fundamentally the cost of money for financial intermediaries [such as investment banks] is significantly in excess of their cost of lending it. So several institutions found themselves in a structurally impossible position… Goldman reverted to a banking charter for a lower cost of funds, which today is still not low enough for the business. So that is the story of how we got here.

Whew! All that in one breath? The man truly knows his stuff. If you got all of that, then you can stop reading now and you are fully prepared to be the star of the next cocktail party that you go to this week. However, if like me some of what Stephen said sailed over your head, then let’s take a few moments and do a some debugging and see what he was really getting at. Maybe if we step through what he said line-by-line it will make more sense:

It’s a perfect storm. It started with Congress encouraging lending to lower income people. You went from subprime loans being 2% of total loans in 2002 to 30% of total loans in 2006. That kind of enormous increase swept into a net people who shouldn’t have been borrowing.

Congress enacted the Community Reinvestment Act (CRA) in 1977 in order to encourage banks to extend loans to qualified people with low incomes. Home loans are actually divided into four different categories: prime, jumbo, subprime and near-prime mortgages. Everything is based on your credit risk: if you have a stable job and a good credit rating, then you can get a prime mortgage (lower interest rate). Jumbo loans are generally of prime quality, but they exceed the $417,000 ceiling for mortgages that can be bought and guaranteed by government-sponsored enterprises – basically if you are buying a McMansion then this is the kind of loan you’d take out. Near-prime mortgages are made at a higher interest rate than prime, but lower than subprime. These are for folks who may not be able to document their income or may have trouble providing a down payment. Subprime loans are for folks with poor credit ratings and risky sources of income. These loans carry the highest interest rates.

Things percolated along quite nicely and non-prime loans made up about 9% of all home loans being made up through about 2001. Then BANG! Two things happened: some clever mortgage banker devils decided to change how they calculated a person’s credit worthiness – they started using the same rules that were used to get auto loans (these were looser rules – it was much easier to get a loan). But wait, there’s more! By itself, just making it easier to qualify for a home loan would not have been enough to cause subprime loans to surge from 9% to 40% of all home loans being made in 2006. There had to be something else…

Once again, it was clever bankers to the rescue. See, it turns out that in order for a bank to make a loan, they need to have equity capital on hand to back those loans up (that’s what they are loaning out). When you run out of this, you’ve got to stop making loans and that means that you’ll miss out on making all that money that banks make when they process mortgages (remember all those “fees” when you bought a house?). What banks really like to do is to sell a mortgage to investors after they’ve completed the paperwork. This way it’s off their books and they’ve got more money to loan out. Hmm, the problem was that these subprime mortgages were too risky to sell to traditional investors. What to do? Sure seems like its time to invent a new financial vehicle to take care of this.

Those loans were packaged into CDOs rated AAA, which lead to the investment-banking firms [buying them] to do little to no due diligence and the securities were distributed throughout the world where the started defaulting.

Oh, oh – it’s vocabulary time. Remember, banks made prime mortgages funded with deposits from savers (you and me) and then sold them to investors. Near-prime and subprime mortgages presented a bit of a problem – no investor was going to touch them because they were too risky. This is where CDOs come in.

A Collateralized Debt Obligations (CDO) is a clever investment tool that was created to make investing in subprime mortgages easier for investors to stomach. What happens is that a lot of subprime mortgages were sold by banks and mortgage originators (non-banks that were handing out mortgages) and then these loans were stuck together into a CDO. Inside a CDO, individual loans were placed into one of three “trenches”: senior (pretty safe), mezzanine (sorta safe), and equity / unrated (uhh – I’m not so sure about this). Each trench paid a different interest rates with the higher risk trenches paying more to compensate investors for the higher risk. Got it so far?

What Stephen is talking about is that this all sorta works if there is a mix of loans (good/bad/ugly) in a CDO. What happens if they are all ugly? It turns out that these beasts are fairly complex and it’s quite difficult to accuracy determine how risky one of them is. The guys who are supposed to be good at doing this, the credit rating agencies (Moody’s, Standard & Poor’s), apparently were asleep at the wheel. An “AAA” rating basically means that an investment is a “sure thing” – its rock solid. They classified a lot of CDOs as being AAA when they were really made up of too many subprime morgages. Oh oh!

Things starting hitting the fan when folks started missing their mortgage payments on their subprime loans. This resulted in default rates shooting up. Hold on – this is where things start to get bad. Defaulting subprime loans then started to cause CDOs that were based on them to stop generating returns to investors (if nobody is making their monthly loan payments, then there is nothing to pass on to investors). All the clever tricks that had been set up to make sure that CDOs could withstand some defaults crumbled when it turned out that lots of CDOs were made up of all high risk subprime loans.

When they started defaulting, out of bad luck or bad judgment, we implemented fair-value accounting… You had wildly different marks for this kind of security, which led to massive write-offs by the commercial-banking and investment-banking system.

So the sky started falling. What made things get so bad so quickly? Well this little accounting trick called fair-value accounting sure didn’t help things. What this means is that the value of a CDO is based on the current market price for that CDO (whatever someone is willing to pay you for it right now). When the financial world started to turn upside down and the loans that made up lots of CDO started to turn out to be worthless, that meant that the value of the CDO itself started a race to $0. This is what caused the U.S. government to have to step in and save Fannie Mae and Freddie Mac they were backing too many bad loans.

When you are an investor and your investment has become worthless overnight (ouch!), what do you do? You write it off – you tell the world that your gold has become lead and you’ve just lost a lot of money. This happens all the time and everyone hopes to move on and do better next time. However, this time around lenders reacted to these signs by tightening credit standards especially on riskier mortgages.

When it became hard for everyone (prime, subprime, etc.) to get loans, people stopped buying houses. This meant that it became much harder to sell a house. This meant that if you got behind in your house payments then you couldn’t just sell the house and make yourself whole. You basically HAD to default on your loan and just walk away.

This meant that the banks and financial institutions could no longer raise money they way that they had been doing even as their investments turned to dust. Can you say cash flow problem? The perfect storm had arrived.

In the face of those losses… you needed to raise new equity…which came from sovereign-wealth funds, in part, which then caused political resistance to sovereign-wealth funds, who predictably have withdrawn from putting money into the system… It seemed pretty obvious that would have to happen.

So if you are a Lehman Brothers, what do you do now? You start cluching at straws. Your next best source of cash is what is called a Sovereign Wealth Funds (SWF). SWFs are typically created when governments have budgetary surpluses and have little or no international debt. A good example of a SWF is the Kuwait Investment Authority – lots of money looking for a home that will generate more money. Having foreign governments make big investments in the firms that control big parts of the U.S. economy made our elected officials in Washington D.C. very nervous. To make themselves feel better, they passed the Foreign Investment and National Security Act of 2007. Basically, this gave the government veto power over any deal that involved a SWF. The SWFs said, ok – if you are going to be that way, then we’ll go play somewhere else. If you were WaMu, then you just saw your last best chance for funding to save yourself walk away!

After this, everything just went to hell in a handbag. It’s not over yet. However, here’s the final take away that Stephen didn’t cover. Everything will work out in the end. What needs to happen is that the credit markets that businesses and people borrow from have to unfreeze. Once this happens, then people will start borrowing again (rationally we hope). Then investers will return and start to make investments. Life will once agian get back to normal. Grit your teeth and we’ll get though this together.

What do you think about the financial mess that we’re in? What do you think that this will mean in the long run for IT? Do you think that the computers and software that all of the banks and mortgage lenders used should have warned them that things were going to go wrong? Do you think that technology can save us from having this ever happen again? Leave me a comment and let me know what you are thinking.

Wicked Ways Of Managing Wicked IT Problems

Thursday, September 25th, 2008
Dorothy Knew How To Deal With Wicked Problems

Dorothy Knew How To Deal With Wicked Problems

Wicked IT problems can frustrate even the best of us – by their very nature, wicked IT problems have no solution (that’s why we call them “wicked” and not just “hard”). As we talked about last time, although you may not have the tools to solve these types of problems, you do have the tools needed to manage them. However, the key to dealing with problems like this successfully is to involve the entire IT department (yes, these problems are really that big). Let’s talk about how you’d go about doing that…

The first department-wide step that you’d need to take is to get everyone to focus on taking action. In traditional problem solving, we think though all of the possible strategies that we could execute and then pick the one(s) that we think will solve the problem. Sorry – that approach doesn’t work when you are dealing with a wicked problem. Instead, what you need to be doing is some experimenting. Specifically, choose a collection of strategies that you think MIGHT work and start executing on them. This approach actually has a name it’s called the “science of muddling through“. One thing that you’re going to have to keep in mind is that every action that you take to deal with the wicked IT problem will cause the problem to change. Remember, we’re dealing with a wicked problem here!

Finally, you need to take the hardest step. You need to implement what is called a “feed forward” process for your IT department. We are all very familiar with feedback systems where we compare the results of our actions to our original plans and then change our actions accordingly. Once again, bad news – feedback won’t help you to deal with a wicked IT problem, instead  you are going to need a feed forward solution. A feed forward process requires IT management and workers to take the time to imagine the IT department in the future. The future should be defined as being 5, 10, 25, and even 50 years down the road. The goal of this process is to picture what the IT department will be like, and then to determine what steps need to be taken today in order to move the department towards that goal.

So there you have it – ways to mange your wicked IT problems. Remember, when you enecounter a fustrating IT problem, there is always the chance that it may be a wicked problem. These types of problems can’t be solved and so you’re going to have to practice some wicked management…

Have you ever encountered a wicked IT problem? Did you try to start multiple strategies to deal with it all at once? How did this turn out for you? Have you ever had your IT department try to imagine how the department will look in the future? What did you do with this vision? Leave a comment and let me know what you are thinking…

A Quick Note Of Thanks To The Folks At Alltop.com

Wednesday, September 24th, 2008
Alltop.com is a web site that lists the best blogs in different areas.

Alltop.com is a web site that lists the best blogs in different areas.

As those of you with sharp eyes may have noticed, this blog is now sporting a shiny new badge over there on the right-hand side from the good folks at Alltop.com. They have added us to their listings of blogs and so I wanted to thank them for doing so and, of course, let you know a little bit about them. They actually describe what they do better than I could so allow me to quote them:

Alltop is an “online magazine rack” of popular topics. Tell us what you’re interested in, and we’ll bring you stories from the best websites and blogs on the topic. All the topics, all the time.

I greatly appreaciate the publicity that they’ve agreed to give this humble little bog and hopefully you’ll take the time to check out their list of other blogs all neatly grouped by topic!

Managing Wicked IT Problems

Monday, September 22nd, 2008
How to manage wicked IT problems

How to manage wicked IT problems

So we’ve chatted about Wicked IT Strategy problems – these are the ones that you really can’t solve. Given that, you’ve got a couple of different things that you can do. The easiest is to throw your arms up in the air, say “this can’t be solved”, and then work very hard at getting promoted so that it becomes someone else’s problem. Good luck with that approach! Let’s take a look at some other solutions for those of us who feel a deep burning need to make the world a better place for all…

Let us acknowledge that wicked IT problems can’t be solved. So your next best alternative is to come up with ways to cope with them. They aren’t going away, so you need to find some common ground that will allow you to live with them. As with all of us in IT, there are countless complicated solutions that you could probably come up with in order to address any problem. However, here are a couple of relatively simple actions that you can take that will yield real results:

Make everyone responsible for finding a way to manage the problem. This means that you need to reach out and drag in employees, customers, management, etc. and you need to make sure that you document everything that is said and establish clear means of communication between all parties. Because a wicked problem is so complex, it will take a wide variety of views and opinions in order to come up with unique ways of managing the problem. However, be careful! Don’t just collect inputs. Instead, make sure that everyone is involved in actually implementing their suggestions. Yes, having more people involved will make things more difficult, but because of the complexity of the problem they are all needed. Documenting all ideas and discussions will become more important when a plan is finally agreed on – the documentation will be needed in order to communicate the plan to the rest of the department.

Define what your department’s identity is. Although many different suggestions will be made as to how best to manage the wicked problem, it will be critical that whatever solutions are finally put in place are true to the IT department’s identity. The department’s identity is the cornerstone of its strategy and provides both direction and focus for the IT leaders. An identity is made up of a department’s values, competencies, and its aspirations. Staying true to these will allow critical decisions to be made quickly and painlessly.

But wait, there’s more that you can do to manage wicked problems. We’ll cover these next time…

Have you been able to assign responsibility for large problems to all of those who need to be involved? How did that work out – did the number of people who were involved make it hard to reach any sort of decision? Do you know what your IT department’s identity is and do you reference it when you are making decisions? Leave a comment and let me know what you think.

Wicked, Wicked IT Strategy Problems

Thursday, September 18th, 2008
Some IT problems can't be solved - these are wicked problems.

Some IT problems can't be solved - these are wicked problems.

Some problems just can’t be solved. As an IT guy with an engineering background, I find this hard to believe – it goes against my grain. I mean, back in school I encountered lots of problems that at first blush appeared to be impossible to solve. However, once I had gotten a little deeper into whatever class I was taking at the time things started to become more clear. New tools that I had learned could be used to solve what had previously appeared to be unsolvable problems. In the world of IT, the IT department can even help keep a company out of an economic stall and so I though that there was no problem that an IT department couldn’t solve. It turns out that real life is not nearly so neat.

Dr. John Camillus has spent the past 15 years studying how companies create their own strategies. During this time he has uncovered what he likes to call “wicked” business problems – strategy issues that are difficult because our traditional processes for solving problems just can’t resolve them. IT departments face these types of problems internally as well as facing them as part of a company’s overall strategy planning process. Wicked problems can be especially trying for IT departments because they seem to resist being solved by our standard techniques of gathering more metrics, revisiting the core issues and creating a more detailed definition of them, or even the time honored technique of breaking the big problems that we can’t solve down into smaller problems that we hope that we can solve. Dr. Camillus says that not only do our traditional ways of dealing with problems not work on wicked problems, but they can also make things far worse.

Dr. Camillus recently wrote an article for the Harvard Business Review in which he discussed wicked business problems. In it he stated that organizations, like an IT department, will most likely encounter a wicked problem when they are facing either a period of constant change or have encountered challenges that are bigger then they have ever seen before. Within an IT department, it won’t just be the technological complexity that make a problem a wicked problem, but rather all of the social issues that come along with it that will turn it into a wicked problem.

How can you tell if your problem is a wicked problem? It would be nice if wicked problems came labeled as such. However, they don’t. Having the ability to identify a wicked IT problem early on can save any IT leader a significant amount of time and grief. You won’t be able to tell just by looking at the problem itself, but rather you have to take a look at what surrounds the problem. Specifically, if a problem is causing confusion, discord among your IT team, and there has been a distinct lack of progress in creating a solution for it so far, then there is a good chance that you are looking at a wicked problem.

Just to make sure that you really do have a wicked problem and not one of those more common really, really hard IT problems, there are some additional criteria that you need to check before you can call an IT problems a wicked problem:

  1. Too Many People Are Involved: A problem that has too many people who are impacted by it starts to look like a wicked problem very quickly. Each person who has a different vested interest and is working on a different set of priorities will contribute to making a difficult problem into an unsolvable wicked one.
  2. The Cause Of The Problem Is Not Clear: There is no single cause for the IT issue that you are dealing with. Generally there are multiple sources that have fed the problem including competition, issues with employees & staffing, company strengths that have become decrements, and a traditional domestic vs. international focus can also compound the problem.
  3. The Problem Is Shaped Like A Blob: This is an especially tricky characteristic to deal with – the problem seems to change shape everytime you try to deal with it. This makes it hard to “get a grip” on the problem and so you may not have any idea as to where to start.
  4. You’ve Never Seen Anything Like This Before: How can you solve a problem that doesn’t look like any other problem that you’ve ever seen before? When you face a problem that you’ve never seen before, the question of what tools or techniques to use to solve it becomes even more critical.
  5. There Are No Signs Showing You The Right Direction: Most problems come with some sort of indication of what the correct next thing to do in order to solve it is. However, wicked problems have no such indicators. You are truly on you own here.

So what’s an IT leader to do once he/she has spotted a wicked problem? One key thing that Dr Camillus has learned is that wicked IT problems can not be solved. Instead, you need to find ways to mange them. How to do that is what we’ll talk about next time…

Have you encountered any wicked IT problems? Did you know it was going to be a wicked problem right off the bat or did it take awhile to discover this? What did you do about it? Were you ever able to solve it or does this problem still exist? Leave a comment and let me know what you think.