Monday, August 30, 2010

Oh My God not a CIO, but a CDO (Chief Disinformation Officer) !

The other day, I found myself aghast by the onstage passions of learned men—those who had absolutely no kind words for the CIO. I tried to get up from my seat in the audience with a wish to raise my voice against what was going on (CIO bashing), but something invisible pulled me back. The 400+ audience comprised largely business folks (with probably a handful of CIOs), and that was their reality. I felt sad, as I internally seethed with no avenue to vent my feelings. I wanted to tell the poor audience that the CIO does not stand for Chief Invisible Officer—or clarify that they are not CDOs (Chief Disinformation Officers). So I began to analyze their reality, hoping to catch some of them later during the event. But, let me start from the beginning.

The event was a leadership summit attended by a cross section of global CEOs, Board Members, CXOs from various functions, and a few invited CIOs who were categorized as business leaders—not just a technology CIO. The setting was a panel discussion between few thought leaders, a senior Asian government bureaucrat, and a couple of CEOs; the topic, the economy, growth challenges and opportunities. Everyone was enjoying the insights and the rich knowledge being shared, as the subject veered towards business analytics, IT and the CIO.

It was evident that for most speakers that the CIO was an inept technical being—rarely visible except when something stops working like the Boardroom projector or WIFI. Beings for whom the phrase Business IT alignment (BITA) is foreign, while IT feeds the hapless business with inaccurate information. They evidently experienced the CIO’s challenged ability to come up to a level of basic understanding of business drivers. The CIO contributing to business discussions was alien to them. Thundered a bureaucrat, “I have only seen Chief Disinformation Officers, not Chief Information Officers …” Others almost broke off into a spontaneous applause.

Though a CEO did appear a bit uncomfortable, he did not consider it prudent to disagree. The thought leader commented on the CIO’s ability to stay invisible most of the time, and thus christened him “Chief Invisible Officer”.

As I walked out of the auditorium thinking about this discussion’s various aspects, I reflected on my experiences within my multiple CIO roles, interactions with peer CIOs, vendor speak, and discussions with CXOs across enterprises big and small. My reality appeared a lot different from what I had heard from the Magi, who have seen more of the world than I have, but from a different frame of reference.

Are CIOs living in illusions of grandeur in their castles far removed from reality or the experiences, especially of the government speaker as an exception? With some relief, I recollected many Indian enterprise CEOs talking positively about the contributions made by their CIOs and IT organizations. Of certain CIOs who have also took additional charge of business, as well as a few CIOs who have also led cross-functional enterprise projects that made a difference in difficult times.

I guess reality is multi-faceted and not bipolar. Everyone reflects their reality and experience; the world is full of diversity that cannot be captured into a stereotype. Many CIOs I know would react similarly upon hearing about the above discussion, while a few CEOs (hopefully none) may actually be able to associate with the panel’s experiences. As enterprises invest significantly in IT enabling the enterprise, they also recognize the importance of a CIO leader who can walk lockstep with other CXOs while working towards achieving excellence using technology driven efficiencies and innovation.

I believe that a consistent movement is required towards spreading the good work done by many CIOs in conjunction with their CEOs. The learning from these can be applied towards improving the kith and kin. It is also important to talk about and discuss the challenges faced so that everyone does not have to rediscover them as a part of evolution—not just in CIO events, but also in industry and other CXO events. After all, the wheel needs to be discovered only once, and then it’s about replicating success.

Tuesday, August 24, 2010

Mobile computing and security paranoia

The last few weeks have seen many news and analysis items on the enterprise mobile market leader, a player that made ‘email on the go’ a way of life, in addition to creating sore thumbs and marital discord for many corporate executives. After all these years, now there are growing concerns around national security in many countries around the world, not just corporate data compromise.

A few countries have taken a tough stance banning the service or seeking the key to monitor all traffic. The European Union decided to totally shift away to a popular consumer phone for their state offices with 20K+ users. The phone’s largest users as well as the associated services are worried about whether they will be required to shift away within a short span to another option. They are scared about imagining life without the familiar buzz every few minutes (of another email) and business applications.

Today we cannot think of work life without access to email, corporate applications, sales data and many more on the mobile. These devices have made 24X7 slaves out of their owners. Expectations of instant response to a message (irrespective of the hour) are becoming the norm. This increased productivity is now factored into the workload. Apart from enabling the sales force with planning, reporting and sales data, mobile devices have provided even the typical desk bound executive an ability to stay connected at home. Thus enterprises have seen improvements that were not possible earlier. Suddenly, all this appears to be under threat.

Should the CIO be worried about this looming uncertainty? While a total shutdown is not imminent, restriction in services is a reality. This may extend in the future and cripple the basic functioning of these devices.

