Take Aways

  Take Aways

 

Take Aways
Services
Clients
Approach
Delivery
Who We Are
Talk to Us
Helpful Links
Home


The CIO Behind the Curtain:
A Classic Tale
by Eileen Cline Strider
Also published in Auerbach's IT Performance Improvement, Volume 1, Number 10, February 1999

 

I was CIO for a Kansas insurance company for four years. Although I’m not a Kansas native, I have developed an affinity for the Wizard of Oz. Remember him? He hid behind a curtain and "feats of stratospheric skill never before performed by civilized men." He spoke in a commanding voice and people quaked in his presence. He had everyone in the Emerald City fooled until Toto pulled back his curtain, exposing him as a man. In my experience, being a CIO is a lot like being a Wizard. I hope this article will help you understand who may be expecting you to perform magic and how you might manage those expectations.

The History of IT Wizards

There is a history of how CIOs became known as wizards, maybe as serendipitous as the Wizard of Oz’s balloon not returning to the fair. Forgive my age as I recite my version of this history.

The BPC Era

There are the BPC and APC eras, or, Before PCs and After PCs. Before PCs were invented (and actually before the term CIO was coined), computers were kept behind the curtain in large, climate controlled rooms. Only computer geeks were allowed behind the curtain. What went on behind the curtain was very mysterious, because as Arthur C. Clarke explained in his Third Law, "Any sufficiently advanced technology is indistinguishable from magic." So, if one could sneak a peak behind the curtain, one would see a wizard standing over a master console where lights flashed and fingers flew over switches. Overnight, reams of paper appeared as if by magic on user’s desks, displaying answers to important problems. Eventually, the magic evolved to where users could communicate with their computer through what the computer wizards called "dumb terminals." But what went on inside the computers remained a mystery understood only by those who could read zeros and ones as if they were words. The computer wizards sometimes predicted with great accuracy when the computer would finish its work. Other times, their magic failed; when it did, their only explanation would be that "a bug was discovered in the computer."

Business users were at the mercy of their wizards and their computer departments. The wizards had the final word. Computer technology progressed significantly in the BPC era, to the point where large mainframes could handle huge amounts of work in parallel and response time was sub-second for thousands of concurrent users. The computer geeks reached a point where they could solve very large, complex problems, given enough time. But only they understood how the magic worked. And even then, they could not predict very accurately how long it would take to perform the magic.

The APC Era

The introduction of the personal computer took away much of the computer magic. In the early days users did have to learn a new language called DOS, which many people found difficult. But Apple and Windows drew people in with a user interface that was in pictures they could understand. Ordinary business people found themselves using word processors. They could solve their own problems on their desktop machine using a simple language called Basic. The term programming was redefined and suddenly, users were sure they understood the computer’s magic. They also knew that it did not take a wizard to program a computer. No longer were they at the mercy of their Information Technology department’s foreign language double-talk.

While the users were busy gaining PC skills, computer manufacturers were moving on, taking advantage of microprocessor advances, making possible a whole new computer hardware environment. Instead of the monolithic mainframe, it is now possible to kludge together limitless smaller, specialized machines that not only can talk to each other but can also share work. These environments can be built in scaleable tiers of two and three levels. But these new environments are also extremely complex to manage in terms of production reliability, performance, security, and networking. Although each piece of hardware may work fine individually, the complexity of the total environments is orders of magnitude more sophisticated than the Wizards’ monolithic mainframes. So, new magic is commanded from behind the curtain in order to provide the levels of reliability and performance that users were accustomed to receiving from their mainframe machines.

Over the past thirty years, it has become apparent that hardware advances are easier to achieve than software advances. The limiting factor in the application of computer technology is now software development. Everywhere you look, vendors are touting the newest magic to produce software better, faster, and cheaper. Today’s CIO Wizards have many curtains they can stand behind as they decide which brand of new magic to use: the magic behind the OO curtain, the Java curtain, the pattern curtain, the reusable component curtain, or the ERP curtain. Each of these curtains claims to have the best magic available, yet much of the magic remains very difficult to perform. Finding, hiring, and retaining trained magicians is not only difficult but often cost-prohibitive. The learning curves for these new forms of magic are formidable. So, what is a wizard to do? So many magical choices! Yet, horror stories circulate of magic run amok behind the curtains. Many CIO wizards have been sacrificed on the altar of technology magic.

The Allure of the Illusion

I think the allure of wizardry is a natural one for CIOs. As a CIO, I wanted to contribute significantly to my company. I wanted to be respected among the senior business executives for my unique technology talents. Of course, the work I performed was in my chosen field, so I did not consider much of it to be magic. For me, it was mostly hard labor with a significant degree of guesswork - because my chosen field is still an art, at least when it comes to predicting software project outcomes. But, on those occasions when I was able to perform illusions that looked like magic, it felt very good to be respected as a wizard.

The "Wizard Trap"

