The CIO and integrity: this shouldn’t be hard, folks

Surprising and disturbing IT-related news crossed my Twitter feed last night: a well-known CIO is being sued for alleged fraud by his former firm. Allegations are that this senior executive received kickbacks from vendors that he helped connect to the company where he served as CIO and vice president.

My purpose here isn’t to comment on this individual case; it’s now in the courts, information is still sketchy about the details, and I feel that people are entitled to a presumption of innocence while the various legal actions run their course. As Forbes columnist Ben Kepes wrote, though, this is “one for the ‘we knew these things happened but tried not to know about it’ department.” Update as of December, 2021: a conviction and sentencing in the courts).

So let’s broaden the topic to the overall issue of CIO ethics and integrity, particularly with respect to financial matters. As I’ve written before, the head of technology for many companies (certainly all the firms I’ve worked for) stands at the rudder of a very large portion of the overall “spend” for that company. IT infrastructure and systems spending, taken broadly, is often the second-highest category, after salaries, for total annual outlay for a company. The responsibility involved for the senior IT executive cannot be overstated.

HT @marciamarcia

Often when I’ve come into a new CTO/CIO position, I’ve discovered, over the course of the natural “archaeology” that one performs in such a situation, highly questionable business deals cut by my predecessors with outside vendors. I’ve raised my eyebrows and, yes, even occasionally shouted a bit at the incomprehensibility of various vendor arrangements I’ve inherited.

[Read more…]

Starting points for the quantitative CIO: downloadable basic tools

Much as in any field, IT executives constantly have to seek a balance between idealism and pragmatism. Given a particular problem and the range of possible solutions, do we insist on “doing it right”, or do we buckle down and “just get it done”, even with gaps?

There’s obviously no single right answer, which is what makes IT consistently so fun and frustrating at the same time. Over time, though, my own approach has typically been to focus on the continuous improvement aspect of “doing it right”: whenever possible, get something going as a start, then hone it over time as you learn more about the problem and your situation.

Using spreadsheets as a management tool definitely falls on the “just get it done” side of this spectrum of approaches. Spreadsheets are seductively easy, omnipresent, and usable by people with a variety of skill sets and technical savvy.

But there’s a host of downsides: spreadsheets are frail creatures. Errors can creep in fairly easily, even for experienced users, as data and circumstances change, and spreadsheets are especially prone to the incursion of silent errors and omissions when undergoing revision.  And once implemented, in all their imperfection, spreadsheet-based solutions can broaden and become large-scale, long-term systems (I’ve seen this happen again and again).

Yet, I feel that every technology executive should be maximally fluent in spreadsheeting: simple tracking, analyzing, modeling alternatives, understanding costs and risks. The technology provides a readily available, easy way to knock out quick and dirty models that can clarify one’s thinking and approach enormously. They work well, as long as you keep in mind that the spreadsheet is usually a stop-gap, for those times when you are faced with a glaring need and you don’t have time, budget, or staff to implement anything deeper right away.

In an early blog post, I listed the seven areas where a quantitative approach is especially necessary for the technology executive:

[Read more…]

CMO outspending the CIO on technology: “so what?” Here’s what.

Rarely do I write targeted responses to specific blog posts, but last week, a CMO-related article crossed my screen that I think is both representative of many people’s attitudes, and enormously flawed in its assumptions, logic, and conclusions. Esmeralda Swartz, writing for ReadWrite.com, titularly opines the following: “So What If Chief Marketing Officers Outspend CIOs On Enterprise Tech?” Even more grandiosely, the post’s subtitle is “Isn’t it possible that a technology buying process driven by marketers instead of technologists will make things better?

Well, I suppose I should allow that anything might be possible, but no, not by the unconvincing (yet not atypical) line of argument Swartz pursues, and not when you consider standard business realities. Here are a few representative quotes related to the backbone of her argument, namely that buying technology is like buying a new car:

  • “Let’s look at an everyday example. Prior to investing large sums of money in a new car, few people feel the need to master the inner workings of the internal combustion engine. “
  • “Despite all this blindness, for the most part, what we buy doesn’t let us down.”
  • “Ultimately, we’ve got a problem that buying a car solves, so we buy a car.”
  • “Buying software – wait for it – simply because it threatened to get the job done – will likely ruffle some feathers.”

