List the Key Learnings from “The Adventures of an IT Leader”

Copyright

 

“A hero ventures forth from the world of common day into a region of supernatural wonder: fabulous forces are there encountered and a decisive victory is won: the hero comes back from this mysterious adventure with the power to bestow boons

on his fellow man.”

–Joseph Campbell, The Hero with a Thousand Faces

Copyright 2009 Harvard Business School Publishing Corporation All rights reserved

No part of this publication may be reproduced, stored in or introduced into a retrieval system, or transmitted, in any form, or by any means (electronic, mechanical, photocopying, recording, or otherwise), without the prior permission of the publisher. Requests for permission should be directed to [email protected], or mailed to Permissions, Harvard Business School Publishing, 60 Harvard Way, Boston, Massachusetts 02163.

First eBook Edition: April 2009

ISBN: 978-1-4221-4660-6

 

 

CONTENTS

 

Copyright

Introduction

PART ONE: THE HERO CALLED TO ACTION

1.The New CIO 2.CIO Challenges 3.CIO Leadership

PART TWO: THE ROAD OF TRIALS

4.The Cost of IT 5.The Value of IT 6.Project Management 7.The Runaway Project 8.IT Priorities 9.IT and the Board of Directors

PART THREE: THE HERO’S ORDEAL

10.Crisis 11.Damage 12.Communication

PART FOUR: THE HERO BREAKS THROUGH

13.Emerging Technology

 

 

14.Vendor Partnering 15.Managing Talent 16.Standardization and Innovation

PART FIVE: MASTER OF TWO WORLDS

17.Managing Risk 18.Looking Forward

Epilogue

Notes

Ways of Using This Book

Glossary of Acronyms and Terms

Acknowledgements

About the Authors

 

 

INTRODUCTION

The Adventures of an IT Leader invites readers to “walk in the shoes” of a new CIO, Jim Barton, as he spends a difficult year learning IT leadership at the IVK Corporation, sidestepping the pitfalls that make the CIO job the most volatile, high-turnover job in business.

Although this book is based on the authors’ years of firsthand experience with diverse companies and managers, the IVK Corporation and its staff are fictional. As the story begins, the midsize growth company is attempting a turnaround following a period of slowing business performance. The stock price has fallen substantially as investors have adjusted their expectations of the firm’s growth. An aggressive new CEO, Carl Williams, takes over and assigns a new management team. In the process, CIO Bill Davies is fired and Jim Barton, former head of Loan Operations and a talented general manager, is appointed CIO. Barton has no background in IT—none at all. The story follows Barton as he figures out what effective IT management is all about and deals with issues and challenges of the job. The financial and other information about IVK in chapter 1 provides a cogent snapshot of the company’s situation as the story begins.

 

 

The Main Characters

In order of appearance…

Jim Barton: The new CIO of IVK. A talented and ambitious general manager, Barton knows little about IT. He sets out to learn quickly and to lead the IT department toward renewed growth, stability, and strategic partnership within the company—but not without facing serious challenges.

Carl Williams: This bold turnaround CEO is high on ambition and short on patience.

Maggie Landis: A savvy management consultant and Barton’s girlfriend, she often provides Barton with valuable insight, references, and perspectives.

The kid: Wise beyond his years, this twenty-something tech nerd, whom Barton mysteriously meets only at Vinnie’s Bar, proves a useful sounding board and source of surprisingly good advice.

Bill Davies: Former CIO at IVK, Davies was fired in part because he struggled with management-level communication. He tells Barton that he “won’t last one year” in the job of CIO.

Bernie Ruben: As the director of the Technical Services Group and longtime IVK employee, nearing retirement and thus mostly immune to concerns about risk to his career, Ruben frequently provides Barton with the candid advice, knowledge, and context he needs to make key decisions.

Raj Juvvani: As director of Customer Support and Collection Systems, Juvvani is part of Barton’s core IT team.

Tyra Gordon: As director of Loan Operations and New Application Development Systems, Carter worked closely with Barton when he was head of Loan Operations and takes the lead on several new IT projects under his management.

Paul Fenton: As director of Infrastructure and Operations, Fenton manages a large and important domain, including IT security, and is part of Barton’s core IT team.