I call this the "Wizard Trap." I found the trap to be highly addictive, both for me as a CIO and for my business friends. It is similar to a drug habit that has to be constantly fed. As soon as I performed magic once, I was expected to pull it off repeatedly. Who expected this of me? My business folks, of course. But also me. I become ensnared by my own desire to contribute, and to be valued: a natural human desire.

Trapped in Other’s Expectations

The view our business colleagues have of information technology magic has changed. Back in the old "mainframe days" they considered information technology to be magic because they did not understand it. Now, they believe they do understand it, thanks to their hands-on PC experience. This experience, they believe, justifies their expectations of ordinary acts of wizardry from their CIO. Some of our colleagues do not understand that what they ask for today still requires magic, given the constantly changing, often immature state of technology. For instance, implementing a three-tiered, geographically distributed system using reusable components performing with subsecond response still requires "spectacular feats of stratospheric skill." Delivering large-scale software development projects on schedule, within budget, and with high quality still requires highly practiced software engineering and project management magic. But, business people have told me, "It can’t be that difficult. I could do it with a spreadsheet on my own PC."

Because of the rapidly-advancing state-of-the-art, CIOs now have to perform magic when their business colleagues no longer believe they are expecting magic. This challenge can quickly turn the perception of a CIO from a wizard into "a very bad person" and of a competent IT staff into a bunch of slackers. These perceptual changes can create a deep chasm between business expectations and IT realities.

Trapped in Your Own Expectations

I found that I was also very skilled at making matters worse for myself. I became convinced that I "should be" able to perform magic upon command. Just like the Wizard of Oz, I empathized with the business people’s need for my illusions. Yes, sometimes they were just pulling my leg. But, more often than not, the business really depended on the outcome of my wizardry to survive and thrive. The time had truly come when IT was strategic to the business. And I was highly motivated to succeed, both for their sake and for my own. I had lots of help from the trade journals in this insidious deception. Regularly, IT periodicals touted stories of my peers succeeding beyond my wildest dreams. So, if I could not do it, there must be something terribly wrong with me.

This thinking process succeeded in propelling me deeper into the Wizard of Oz Trap. The Trap became a rat hole for my self-esteem. How could I possibly expect myself to regularly perform acts "never before performed by civilized men?" The harder I tried to force magic to happen, the worse things got both for me and for my staff. Because my staff understood that it was to their advantage to help me deliver magic, they became sucked into the Wizard Trap along with me. Soon, the collusion spread to the entire business. I found myself living in the Emerald City and I was the Wizard of Oz. How long could I keep this act up before it all came crashing down around me?

Sometimes, like Dorothy, I think I must have dreamed all this. Perhaps. But the Emerald City seemed real when I was living in it. As I write about it now, the foolhardiness sounds so obvious. As a consultant, however, I find myself working with CIOs who are not aware they are living inside an illusion; not only living in an illusion, but perhaps even creating one in their company. You might be asking yourself, "How can CIOs become so blind?" Well, it is like seeing air. You cannot see it when you are in it and when you are breathing it everyday. You do not even notice it. You cannot see it until it gets so polluted that you can barely breathe. And that is exactly why the Wizard Trap is so insidious. Even after you see the Trap, it is hard to imagine that anything other than the illusion is possible.

Surviving in The Emerald City

Does your life as a CIO have to be an illusion? Do you have to hide behind a curtain pretending to have all the answers? Perhaps, but as any IT manager worth his or her salt will tell you, "It depends."

Perhaps the answer is, to some degree, "yes." After all, there are times when you can magically produce solutions that are real, and not illusions. And I certainly want to give you credit for these successes. On the other hand, if you cannot face the pain of reality, perhaps the illusion has to be maintained. To face reality voluntarily takes a great deal of courage. It is much easier to continue living the illusion, at least until you are forced to face reality. But eventually, reality exerts itself, not in the form of a small dog named Toto, but often in the form of a large, critical project gone bad. When the curtain is pulled back , your humanness is exposed in a very public way. It is embarrassing and it hurts. It inflicts heavy damage on your credibility and may even cost you your job, and your reputation. But remember, as a CIO, you do get to decide how to deal with the expectations others have of your own wizardry.

My personal lessons for managing wizardry expectations were painfully expensive. It was not always easy to find my courage. I hope that by sharing my "lessons learned" with you, your personal price may be lowered. Here are four.

Lesson One
Decide to live in the Emerald City, or in Kansas

Yes, you do have a choice about this. You might decide to live in an Emerald City illusion for as long as it lasts and take your lumps if and when reality catches up with you. This is a very attractive option. Maybe you will be luckier than I was. Just remember what Dorothy told the Wizard: "If you were really great and powerful, you’d keep your promises."