Here’s the thing, though. IT systems are not cars. 

[Read more…]

CDO: The Chief Déjà Vu Officer

Whac-a-mole. It’s my favorite of all metaphors, at least when it comes to applicability to IT. For those who don’t know the background: Whac-a-mole  is a commonly seen arcade game, where plastic moles pop up at random through holes in the game panel. The job of the player, of course, is to pound them down again with a mallet, accumulating points with each kinetic, mind-clearing, vigorous whack. And, of course, the game keeps speeding up. The moles never stop coming.

Any readers who don’t instantly get the clear analogy to IT are probably reading the wrong blog.

A career spent in IT feels like a constant bout of Whac-a-mole. But here, again, is one key recurring “mole” that I find especially irritating: the proliferation, against all logic, of articles and tweets about the demise of IT, the death of the CIO, and how technology is now so easy, so omnipresent, that experts are no longer required.

I wrote about this ever-repeated meme a year ago in a post titled “IT consumerization, the cloud, and the alleged death of the CIO”.  I railed against the meme, pointing out that “this frequent linking of cloud and IT consumerization to the looming demise of the CIO and IT is not just misguided, but actually gets it completely backwards. In fact, I argue that IT consumerization and the cloud will actually elevate the importance of IT within a company, as both a service and a strategic focus.

But IT moribundity is a meme that somehow refuses to, uh, die.

[Read more…]

Book review: The CIO Paradox: Battling the Contradictions of IT Leadership

It’s a universal trait, it seems: we all want to be understood, want the world to see things through our eyes, want to watch the “aha” light go on when people finally realize just how tough we have it and how magnificently we still prevail.

IT people, and senior technology executives in particular, are anything but exceptions to this longing. In fact, it seems that very few other disciplines have to put up with a constant stream of articles and books questioning our very existence, approaches, purpose, and worth (Does IT Matter?, the death of the CIO , etc.). Even the acronym CIO is commonly and gleefully referred to as standing for “Career Is Over”. And you want a downer? Just try googling “average tenure of the CIO”.

A person could downright get a complex here. No one seems to get it! No one understands how tough a job this is! No one seems to perceive the “damned if we do, damned if we don’t” intrinsic nature of our role. I present this syndrome with all due humor (“against the assault of laughter nothing can stand”, said Mark Twain), but I also mean it: is it utter masochism that leads us to choose this “whipping boy” kind of career at this level?

The CIO Paradox, book cover
That’s why it’s so welcome when a book comes along that effectively presents insight and understanding into the “big picture” struggles of today’s CIO, even combined with empathy and warmth. Martha Heller’s The CIO Paradox: Battling the Contradictions of IT Leadership, just out late last year, brims with “been there seen that” deep insight into many of the standard CIO predicaments.

[Read more…]

Novels of IT: The Phoenix Project

Nerd alert: it’s an exciting day for me when someone releases a new “novel of IT”. I’ve made it my mission to find and review several of these (now four) over the past couple of years, and I may be one of the few people out there who has read and reviewed all of them.

To recap: what do I mean by a “novel of IT”? It’s a term I coined to describe a fictionalized depiction of life in a corporate IT environment, usually bearing a number of intended lessons in tow about IT best practices, approaches, pitfalls. They’re generally not works of serious fiction; their audience is usually the lot of IT professionals rather than the broad public. (For example, I don’t include in this category two fine and recommended works that in fact aspire more to literature than to IT didacticism: Douglas Coupland’s Microserfs and Ellen Ullman’s The Bug).