Gary Geisler: As director of Planning and Control, Geisler works closely with

 

 

Barton on IT financials.

John Cho: IVK’s outspoken resident security genius, Cho has a distinct fashion sense and provocative musical talent.

Jenny: Barton’s ever-dependable executive assistant.

Several additional characters populate the story, but are described in context.

 

 

PART ONE

THE HERO CALLED TO ACTION

 

 

 

 

 

CHAPTER ONE

THE NEW CIO

 

 

Friday, March 23, 11:52 a.m.…

 

Jim Barton sat motionless in a blue leather chair, one of several positioned around an elegant glass table at one end of the CEO’s expansive corner office. At the other end, Carl Williams stood looking out a window. The silence grew long. Finally, Williams turned to look at Barton.

“Speechless” was not a word most people could imagine applying to Jim Barton. His energy and outspokenness as head of the Loan Operations department made him one of IVK’s most dynamic executives, a key player and a likely CEO someday—of a different company, if not this one.

But the news Williams had conveyed moments before had left Barton silent, dumbfounded.

A few minutes earlier Barton had rushed to William’s office, summoned for his turn with the new chief. All morning, leadership team members had marched down that hallway one at a time, each after receiving a phone call, each on a journey to discover his or her fate. As the executive assistant greeted him courteously and waved him in, Barton allowed himself some optimism.

Most likely, he thought, he was about to receive a promotion. He’d done a good job, been a big contributor as the company had grown to its present size. Something like “Chief Operating Officer” would fit him quite nicely.

On the other hand, to hear that he was being asked to leave would not have enormously surprised him. He hadn’t done anything to warrant such treatment. But unexpected things happen when companies are in crisis. The logic behind executive appointments, retirements, resignations, and firings was rarely transparent. Sometimes, Barton thought there was little logic to it at all.

The timing of his meeting gave Barton reason for hope. According to word going around, firings, resignations, and forced retirements had been handled in the first meetings of the day. Since midmorning, he’d heard mostly about reassignments. Executives involved in early-morning meetings had departed as soon as they’d finished, but for a while now people emerging from meetings with the CEO had been staying. It was late enough in the day that he might just be in line for that plum job.

But his mood darkened when Williams, standing by the window, not looking at Barton, began to speak. The CEO’s words struck Barton with near-physical force.

 

 

“Jim, I don’t think you’re going to like this very much.” Barton’s mind raced. Why would he wait this late in the day to fire me? What

have I missed or misunderstood? He pulled himself together well enough to answer: “Just tell me, Carl. We’re all grownups here.”

Williams chuckled. “It’s not what you think. We’re not asking you to leave or anything like that. But when you hear what I have to offer, your first inclination may be to think along those lines yourself. Though I sincerely hope not.”

To Barton, William’s gestures, standing across the room, staring out the window— the entire scene—appeared overly dramatic. Although the view from the thirty-fourth floor was enticing, Williams wasn’t simply lost in admiration, he was avoiding eye contact. Barton glanced around the room, seeking additional clues to what might be going on. The office, he noticed, had been completely transformed, all signs of the previous occupant vanquished. That was too bad. Barton had gotten along well with Kyle Crawford, the former CEO. There had been rocky moments, but suddenly, looking back, those didn’t seem too awful.

“As you know,” Williams continued, “the board is determined to get things on track. They want us back on our earlier, steeper growth trajectory. They believe, and I agree, that the controversy that has dogged us for the last eight months has been a damaging distraction. When they brought me in from outside, they asked me to take a look at the company and to formulate a recovery plan.

“As you probably suspected, the board asked me to reconstruct the leadership team, to clear away the ‘rot’ that might remain from the way some things were done in the past. To recommend the composition of a team that could rise to the challenges we are facing in the coming months. I’d like you to be on that team.”

Relief. It didn’t sound like a demotion. Williams continued. “It has been a difficult process. I haven’t told anyone else this, but the first time I

went to the board with my proposed team, they balked. They asked for additional changes. I had originally proposed a very different role for you than the one you’ve ended up in.”

