Software Development
Blogs and Discussion
developer.*
Books Articles Blogs Subscribe d.* Gear About Home

CIO Spectator

I spent two days at a conference targeted to the highest technology officers and their direct reports. The latter group was easily distinguishable from the former by the absence of key indicators (to borrow one of their favorite terms): crisp suits, VIP ribbons, and complimentary leather portfolios with CIO emblazed on the front. Even without these outward tell-tale signs, one could have presumed the pecking order by the expression on the vendors’ faces upon entering the swooping radius of their booths. Strategic smiles cranked up for CIO consumption fell in proportion to their expectation of a sale.

Under other circumstances we could have assumed good postures, choked back our southern drawls, and pressed the flesh with CIO-like assurance. We’d pretend we had been hand-picked by our CIO as his successor. Instead we opted to congregate conspicuously like gangly teenagers forced to attend a grown-up function, taking comfort in each other’s shadows. We networked, sharing helpful information like which vendor booth was giving out nifty flash drives that converted to a pen and which had such notorious reputations for post-conference stalking that it wasn’t worth leaving a trail for the chance of winning an iPod. Of course if you slowed down at all while traversing the catwalk from conference room to facilities, a vendor would take aim at any prey available (even the skinny, non-CIO variety) and zap your barcode-enabled conference badge. Voila: you became a record in a customer relationship management system. That’s when I would start answering my work phone with a prepared response: “Oh…you really need to speak with our Network Administrator about that. Here’s his number…”

“We’ve got a diverse group here today,” one conference administrator began, introducing the “distinguished panel” of speakers. “Diverse? Really?” A female, non-CIO coworker to my right muttered. “Looks like a bunch of middle-aged white men to me.”

“What animal best describes your leadership style?” The facilitator posed the question to the panel of CIOs while I silently animalified [is there no equivalent to personified?] my own coworkers. One was clearly a bull dog…no, maybe a Pit bull. One was definitely a turtle. A former coworker was self-described as a pack mule. I settled on myself as a hound dog….the faithful sort with tired eyes that can be a pretty useful hunting companion when the spirit moved.

How would these CIOs describe themselves? I figured a gazelle would be a good answer if you wanted to be perceived as agile, but sensitive. A panther if you were more the cunning sort, crafty enough to keep up with the speed of technology evolution. Maybe an eagle? Perhaps a lion, symbolizing an unintimidated conqueror of the technological jungle?

The first response was “a giraffe”. You know…above the forest…able to see the big picture. The second response was…um…a giraffe. (Oops…guess they didn’t discuss their answers beforehand.) The third was “a chameleon.” A lizard that changes colors to suit the circumstances? Well…it could fit. (I was later told in confidence that one of the respondents in question was, in fact, not the animal they named, but a Tasmanian Devil.)

Of course the conference was a fascinating opportunity to observe so many CIOs in close proximity... like a corporate petting zoo. In particular I paid attention to the topics (supposedly selected by the CIOs themselves) that seemed to be foremost in their minds. Last year it was all about risk and outsourcing. This year the buzz was storage management, IP telephony, and next generation wireless…with a few timeless classics such as change tossed in for good measure. As a developer, the catch-phrase that stuck in my mind last year was “code is a commodity.” This year I remember, “You don’t out-task innovation; you out-task execution.”

Despite my propensity for mind-wandering during Powerpoint droning (I planned an entire event menu and made a list of Christmas cards to send during one especially productive session), I realize that the opportunity to get an insider’s view of the CIO perspective is valuable since I will likely spend the rest of my employable years reporting to one.

Huh?

“You don’t out-task innovation; you out-task execution.”

I don't even know what the hell that's supposed to mean. How did the panelists explain it?

I found the comment you made about the focus this year being on storage mgmt and wireless capabilities to be interesting. Those are exactly the things we were tossing around at the company I just left. Wireless for purposes of penetrating the Pac Rim as well as remote administration of the server farm, and then storage mgmt for segmenting the absolute gobs of information we carried for our user base. Storage Mgmt is interesting because the problems we ran into were due to lack of segmentation of different types of data. After solving just the basic problem of not enough space, we discovered that our system would not be able to perform as we wanted it to since we hadn't accounted for how the different types of functionality we provided accessed the disk array. For example, due to decisions made in the long ago past, our 1/2 terabyte library of hosted images also sits on the same array as our OLTP database. Not good. Similarly we also had to provide data warehousing and page counter functionality from the same massive disk array. The bottleneck wasn't the disks -- it was the amount of traffic we were trying to push over the controllers.

This is where the latest trend of renting equipment from hosting providers is becoming so appealing. Instead of buying a new SAN for $80K which will be out of date in 3 years to carve off our image or data warehousing traffic, we can simply rent a device from our hosting facility for $3K a month. Sure we'll pay a bit more over the course of the three years, but they have the headache of making sure it stays up. So when you figure in the cost savings from a personnel standpoint, it's a good deal. Plus you get a new piece of hardware when the provider upgrades. In any case, it allows companies like my ex-employer to segment their infra-structure and create feature-specific silos for optimal performance much cheaper than in the past.

Tight cohesion and loose coupling don't only apply in the software realm.

Stay of execution?

As I recall, the comment, "You don't out-task innovation; you out-task execution" was followed by a comment I originally thought too controversial to record here. It was , "Code: who cares?" Of course these were high level folks and I believe they were saying that it is appropriate to out-task (the word used much more frequently than outsource this year, as though that makes it more palatable) the writing of the code, but not the generation of ideas...the innovation at the core of whatever business you are in.

While this can be true, I think we *do* care about the code, and if it is out-tasked, it should be done so carefully with oversight. Otherwise the in-house folks will pay for it in support hassles for years as standards/conventions aren't followed, etc. Keep in mind that these CIOs were probably not thinking of companies where the key asset is intellectual property in the form of software.

About storage management: Where I work we do have a SAN and a NAS and we keep the databases on the SAN (for relatively expensive high-speed transaction access) and we use the NAS for images and files. At the conference the speakers advocated tiered storage management solutions based on criticality and the number of people who would be affected. Only level 1 data is relegated to the most expensive solution. Apparently it has helped to manage cost in some large organizations where the data gets into the petabytes. They are able to tell the department heads the relative costs and let them judge how much it is worth to them. Otherwise everyone wants immediate recoverability.

Interestingly, on the topic of IP telephony and storage management, there was a good amount of discussion about whether to integrate voicemail into the single Outlook interface. (Ours is done that way: when you receive a voice mail, it shows up in your email inbox and you can play it on the computer or via the traditional means through the phone.) Most of the panelists said that the users love it, but it DOUBLED the amount of Exchange data storage.

The solution your company was using sounds like a good option for many organizations.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Recent comments

User login

About our advertising.

Atom Feed

developer.* Blogs also has an Atom feed, located at this url.

Click here for more information about Atom.

A Jolt Award Finalist
Software Creativity 2.0
Foreword by Tom DeMarco

Recent Posters

Based on most recent 60 days, sorted by # of posts and name.

Google
Web developer.*

Who's online

There are currently 0 users and 24 guests online.

Syndicate

Syndicate content
All views expressed by authors, bloggers, and commentors are their own and do not necessarily reflect the views of developer.* or its proprietors.
Click to read the Copyright Notice.

All content copyright ©2000-2005 by the individual specified authors (and where not specified, copyright by Read Media, LLC). Reprint or redistribute only with written permission from the author and/or developer.*.

www.developerdotstar.com