CIO inverted is OIC or "Oh I See" !
A CIO Blog with a twist; majority of my peer CIOs talk about the challenges they face with vendors, internal customers, Business folks and when things get through the airwaves, the typical response is "Oh I See". Some of you may disagree with my meanderings and that's okay. It's largely experiential and sometimes a lot of questions
Updated every Monday. Views are personal
Monday, March 31, 2014
The King is dead, long live the king
Monday, January 30, 2012
Vendor lock-in
Monday, January 23, 2012
Walk the Talk
Monday, July 12, 2010
What's in a name ?
Flashback to 2002; I interviewed for a Fortune 50 company’s Indian operations. The process progressed well, and I joined the company (which had a federated IT organization). The corporate IT organization was responsible for standards, infrastructure, architecture, and many applications that were supporting the operations. Then we had Manufacturing IT, which focused on the requirements of the manufacturing plants, connecting to suppliers, managing the manufacturing process, and running the warehouses. The company also had an R&D IT function that empowered the large and globally spread research teams with enabling technology solutions that were critical towards maintaining the company’s leadership position. Each IT organization head reported to the respective function head with dotted line to the global IT head; they had the flexibility and independence to create solutions or choose vendors. Last but not the least was the function called Business Technology, into which I was inducted.
Business Technology worked with the sales organization. It existed in almost every country that the company operated in, and reported to the CEO. It was the largest group and also the most powerful, since the sales teams connected with customers, and thus also had the power to garner larger IT budgets. Thus this name signified a closer relationship with business. It provided technology initiatives that impacted life everyday on the field connecting with customers, while competing with others in the industry. Not that those other teams were not aligned to their respective business folks, but the impact of changes was slower, and largely created internal efficiencies or benefit. Thus, every introduction to an outsider required a five minute discourse on why we were called Business Technology.
Was BT any different? We still had our challenges around vendors, change management, new initiatives, budget approvals, technology adoption, political issues, everything that a normal IT organization experiences every day. As the CIO, my role was acknowledged with a seat on the management table, but like every other CXO, it required consistent performance to keep it there. The basic expectation from the CIO was to create business value, challenge status quo, and participate in all discussions around the table that influenced the company’s future direction.
So, what about the role today? The CIO is required to do all of the above, sometimes even fight to get a seat on the management table; in a few cases where the CIO does not report to the CEO, they are dependent on other CXOs to be their voice in the management team meetings. Will the change in name to business technology bring about the transformation and fast track the evolution and acceptance of the function better than when it is plain old IT? I guess not–the enterprise, the IT leader, and the culture largely contribute to its success. BT happened almost a decade back, evolution is catching up.
After all, as the bard said it a long time back, “What’s in a name; that which we call a rose, by any other name would smell as sweet”!
Tuesday, March 02, 2010
Are you happy being a CIO ?
It doesn’t matter which conference you go to, or who is the person at the discussion’s other end — Whenever the CIO’s evolution is examined, the other person always has a view on what should be a CIO’s next role. Multiple propositions get discussed, including that of the COO and CEO. Sometimes, the lateral inclusions are in supply chain, logistics or human resources, rarely in finance or marketing. But is the CIO an interim position that has to evolve into some other role? Why can’t CIOs be happy being good CIOs?
A few weeks back, a reporter called me. She said that I was one of the few people she knew who was happy being a CIO. She had not come across too many such people within her contact book despite having hundreds of listed CIOs. So this discussion continued on whether a CIO should necessarily move on to another role. If yes, which one?
I wondered a bit as she continued her excited chatter — what’s wrong in being a CIO, and that too a good one! Why is the world interested in my evolution to another CXO’s role (as if other CXOs would be extremely delighted to fill in my shoes)?
Apart from technology expertise, CIOs by virtue of providing technology enabled systems and processes across the enterprise have unparalleled visibility in terms of what happens across each function. They are expected to “know” the business, as well as understand the domain specific challenges and opportunities. Such a knowledge level is essential to provide new technology solutions, whether it’s marketing, sales, warehousing, finance or any other. Typically, this gets referred to as the wonderful world of “IT-business alignment”. Such opportunities give them an advantage over others from the CXO domain who may not have this opportunity (or the interest). Best of all, other CXOs do not get measured for knowing other functions and their ability to engage, let’s say the head of supply chain, in a discussion on the best put-away process.
This advantage and ability to influence business outcomes opens up possibilities. Maybe, just maybe, the CIO could take on additional responsibilities beyond “mundane” IT. In all possibility, he can bring about the best while improving the present. Analytical abilities come to the forefront at this point, whereupon the CIO typically challenges status quo, seeking a better tomorrow. So the question of whether a CIO is ready to take on the role of another CXO or a COO becomes irrelevant. If we push the envelope a bit further, he even has a remote chance of being a CEO. So pressure starts to build upon the CIO to get on with it.
So what’s wrong in being a good CIO? Why can’t the CIO remain in the current role and evolve it into a meaningful contributor to the organization (a difficult task to consistently execute)? At this point, the Board may benevolently grant a seat in the Boardroom’s hallowed chambers with other CXOs, executive and non-executive directors. The CIO then reaches the pinnacle of success within his role’s dimensions. Sustaining this peak position obviously requires as much effort as it took to get there. It’s at this juncture that the CIO can be deemed ready to challenge any CXO and succeed in the new role. Of course, this requires the ecosystem to at least be neutral (if not positive) towards the CIO. A negative or a non-conducive environment will be a challenge for any CXO, including the CIO. (See Are Boards ready for the CIO?)
Time to get back to the question “Are you happy being a CIO?” If you are, great! Build upon your success, challenge the organization, and keep on asking the question, “What do I need to do to get to the Boardroom?” If you aren’t, you are probably a CIO by accident or unable to find the magic formula for success (the magic formula is for another day). If you face a personal crisis on your role as a CIO, you should find yourself a mentor or coach who can help. Otherwise, go and find the right job for yourself !
Monday, February 01, 2010
CIO Publications have yet to evolve !
A decade back, the IT leader — now referred to as the CIO — focused a lot on applications, infrastructure, new technology innovations, and business process improvements. In a few cases, the CIO also participated in discussions that were indeed strategic in nature. Contributions to ideas and products were happening even then, as they are the norm today. Ten years back, emails were not as many as they are today, pure-play content sites were few, and not too many sent daily updates. The focus was typically on the nuts and bolts that make up IT infrastructure, the wrapping around it, the database, middleware, presentation layers, and packaged applications which were replacing legacy custom coded programs.
The CIO’s role started transforming in the early part of this millennium. This was driven with the expectation that if a CIO has to retain his right at the table, he has to become more business savvy and leave technology to partners and outsourced teams, as these skills became commodity. IT teams reorganized themselves around business functions and avidly pursued learning of, and about the business and processes. The focus was on how IT teams could contribute towards achievement of common corporate goals and objectives. Vendors and consultants changed their pitch to the CIOs talking about business issues, measuring the efficacy of the CIO’s business knowledge, and how they applied this towards solving real business problems.
Thus CIOs started to attend executive development programs, speak about business technology, scavenge management books, and debate with management thinkers. It was suddenly about how to challenge CEOs and other CXOs on how they can contribute to the business. A few expanded their roles into other parts of the business.
All along, CIOs continued to stay in touch with their roots through various newsletters, magazines and online publications. These media channels continued to feed them with latest happenings in technology, vendor landscape and case studies of how someone leveraged technology investments (in a few cases). IT-business alignment was one of the much debated subjects.
But guess what? Media continued to push technology content down the throats of CIOs who were not really interested in that stuff anymore. Yes, awareness of trends, innovation, new gizmos, and collaboration technologies was important, but not to the level of detail that is being published. That is stuff for IT managers, the doers, and the technical teams (outsourced in many cases).
And that confused the CIOs on whether they should retain the level of in depth technology expertise which is being thrown their way. Most weaned themselves off such content, to make the move towards domain, industry and softer issues that a CXO has to manage every day. Content for such learning is rarely available from even marquee publishers — offline or online.
Such disconnect between expectations drives home the point that the evolution of information givers to the CIO is still incomplete. Media has lagged behind the role that they themselves have created for the CIO by egging them away from the technology stuff towards what matters. We are thankful for that, and hope that CIOs will no longer be subject to tips on how to configure a listener for a DB or resolve malformed IP packets or even look at performance management tools for networks!
By attempting to address a range of audience which spans mid-level managers to executive directors and senior vice presidents, the upper segment is being alienated. And if the CIO is indeed the focus, then a major transformational change is required.
The solution to this for the CIO is to diversify their reading habits and include a large portion of business publications to make up for what their daily bread and butter is lacking in.