An unusual assignment. I can live with that. Spirits lifting, Barton made a constructive noise: “I’m willing to do whatever will help,” he offered. “You know me, Carl. I’m a team player.”

“I’m delighted that you are taking that attitude,” said Williams, who smiled but maintained his place at the window.

“You see, after a considerable amount of shuffling and reshuffling, and having discussed this with the board extensively, we’ve…” Here Williams drew in a deep breath, “Well, we’ve decided that you should be our new chief information officer.”

This was the news that had knocked the air out of Jim Barton, reducing him to his unfamiliar wordless state. After allowing Barton a moment for thought, Williams finally turned away from the window. Barton felt the boss’s gaze burn into him. Finally, Barton

 

 

managed to babble: “CIO? You want me to be the CIO?” “Davies has been overwhelmed in that role. You’ve been one of his most

outspoken critics.” “I know, but… I’ve got no background in information technology.” “By all accounts, you have a lot of thoughts on how IT should be run. A lot of

people think you have pretty good thoughts about this. I think you’ve said a few things along those lines to me, even in my short time here. Unlike Davies, you’ll report directly to me.”

Not yet able to unpack a tangle of additional objections all crammed together in a ball at the top of his mind, Barton simply repeated himself: “But I’ve got no background in IT.”

“And Davies has a lot. That clearly doesn’t work, so we’ve decided to try something else.” Williams moved to the table and sat down. The CEO leaned forward, now locking eyes with his subordinate. “You’re a good manager, one of our best. You may not know much about IT, but we think you’ll figure it out.”

“I’ll figure it out?” “Yes.” He nodded and leaned back in his chair. “It’s very important, you know.” “I know it’s important. I’ve been saying that myself.” “A lot of people have heard you, loud and clear. The members of the board of

directors agree. We’re not a small firm anymore. Haven’t been for a while. Increasingly, we’re more of a financial services factory. But we don’t come close to running the company that way yet. That’s got to change. And a huge part of the change will be IT.”

Barton was helpless to disagree. Williams was paraphrasing arguments that Barton himself had made many times. When he’d made these arguments, though, he’d never imagined that it might become his job to act on them. The sobering thought that he might need to figure out how to implement his own recommendations helped him recover.

“What’s going on with Davies?” asked Barton. “Gone,” said Williams. “This morning.” So there would not even be a transition period. Just as well. Barton had never

gotten along with Davies. Davies didn’t like Barton, and who could blame him? Barton had been very critical of IT. He wasn’t proud of it, but he’d even occasionally stooped to making fun of Davies’s weird taste in neckties.

“Carl,” said Barton, “I just don’t think I’m the right choice. It’s not the place I can add the most value. Can I ask you to reconsider?”

Williams stood, strode to his desk, ready to move to his next meeting. “It’s done,” he said. “I know it’s a shock, but I think this is a fundamentally sound choice. Think about it. If you can manage a modicum of objectivity, I think you’ll see that it’s a good idea. As unexpected as this may seem, it’s not a punishment. IT is a problem area. You

 

 

are a highly regarded fixer. It’s going to be hard, but if you succeed, it will be very good for this business.”

“I just can’t see it at the moment,” said Barton. “Give it time,” said Williams, impatience creeping into his voice, “but not too

much time. I sincerely hope you won’t do anything stupid, like walking out. Let me know what you decide.”

The meeting was over. Williams still had many others to talk to before his day was finished.

Barton stood and shuffled toward the door, but turned back as he approached it. “Thanks, Carl,” he said, automatically. Williams looked up, trying to determine whether Barton intended sarcasm,

deciding that he did not. “You are most welcome,” he said. Then he looked down at a sheaf of papers on his desk, to remind himself who was next on the day’s meeting schedule.

 

 

Friday, March 23, 2:41 p.m.…

 

A small crowd was forming outside Barton’s office. All day, eager IVK employees had been working on a big whiteboard in the back of a storage room to create a chart showing the new management team for the company, as well as they could discern it. It was detective work, following clues to possible scenarios and likely conclusions. All of it would be announced soon enough, of course—probably as soon as Monday—but curious souls could not wait that long. Besides, it was fun, in a fatalistic sort of way, this sleuthing for facts that might have implications for all, their jobs and careers. Certainly more fun than fretting or doing their desk jobs.

