(As the first in this series, I’m trying to use construction terms to “build” our investment bank… we’ll see if it adds or detracts.)
As we begin our journey to build our very own investment bank, I’m going to make a few statements that people “in the know” will find both surprising and, in hindsight, very obvious. The topic, as the title states, is technology. Now, here are the statements:
- A major contributing factor to the way banks did business, especially in the businesses that contributed the most to banks’ current problems, was their lack of technology.
- Credit default swaps, in all their glory, had most of their issues rooted in technological inadequacies at various institutions.
- A large portion of the cost structures at investment banks are due to a lack of technological heft.
I know, these seem outrageous. However, as anyone who has worked at a few different firms will tell you, there is a massive difference between a firm with good technology and bad technology. Let me tell you a simple anecdote: When very senior executives at a firm called down to the managers in charge of securitized products, they asked for the current marks and a summary of the various exposures “on the books.” It took about ten people three days to cull through all the various positions, put marks on them, model them, and put a concrete value on them. There wasn’t time to break down exposures by anything but the most trivial categories. Now, why this end product was acceptable is a different issue, but it should be clear that an effort of this magnitude shouldn’t be necessary to answer questions so totally basic in the context of running a multi-billion-dollar (although now with fewer billions) financial institution. A corollary: If it takes you several days to enumerate the positions your area has, you don’t know what it is yourself.
Now, when I speak of technology, I’m really speaking of the specialized systems and solutions used to tackle business issues, and not really the “desktop support” kind of technology. The systems that manage risk and positions, handle accounting, maintain an integrated analytics platform, deliver research and other products internally and externally, manage the human resource functions of the firm, and otherwise grease the wheels of capitalism.
Our technology plan will have a few different components…
Structural Frame 1: Whether our theoretical investment bank is a startup or an established entity, the technology at the core will be home grown.
Structural Notes: Hiring consultants to stitch together purchased solutions and legacy systems is unacceptable. Technology, in order to be most effective, needs to be responsive. When a trading desk needs to run its business, and the system provided is insufficient, then it’s an unacceptable solution, and things will be done manually. Remember synthetic CDOs? Remember the ABX and credit default swaps on sub-prime bonds? Would it surprise you to know that at many major investment banks there was a manual component involved with every single contract and trade? The systems weren’t able to handle these instruments, and these businesses scaled up at a rate that was untenable. Also, there were no analytics available for these products. Businesses bought third party solutions for modeling and analytics, but those didn’t integrate or scale, so all the marks and risk numbers used to compute capital needs and P&L were merely estimates as these businesses were growing the most.
Let that sink in. Is it any wonder the senior managers didn’t know, before it was too late, what the actual exposures were? Had these firms built an integrated set of systems instead of buying a patchwork of specialized programs to solve the most current problem, these issues would not have been nearly as bad. I won’t even tell, in detail, the story about how, years ago, the system for trading credit default swaps at one bank was so difficult to use that they only created one identifier for GM and GMAC, not distinguishing between the two at all. But, when they were both on the brink of being downgraded to junk, but GMAC was de-coupled from GM, I wonder what kind of fun it was to rummage through 5- to 8-year-old confirms trying to match thousands and thousands of trades with the exact entity? Costly? Absolutely. Avoidable? Double absolutely.
On another note, an investment bank need not be innovative, but if it isn’t, then it should be able to mimic innovations quickly. Reporting to management, having an accurate record of transactions and various changes to the firm’s balance sheet, the ability to run various analyses on various products, and other, more basic, reporting functions (not even mentioning compliance and regulatory functionality) are all things that should be implementable once something new hits, and the only way to make these kinds of incremental changes is to build, not buy. A business as complex as an investment bank shouldn’t be reliant on outside parties to build software vital to their business–both from a cost standpoint and from a delay-until-completion standpoint. Further, the procurement process takes months!
Structural Frame 2: The technology part of the organization will not be a monolithic standalone bureaucracy.
Structural Notes: Simply put, technology (the people or business unit) needs to be vested in the process of making a business more profitable. Rather than taking on the normal support role mentality of, “If I say ‘yes’ then I might be wrong and held accountable, so I will say ‘no.'” The best way to do this is to not have technology be its own portion of the organization. Allowing technology to have a seperate seat at the table–or, worse, report into some catchall support person–only contributes to creating a centralized process for technology decisions. Centralizing technology decisions for many businesses with different needs creates unnecessary layering and wedges a huge management structure between the people doing the actual work and the people who are using the product and paying for it.
The final plan, I believe, would be to have as many technology people as possible integrated into the physical workspace of the people that utilize their work. Have investment banking developers sitting amongst investment bankers. Have the developers that build trading applications sitting with traders. The reporting structure should be a matrix of sorts–senior technology managers should report into a business whose technology needs are distinct from other businesses (atomic, perhaps is a better word) as well as a more senior technology person. In essence, people working in technology would be ingrained with the thought that they are there to help–the business unit would be setup as the client and the technology super-structure would be more for managing the processes. Obviously when the business is viewed as the client, technology managers are incentivized to get the businesses what they want, and when the people (both doing the work and in charge of liaising with the clients/business) are integrated (and can see the working environment of their clients and usage of their products) a lot of inefficiency and “lost in translation” moments are avoided. Senior managers really need to think of their business as including technology instead of interacting with it. This is highly important and is much more likely with a structure like I’ve proposed. Also, the closeness will just yield some more technologically savvy people and even encourage people to move between the two “worlds.”
Structural Frame 3: The people who are hired for technology roles will be of a high caliber and will be under a compensation regime and in an environment that sets big technology companies to shame.
Structural Notes: This shouldn’t be a hard line of reasoning to follow, but in general the difference between firms that “get it” and firms that don’t is how they recruit. Having an engineering background, I was recruited for I.T. from a very good school for that sort of thing by a few banks. Those banks have a high correlation to both still being around and surviving the mortgage mess with the smallest scathing in their peer group. I know several people who have told me that some other firms, one that haven’t been so lucky, have absolutely ridiculous and incredibly stupid policies for recruiting technology people. Most notably, one Manhattan firm recruits from local state schools almost exclusively–this is done so that the students they recruit can work part time during their senior year of college. No school in the top fifty or so participates. If one had to draw a grid, and rank various factors as to how important they are, the program I have just mentioned is the most ridiculous, stupid, and demonstrating a complete lack of critical thinking skills (or, for that matter, basic grasp of the business and reality) of the programs I have heard of or encountered. The people responsible for it have all moved on and the firm has suffered greatly from it’s underinvestment in technology.
So, to recruit good people you need a draw. To be honest, most graduates don’t fully grasp the concept of upside or career path–especially not ones in I.T. This makes it simple to get them, just offer a bigger number for the compensation in the first year. While this would work, it should be clear that this won’t help make them much more productive than the average technology drone in an investment bank. Giving technology employees a compensation structure that matches the businesses they are supporting is, in my view, a great solution. Obviously there would be more stability, but there should be a linking of incentives to the business and an interconnectedness in how they think about how technology and the problems facing the business. They should also have an incentive to be proactive and try to advocate solutions to problems they see instead of waiting for others to focus on them–this contributes greatly to becoming a nimble organization.
As for work environment, whenever possible, for groups not truly linked to a single business, like infrastructure groups and the web development team, my focus would be on building a start up-like atmosphere. The marginal cost of things like free coffee, free food, and some extra square footage for odd amenities is insignificant in relation to the quality of the work produced by the people snatched from places like Microsoft and Google versus a lower caliber of student culled from whatever lower-tier school(s) happens to be nearby. When you know your competition and what they offer that you do not, it’s very easy to compete: just offer what they offer. For things that aren’t as timely and linked to a knowing how a certain business runs, there is no problem in creating a lifestyle and work ethic that is free-form as long as it meets goals and needs of the firm. (Note: This isn’t my unique idea. A certain investment bank with a strong brand does this sort of thing already… but I did think of it before I knew that!)
Structural Frame 4: Technology, especially experimental or new technologies, should be used to try to create, or even drive, value.
Structural Notes: This is more a philosophy than an actual directive, but it’s important to taking a firm’s strategy on technology to the “next level.” There is a massive body of knowledge within a firm that is lost everyday due to a lack of effort. Usually the solution is to put humans somewhere and have them manually type in numbers or perform mundane tasks to get this working smoothly. Not in our investment bank! Let me furnish you with an example. The corporate bond market works in an unusual way: traders send around “runs” or lists of bonds with quotes of where they are willing to buy and sell bonds via Bloomberg’s messaging system–they are generally free form text. Why do they do it this way? It’s quick and easy. The firm I worked at didn’t make any effort to collect these pricing levels and store them somewhere. However, for publishing strategy reports, helping the desk find trade ideas based on historical relationships, calculating risk metrics, and any other number of things, this data would have been vital. Technology can easily help to store, warehouse, and serve these sorts of datasets (readily available from the market but unstructured) and help the organization as a whole improve its efficiency. This is just one example, but it serves to illustrate a point that is extremely common in an investment bank–lots of things require information that no one keeps but was readily available. Technology can drive value for lots of internal things by helping to solve problems like this. And, honestly, there are too many things that are out of one’s control not to have an organized and structured solution to the simple things that can be fixed.
Another note on technology, however, is that as the Web innovates social behaviors and collaboration those technologies should be actively examined as potential solutions to problems an investment bank would face. For example, lots and lots of information is needed when talking to a client. Getting good market “color” that everyone can see, and that is available, consistent, and easy to find is important. Perhaps a series of blogs could be used to ensure the delivery of this content is made as efficient as possible. One way I added value at my firm was by knowing as many people as possible. When liquidity started becoming an issue, the people I spoke to on the desk that funded banks in the LIBOR-based funding market explained what was the situation and we were able to assess if we thought this warranted a change in our positions or business in general. If that desk had a blog where they posted color throughout the day and the firm had an easy way to deliver this information to all of its employees, perhaps this could have helped people develop a more specific view on the market and notice some irregularities leading to the current crisis. Could Wikis be used effectively? I’m sure that they could. If it was institutionalized to have an up-to-date knowledge base within the firm, and it was made a priority to keep those things updated, nuances and details on complex transactions could be documented. People could avoid falling into the same traps or having to research the same issues other already have. These are just a few examples of how new technology innovations can be used to create value where it would otherwise be impossible.
Structural Frame 5: Every employee should be very comfortable with technology and make a large effort to integrate it into their work.
Structural Notes: I hate to sound like a snob, but in general, if you can’t figure out things like email and basic spreadsheets, you don’t have a lot of room left to grow. People should learn new technologies as they are available and make an effort to work more effectively. If this isn’t a priority of almost everyone in the firm, then building new systems and integrating things into their daily “workflow” is useless. Part of pushing the envelope on how new things are used means that people will have to learn how to use them. I’ve seen too many people, uncomfortable with a new system, resort to keeping their risk positions and other vital data the firm should know in a spreadsheet. Unacceptable. Now, not everyone has to “ooohhh” and “aaahhhh” over new features and technological platforms, but everyone should be asking themselves how they can use some new technology product to make more money, pitch more transactions, better monitor the firm’s risk, develop a better strategy for investing, or whatever their job entails. I don’t think this is hard, but I do think it’s important. And, with technology employees sitting with business people and understanding how they work day-to-day, the resources to figure out these sorts of things will be much more readily available than at most other firms. (See how the “structural frames” all interplay?)
The Final Inspection
As one can see, I value the little things that help people get 10-15% more productivity out of their daily routine–that’s the edge most firm’s need to excel in what they are focusing on. However, most firms poorly thought out systems and infrastructure issues, especially when it comes to technology, adds a hugely cost-ineffective layer of one-fix-at-a-time solutions that have added up. Why have a system where traders can input their own trades as they do them? Give them a paper record and hire a person, with full benefits and being paid an amount commensurate with living in New York City, to type them in. Oh, and now that the business has grown to three times to trading volume in six months, let’s hire four more people. Why have a system that allows a capital markets person to view real-time quotes in their sector or updates those quotes into a spreadsheet or presentation? Just have a bunch of analysts do it by hand. Why would you want a system that can model securitizations and CDOs and run the numbers effectively? We can have someone do it in a spreadsheet, that’s “close enough.” Although it doesn’t capture the nuanced risk factors, I’m sure defaults will never get high enough to worry about. These are the kind of solutions that, from the start, one should be thinking about. From the first instant it’s possible to fix these, they should be fixed. I think the five parts of the framework I’ve laid out will make a good plan to follow when building the technology part of our investment bank!