As I’ve traveled through the fictional scenarios depicted in these four books, I’ve evolved criteria for what makes them successful (or not) in my eyes. In a novel of IT, I’m looking for a book that is both reasonably engaging as a novel and one that accurately portrays a broad swath of the inner workings, nuances, and personality types that are typically part of the landscape of IT in today’s world. Reading the book should provide a window into common dilemmas and disagreements regarding IT issues, lending perspective and insight into all parties’ motivations and interests.

I looked forward for many months to the release last week of The Phoenix Project: A Novel about IT, DevOps, and Helping Your Business Win, by Gene Kim, Kevin Behr, and George Spafford,  after meeting and chatting with Gene Kim at a conference back in May of last year. I was greatly impressed at the time with Gene’s general demeanor, enthusiasm, and articulateness. He gave a rip-roaring presentation at the conference on “ITIL at Ludicrous Speeds: Rugged DevOps”: I recommend seeing him speak if you get the chance. I felt certain that his long-promised “novel of IT” would be a worthy addition to the collection of works in this category.

[Read more…]

IT consumerization, the cloud, and the alleged death of the CIO

As with just about any area, IT is a discipline subject to fads and memes, “received truths” that seem to arise in the press or the blogosphere and then ricochet around the echo chamber until they sound plausible even to skeptics. A number of these roll across my Twitter stream every day. But one such meme rises so high to the top that it has to be the sole focus here. And that is the much-repeated “death of the CIO” meme, coupled as it is currently with dreamy visions of the world brought to us by the consumerization of IT and the cloud. They’re all linked, at least in many pundit eyes.

Here’s the gist of their argument: users can go out and get their own technology now; they don’t need IT to do it for them. End-users are now IT-savvy, and can fend for themselves.They’ll bring their own devices (BYOD); they don’t need or want IT to provide devices for them. They’ll procure the services they need and want from the various SaaS offerings in the cloud or from outsourced vendors, and they’ll handle it all themselves.

All this ultimately gets not only expressed as the question of who needs a CIO anymore, it goes even further: who needs an IT department at all anymore? Says one article, “If IT does not provide the end user with the infrastructure they need, the latter can rent it, by the hour or month from companies like Rackspace or Amazon… All you need is a credit card and no approval from IT.”  Other CIO “thought leader” articles feature astonishing blanket statements like, “With the consumerization of IT, consumers can create value for themselves and the enterprise, using technology that costs the enterprise nothing.” And people even take this so far as arguing that the CIO at this point should just leave technology up to the VARs.

Let me be clear once again: this frequent linking of cloud and IT consumerization to the looming demise of the CIO and IT is not just misguided, but actually gets it completely backwards. In fact, I argue that IT consumerization and the cloud will actually elevate the importance of IT within a company, as both a service and a strategic focus.

[Read more…]

Novels of IT, Part 2: Haunting the CEO

Last time, I introduced this series by pointing out that reading what I call “novels of IT” could serve a few very useful purposes for those of us who work in and around information technology.  In fact, I presented a number of criteria that come to mind when answering the implicit question of why anyone should bother to read a novel of IT.

Ideally, it’s because such novels, at their best, can do the following:

  • provide a degree of engagement and entertainment in making their points
  • provide a realistic insight, in a “show not tell” kind of way, into what motivates the typical players in these business scenarios,
  • help all factions (inside and outside IT) come to see the other side’s perspective and arrive at deeper understandings of common problems and disagreements.
  • allow the CIO to hand the novel to his or her CEO or CFO and trust that everyone’s reading of it will help reach common ground in how to collectively and collaboratively approach the company’s goals.
There are, of course, pitfalls involved in constructing such a novel, the foremost of which is falling into blatant stereotypes: most notably, the nerdy CIO who clings to technology and can’t see a larger role for himself or herself. The book I covered in my first post on IT novels, Chris Potts’ FruITion, not only fell into this trap in spades, but took it to a whole new dimension, painting IT in general as basically no longer needed as a separate discipline, and as having become so trivial as to not need an executive at all.
This time, I’ll discuss John Hughes’ recent and excellent contribution to this genre, Haunting the CEO.
Mastodon