Or you might to decide to keep in touch with reality. The tricky part of this decision is to recognize the illusion while living it, given its power to deceive you. Here are some suggestions. Find yourself an outside consultant or coach who does not live in your illusion. Ask this person to give you information about his or her sense of what is really going on, to help you see the air you are breathing more clearly. Choose a person whom you really trust to help you see what you are contributing to the illusion, and to help you deal with how you feel about it when reality sets in. Keep in touch with independent industry analysts who will tell you what they see happening in other companies, and not just parrot trade journal propaganda, paid for by advertisers.

Lesson Two
There may be times when you should stay behind the curtain.

You may realize that something is an illusion, but decide to allow it to continue. For instance, you might realize you are maintaining an old system without the source code. You may decide to let this continue, knowing the system will be replaced soon. This is different from "living the illusion." In this case, you know it is an illusion but you choose to let it be. This is sometimes a very wise decision that both recognizes and accepts your limitations. I worked in an organization once where the "big boss" lived under the illusion that bullying and humiliating people was successful management magic. It was apparent to me that he was not interested in pulling the curtain back on his wizardry. So, I just let it go and looked for another job.

Lesson Three
There will be times when you will want to come out from behind the curtain.

When you recognize you cannot perform the expected magic, you might decide to heed the advice of Glinda, The Good Witch of the North: "The sooner you get out of Oz, the safer you will sleep." You can come out from behind your curtain and show others you are a real human being. You can be forthcoming about what you and your organization can realistically accomplish and negotiate a new outcome. You can help others understand that no matter how hard you try or how committed you are, there are some things that are not humanly possible and that to promise them at this time, would be a deception. This forthrightness demystifies the magic. The process can be an extremely painful experience, but one which allows you to honestly look at yourself in the mirror every morning. It takes the courage of the Lion. If the curtain is going to be pulled back and expose you anyway, you might as well salvage some credibility by telling them before they discover it.

I know from personal experience how hard it is to do what I am suggesting. I clearly recall a meeting where senior business executives were espousing "burning the ships." (In their language, this meant "Let’s not fund year 2000 work to make the current systems compliant.") They believed this would force the IT staff to complete huge development assignments on numerous new systems before the Year 2000 deadline. This was a "bet the company" strategy based on the illusion that cutting off other options would guarantee that new development would be done in time for year 2000. In my experience with very large software development projects, this would have required magic the likes of which had "never before (been) performed by civilized men." And given their organization’s track record of meeting software project schedule dates, it was pure folly.

But the illusion quickly took hold of the meeting’s participants and, within a few minutes it became a rallying point. I had to decide what to do: either encourage the illusion or explain reality. I thought I had a fiscal and managerial responsibility to explain the risks posed by this strategy. The immediate reaction was to hang me from the flagpole outside the conference room window. I was accused of "not being committed enough." "Committed to what," I asked. "I’m committed to this company’s survival beyond the year 2000 and I cannot in good conscience support this strategy when there is no supportable evidence that the strategy is achievable. It’s because I do care that I tell you this; not because I don’t care."

They still did not like me for it, but two weeks later they invited some outside consultants in and asked about their experiences with projects like these. When they heard the answers, they acknowledged that "That’s what Eileen’s been telling us - but we didn’t want to believe it."

In the end, my credibility survived. But it was a tough two weeks while I was the Wicked Witch of the West.

Lesson Four
Take people behind the curtain with you.

Look for opportunities to take your colleagues behind the curtain to experience what really goes on. Sometimes you can do this by involving them in project planning, requirements definition, and testing. When this is not possible, use your imagination to create other ways to demystify the magic and introduce reality. I once re-produced the show called This is Your Life to demonstrate the condition of an old system. Business general managers acted out the significant events in the life of this 25-year old system, demonstrating for the audience of 100 insurance sales people, how the system had deteriorated over 25 years. They all came away laughing but also with a deepened understanding of the history and condition of the system. Using your sense of humor and playfulness is a great way to hold your customers’ attention and educate them about technology at the same time.

Is this a Wizard or a Very Good Man (or Woman)?

In summary, I found being a wizard to be both a blessing and a curse. On one hand, you might be revered like the Wizard of Oz because of the wonderful things you do. On the other hand, you might be found out, only to admit as the Wizard did that, "I’m not a bad man. I’m a very good man, just a very bad wizard."

Or, you might be respected as a good woman who deals with reality in an open, straightforward manner. So, if you cannot leave Oz altogether and therefore sleep more soundly, at least sleep with one eye open to those illusive illusions.

top
HOME
TAKE AWAYS
PRODUCTS & SERVICES
OUR CLIENTS
OUR APPROACH
DELIVERY METHODS
WHO WE ARE
TALK TO US
HELPFUL LINKS
SUBSCRIBE TO EMAIL NEWSLETTERS
SITE MAP
Strider & Cline, Inc.
7420 N. Granby Ave.
Kansas City, MO 64151
(816) 746-8118
info@striderandcline.com
Copyright © 1998-2008. All rights reserved.