Much was known. Some executives had told people of their new assignments. Others’ roles had been determined by mysterious, undisclosed means. Still others had been escorted from the building and were presumed gone for good.

Jim Barton remained the biggest puzzle. He was still present, but had said nothing to anyone about what Williams had offered him, and he was an obvious fit in none of the remaining slots. When inquisitiveness overwhelmed them, people gravitated to the corridor outside Barton’s office. The bold ones squinted through glass and half-closed blinds to try to see what he was doing.

Barton was oblivious to their attention, lost in a thick fog, oscillating between anger and excitement, as unsure as he had ever been about anything. One minute he’d decided to resign, the next he was jotting notes for improvements to IT processes. He’d skipped lunch, a bad idea he realized now. At 1:35 p.m., he’d swiveled his chair around to the computer screen and had begun searching the Web. Now his eyes were locked at a focal distance of about sixteen inches, on the surface of the computer monitor. From within his sphere of intense concentration he could not have seen people peering in at him even if he’d looked right at them.

The first thing he had typed was “IT Management.” Google informed him that it had located 1,240 million Web pages on that subject. He clicked on the first of these; what looked like a table of contents for a magazine appeared. He scanned it. “Outsourcing to India.” That seemed like a legitimate management issue. The next few items, reviews of new devices, not so much. Then came stories about companies that had succeeded with things that had techie-sounding names: “Virtualization.” “Managed services.” Acronyms lay strewn about the page: SaaS. SOA. PLM. ITIL. SSL. VPN.

 

 

Most of it didn’t look like “management” at all. This was one of Barton’s pet peeves. He used to say it to Davies, all the time: “IT management has to be about management. Talk to me about management. Profit. Risk. Return. Process. People. Not Trojan this or blade server that.”

He stood up, moved to his whiteboard, and erased everything on it. Then, at the top, in big, green letters he wrote, “IT management is about management.” He underlined the second occurrence of the word “management” and looked around unsuccessfully for a pen of a different color that he could use to emphasize the word even more.

For a while, he just stared at what he had written. Then he rolled his eyes and

slapped the green pen back onto the whiteboard tray. “That helped a lot,” he said sarcastically.

He moved back to his chair and started surfing from link to link, not pausing to read most pages. In the blur of passing pages, a sentence caught his eye, prompting him to stop: “More than any other group within a company, IT is positioned to understand the business end-to-end, across departmental boundaries; no other department interacts with as many different parts of the business as IT.” What a bunch of crap, he thought. As he’d seen again and again, IT people did not understand the business. That was one of his big problems with them. But as he read the sentence again, as he thought about it carefully, he realized it didn’t say “IT understands the business better than any other group.” It said IT is positioned to see better into more corners of the company. IT people have an advantage in gaining a deep understanding of the business. Doesn’t mean they do a good job in seizing that advantage. The potential, though, interested Barton. He had never before thought of it that way.

He surfed. Pages and more pages filled with gibberish. He stopped on a page with a pair of diagrams. The first claimed to portray the usual state of affairs in IT management situations. It showed business knowledge (“smarts” in the diagram) and technical knowledge having no overlap, but needing to be pushed together:

The text that accompanied this diagram suggested that one of the top

responsibilities of the IT manager, one of the most useful things that he or she could do, would be to take actions that pushed the two circles closer together. If this effort was

 

 

successful, that would then result in a changed diagram:

Hmm, thought Barton. Overly simplistic, maybe, but consistent with my

understanding of the situation and the problem. He wasn’t sure what actions might push the two circles together—he’d think more about that. Education, training, came to mind, but there had to be more to it than just that. This way of thinking about the problem suggested, at least implicitly, that communication issues were a big deal. That, too, fit with Barton’s IT-related experiences. If business people and technology people shared more knowledge—more understanding—the end result of that would be an improved ability to communicate with each other, which should result in getting work done more smoothly. The discussion that accompanied the diagram also suggested— helpfully, he thought—that people able to operate in that area of overlap where “Value” was created were a resource to be hired, retained, and cherished. You could keep track of how many people you had who were like that, whether they were business-savvy types in the IT department or tech-savvy people from business units. And you could try to increase their numbers.