To me, the answer is a resounding yes. Country laws and regulations are paramount for every entity operating within the geographical boundaries. There is no circumventing these; so if applications depend on a type of service, they may have to be rewritten or discarded. Alternatives should be explored and options made available, should a switch be required to reduce the adverse impact. This should be discussed with the management and the level of impact (if any), be communicated clearly and explicitly.

With an ever increasing number of mobile devices deployed by the corporate or just connected to the enterprise (employee owned), it’s important to periodically assess and review mobility solutions and options. Work with the service providers to create an insurance policy. No one wants to die, but insurance always makes sense.

Monday, August 16, 2010

Strategic or Operational, the choice is yours !

Recently, I met a CIO who was berating the fact that whenever (which is infrequent in any case) a meeting was scheduled to discuss the strategic IT agenda, the gathering ended up discussing operational issues in almost every case. This was leading to a buildup of frustration, and the CIO was wondering if the business had no interest in pursuing the strategic alignment of IT for their enterprise. As I listened to these woes, I realized that the CIO had a remote possibility of getting there. This was not because the company did not understand or appreciate the value of IT’s contribution, but since the malaise had its roots in the way IT was engaging with the rest of the company.

Every CIO aspires (and rightly so) to create a significant impact to the company with the help of tools and IT enabled processes that give them tactical advantage many a times. IT organizations which are able to create several such initiatives sustain the benefits that IT provides, and creates IT advocates from within the business. However, this is possible only if everything else is working hunky dory, or at least has a jointly agreed review process that allows the organization to conduct a dialogue that focuses on the issues and challenges they face.

Periodic review meetings with different functions (like finance, marketing, sales and production)—singularly or jointly—provides a framework to list, review, mediate as well as track issues that are irritants to daily chores and operations within the enterprise. Over a period of time, as the IT organization resolves issues and engages in an open dialogue, these meetings become a regular way of exploring new opportunities that allow for mutual win-win situations. The assumption is that these issues are resolved to the satisfaction of “users” within the agreed to timelines. Where the formal review meetings are not the norm, any meeting that discusses IT in any shape or form becomes the ground to rage war with the CIO.

My CIO friend suffered from this lapse. He considered it inappropriate to engage the business in operational meetings, as he wanted to discuss only the strategic agenda. His team worked diligently to address operational issues when they were brought to their notice (normally when it was a crisis). As a result, the IT team was always fighting fires, without opportunities for an across the table discussion. This lack of a structured review mechanism ensured that the CIO rarely had an opportunity to table the strategic agenda which he was passionate about.

CIOs should balance the need for operational reviews, along with discussions that look at the long term impact created by innovation and new technology. Failure to engage the business across both planes will result in the strategic agenda being hijacked and loss of credibility to deliver business as usual. Such situations just end up further distancing the Business IT Alignment (See BITA).

Monday, August 09, 2010

Weather predictions and the CIO: enough of Cloud Computing

Last month, I was part of a two day gathering (attended by a little less than 100 CIOs) at a great beach resort in the wonderful locales of Goa. It had stopped raining after 20 days of incessant rain, said the lady at the Reception while welcoming us. The next few days were expected to be cloudy, with some sunshine bringing smiles—the CIOs were looking forward to rewind, relax, and network while exploring some serious thoughts on IT during the day. Weather stayed faithful to the prediction—apart from the occasional showers, the sun played hide and seek with the clouds. I could recognize cirrus, nimbostratus and cumulus.

As the conference progressed, it was evident that every IT services and product company (irrespective of what they had to offer), created some connect with cloud computing. We had power management, data center hosting services, servers, virtualization, software, telecom services and some of the global top five IT companies—all talking about cloud computing as the essence of IT. This herd behavior had resonance with hype seen in the late ‘90s around the Web and Internet. Words from the past echoed, “Any company who does not have a Web strategy will be dead in the next decade”. We all know that most of the companies which had only a Web strategy fell off the cliff into the chasm of oblivion. Predictions and promises of the cloudy set mirror the irrational exuberance that was pervasive in the dotcom era.

Do you know what cloud computing is? A rhetorical question; the speaker did not wait for the answer and began his 30 slide presentation starting with what is virtualization. The next speaker added to the misery with green data center and energy efficiency, while acknowledging that IT contributes to only 2% of the carbon emissions. If everyone did their bit, carbon emissions would come down by 0.4%. And, if all of us moved our entire infrastructure to the cloud, maybe that figure will go up to 0.7%. Save the world, move to the clouds. Over the next day, almost everything (from basic definitions to use case models and in between) was pushed down on the hapless audience, which braved the frontal attack while wistfully looking at the sunny sky outside.