Again, Barton surfed. Not far from the circle diagrams, he found a picture that he liked even more:1

The IT leader/general manager capability gap

Something about this diagram better captured the anxiety he felt as he considered

accepting the CIO job. He believed he resided at the top of the “Executives” hill in the picture, near the peak of understanding the company’s general management, business strategy, and operations issues. Moving across to acquire understanding of IT strategy and operations would, according to this depiction, involve crossing a threatening chasm. If he accepted the position, he’d need to come up with a way of building a bridge between the two hills, or crossing from the top of one hill to the top of the other. He had no interest in spending a lot of time down in the valley between the two

 

 

disciplines. But that wasn’t the only source of his anxiety. The idea of tiptoeing across a rickety bridge between the two summits held little appeal. It would be all too easy to fall through a crack in the bridge and plummet to his (career’s) demise. Even thinking of hanging out there in the middle of such a bridge called forth in Barton an acrophobic surge of adrenalin. The words to an old Elton John song, “Rocket Man,” floated through his mind: it would be lonely for Barton out in that space.

The text that accompanied this diagram argued that the valley could be spanned from either direction. A career technical employee could acquire enough understanding of the business to be an effective IT leader. Or a career business employee could acquire enough understanding of technology. It suggested, even, that it might be a bit easier and more viable for the career business leader to work the problem from that side. The rationale: technical knowledge, as much as you needed to know as an IT manager, was relatively explicit and learnable, whereas a lot of the understanding that made managers effective was tacit—mastery of relationships, understanding of political factors, and so on. This argument also rang true. It was in those softer, tacit areas that Davies had repeatedly had problems. Half the time, the guy couldn’t even dress himself to be taken seriously in a business group. No one would’ve even thought of taking him to a meeting with customers, although he had suggested exactly that on numerous occasions.

Barton returned to Google and typed “CIO.” This time only (only!) 134 million entries resulted. He began clicking through them. CIO magazine and CIO Insight were the biggest hitters among the first ten entries. After working his way through a few more pages of entries, glancing quickly at some, he came across a PowerPoint presentation called “A Short History of the CIO Position” and clicked on it. It looked like a presentation prepared by a professor from a school Barton had never heard of. Some of the content was cryptic, but the gist of it was clear.

The presentation described the last decade of the CIO job as a “roller coaster ride.” In the late ’90s, the Internet explosion made tech start-up companies glamorous. This created difficulties for CIOs as some of their best employees left for possible IPO riches. But these events also raised the prestige of the average CIO. Established firms looked to their own IT managers to acquire some of that start-up magic. Technologists, keepers of the magic, became cool. In annual reports, blue suits and white shirts gave way to khakis, neat haircuts to ponytails, b-school types to nerds.

IT managers rode enthusiasm for the Internet to new heights. Higher status meant bigger budgets. IT practitioners throughout corporate hierarchies became vital consultants to business-area partners. Companies reorganized, extracted IT departments from beneath finance, where they often resided (for historical reasons—“data processing” started with payroll and accounting), granting them equal stature with organizational areas such as finance, marketing, and operations. According to the statistics in the presentation, by 2002 barely 10 percent of companies continued to

 

 

house the IT department within finance.2 With reorganization came a seat for the CIO at the senior management table. In a few companies, CIOs ascended to CEO, seemingly altering the historical career path for IT managers.

But the story ended badly. The NASDAQ peaked in March 2000, then plummeted. Within a year, former

high-flying companies crashed. IT workers, accustomed to setting their own salaries, suddenly couldn’t find jobs. People took notice of how few Internet companies seemed capable of generating profits. Established firms whose strategies had evolved vigorously under threat from the IT “revolution” tossed out the new strategies and reverted to old ones.

Revenge of the nerds gave way to revenge of the cost accountants, dot-com to “dot vertigo.”3 With consummate bad timing, large IT projects, such as ERP and CRM implementations, stumbled.4 Costs overran budgets; benefits undershot expectations. IT project failure was nothing new, but as technology lost its luster such failures earned renewed scrutiny. Projects were cancelled, budgets slashed.