Out of courtesy to the speakers and organizers, CIOs continued to field the inane presentations as well as panel discussions on clouds, clouds, clouds, and some more clouds. A resurgent CIO challenged the vendor’s wisdom (on stage) about treating the audience like kindergarten kids. They were challenged on solutions for the enterprise’s current ailments or help for the CIO’s real life problems; not just talk about irrelevant solutions. CIOs broke into spontaneous applause which would bring a politician pride, but evinced no answers from the speaker—again, like the politician. Sections of the audience wandered away after every break, leaving behind a thinning crowd for subsequent speakers. The sun too teasingly invited captives to come out, as the waves’ murmur tortured the spirit. The CIOs saw merit in discussing cloud formation in the skies—no connection with the conference room’s discussion.

With the ecosystem yet to evolve and create meaningful cloud transition strategies for enterprise users, the IT vendors will do a favor by not increasing the hype and aligning to reality. Privately, most vendors acknowledge the fact that clouds are as yet mature, since the concept is surrounded by a lot of questions that require hard answers like security, geographical data residency, privacy, licensing, and many more. Their organizational compulsions prevent them from being honest in a public forum—lest it be seen as them not toeing the party line. Thus, vendors and consultants will do well to listen to their customers before charging ahead on their favorite subject for now, cloud computing.

As the conference was coming to an end, a tweet escaped the room, “Cloud in the sky, cloud in the room, my mind is cloudy too after listening to so many speakers on cloud computing”. Personally, I enjoyed counting the clouds outside than the utterances inside.

Tuesday, August 03, 2010

IT Chargeback, gain or pain ?

Every so often, the subject of chargeback raises its head, and challenges (un)conventional wisdom. In the recent past, it has been in the news as a critical requirement for deployment of cloud computing. Many reports have been written on why IT chargeback makes sense—especially in a diversified enterprise, with multiple business units using IT services provided by a corporate function. Almost everyone uses the rationale that chargeback helps IT allocate fair (?) cost to consumers of these services, and thus possibly provides the budgeting framework for KTLO (Keeping the Lights On) or BAU (Business As Usual).

I looked up IT chargeback on Wikipedia, and found the paragraph below as the closest definition:

“IT Cost Transparency is a new category of IT Management software and systems and that enables Enterprise IT organizations to model and track the total cost to deliver and maintain the IT Services they provide to the business. It is increasingly a task of Management accounting. IT Cost Transparency solutions integrate financial information such as labor, software licensing costs, hardware acquisition and depreciation, data center facilities charges, from general ledger systems and combines that with operational data from ticketing, monitoring, asset management, and project portfolio management systems to provide a single, integrated view of IT costs by service, department, GL line item and project. In addition to tracking cost elements, IT Cost Transparency tracks utilization, usage and operational performance metrics in order to provide a measure of value or ROI. Costs, budgets, performance metrics and changes to data points are tracked over time to highlight trends and the impact of changes to underlying cost drivers in order to help managers address the key drivers in escalating IT costs and improve planning.”

A mouthful indeed! Now, I agree that IT cost transparency matters, but chargeback? Having been part of enterprise IT across industries and IT models that included chargeback systems or none at all, my perspective:
  1. Chargeback systems are important if IT is a “service provider”, and needs to justify every expense; innovation will have limited scope in this context
  2. Chargeback systems will always be challenged by the majority of business units, as being an unfair practice
  3. You will be required to reduce costs year-on-year irrespective of volume, and especially when business goes through recessionary cycles
  4. Even after automation, the effort required for maintaining and managing data can be humungous. This will have the IT team on a defensive stance, churning out unusual associations of metrics in reports
So why is chargeback coming back again? Does virtualization, cloud service, or the next disruptive technology suddenly turn the tables in favor of chargeback? Does it really matter which specific function or business unit pays for the service, considering that it’s a zero sum game for the enterprise? So why should you bring in the complexity of managing unit costs for transactions, memory, CPU, storage, bandwidth, man hours and licenses?

When IT shops struggle to get incremental budgetary support, the practice of chargeback is typically seen as a vehicle to justify the high cost of KTLO or BAU. This is evident if you consider that with the exception of manpower cost, all other metrics have been on the downward spiral over the last decade. Thus, marginal reductions in these KPIs help in sustenance of inflated budgets, while keeping the attention away from metrics that matter (like contribution to business growth, profitability or customer retention).

CIOs should carefully evaluate why they need to implement IT chargeback mechanisms. After all, if they have aspirations to move to the next level of evolution, they should be enamored by business, and not expend energies counting pennies.