By 2003, IT managers were living in what one consultant phrased a “hunt-kill-eat” climate. Grand visions and strategies that had seemed so important a few years earlier now elicited disapproval. Executives who had been eager to discuss IT-enabled futures were no longer in the mood. These harsh realities descended on IT managers and put them into basic survival mode: hunt, kill, eat.

Cost savings became the project mantra du jour. Subject to tightening budgetary control, the typical IT organization became reactive, with few new applications being developed. Press accounts in 2003 traced the CIO’s fall from grace. Old organizational arrangements, such as having the CIO report to the CFO, reappeared.5 The need to comply with new legislation such as the Sarbanes-Oxley Act of 2002 once again made the CIO job seem closely aligned with finance. The number of CIOs reporting to CFOs doubled, and the average CIO salary dropped.6 CIO magazine ran a cover story called “The Incredible Shrinking CIO” (“Their budgets have been cut, their work’s been outsourced, their staff’s been downsized, and they’ve been pushed off the executive team”).7 The roller coaster that once carried IT managers so high now hurled them earthward.

By 2006, the presentation concluded, many CIOs had lost seats at executive tables. Their organizations were increasingly being shipped off to vendors, both domestic and overseas. On the other hand, the emphasis on IT as purely a cost-cutting tool was easing a bit. Improved economies had CEOs looking for ways to increase revenues again, turning their attention from bottom to top lines. In some companies, IT was enjoying a mild renaissance as a possible enabler of new growth. A few companies drew senior IT executives closer into corporate governance by establishing IT oversight committees on their boards of directors. 8

Barton thought back through the history of IVK. During the dotcom craze, IVK had

 

 

been very small, one of a breed of corporate creatures that was rare in those days, a non-tech startup company. When the bottom had fallen out of the tech market, it was a very good thing that IVK had never quite gotten on board the Internet express. Throughout much of the crash-and-burn period for Internet startups, IVK had managed to grow.

The part about IT being a potential source of growth for a firm excited Barton. He wasn’t quite sure what it meant, but he wasn’t ready to discount it either. He remembered Davies arguing that superior technical features that could be effectively demonstrated to clients could be a factor in closing deals. That’s why he’d wanted in on meetings with customers. The idea of Davies and his weird neckties sitting down with customers had obscured serious consideration of this argument.

Surfing just a bit more, thinking about wrapping things up and taking his decision home for the weekend, Barton stumbled across a sentiment that he appreciated. It proposed that IT managers try a thought experiment:

Imagine your day-to-day work. How much would be left to do in a day if a moratorium were declared on discussions about specific technologies? In how you think about IT management, how much would there be—principles, philosophies, practices—that could be said to be independent of the underlying technologies?

Because the world was still reeling from the aftershocks of the Internet crash, this

article said, it was essential that IT managers understand and demonstrate to others that the need for shrewd IT management does not vanish when over-hyped technologies do. If the field of IT management was to mature, to take its rightful place in the pantheon of management ideas, it must have substance beyond the specific objects of its actions. The article finished with a flourish:

The core of IT management—the management content—is not transitory. Just as the fundamentals of, say, finance or marketing, remain relatively stable at their core, so are the fundamentals of IT management.

If this was true, Barton thought, then there was hope for him in the CIO job. He shut down his browser and stood up, reaching for the coat on the rack behind

his chair. Finally, looking toward the door, he noticed the sizeable group of people gathered outside his office.

“What is it?” he asked them, as he emerged with coat on and briefcase in hand. No one said anything. He looked from one to another of their sheepish expressions. Then he singled out someone who worked for him—or who had worked for him—in Loan Operations.

“Jackie, what’s going on?”

 

 

Jackie gathered her courage and told him: “We’ve been trying to figure out where you fit in the new management team. We’ve figured out pretty much everyone else, but you’re a puzzle. And,” she quickly added, “of course those of us who work for you hope you’ll continue to be our boss.”

 
"Looking for a Similar Assignment? Get Expert Help at an Amazing Discount!"