Skip to main content

IT Governance - CIO Role

I feel IT Governance is the most an important function under the umbrella of the CIO. Since Technology Governance is a overarching organizational issue, the CIO comes in as a strategist with the unique ability to bridge the gap of the many business departments and that require technology and offer perspectives on solving business problems. In practice however there seems to be a lot of confusion in roles and responsiblities of a CIO  in the technology governance realm when compared to the CTO. The CIO is not your IT guy, web guy, or the techie that rescues you from the hole.

The key attributes that will be required by a person in the CIO role would be

Big-picture thinking

Big picture thinking is the ability to see the whole gammut of organizational operations and see, identify the broken processes or the lack of them and the need of integrating technology to improve efficienty of the bottom line of operations and streamline flow of information back to the senior management.

Capturing Market Share

A CIO role in technology governance becomes crucial because he is responsible for connecting the dots of communication between business functions internally and use a heavy dosage of business intelligence and market awareness and bring that data to the table for strategic planning and strategic decision making.
Auditing Risk & Security
Another key area I feel the CIO role in IT Governance is auditing risk and security of the databases, data in general, and the procurment & implementation of the technology strategies. A cost/benefit ratio analysis, ROI and other financial ratios and KPIs are important tools in the arsenal the CIO carries.


But I thought the CIO was the head of the IT department?

The technology department is a operational entity but also a curcial strategic entity these days. Because of its operational nautre and its 60% responsibilities take the nature of executing and supporting daily technical needs of employees, implementing technology, building services etc, it still requires the guidance of the CIO to implement and make sure that these activities aim at increasing efficiency of the organization and satisfying current and future business needs & problems.  In many organizations based upon size there may be multiple operational IT managers and here is where alignment of solutions and operational efficieny and mitigation of risks should go hand in hand.

Why don’t other departments just talk to the operational manager(s) of IT?

Normally the technology department or operational project managers take in problems, build a new service from heads & personnel of functional depts like HR, Finance, Engineering, Warehouse etc and implement solutions in silos, or "one-off" solutions that are temporary fixes, workarounds because of costing issues. But these end up being expensive in the long run because of maintenance burdens, migration bottlenecks, and ultimately wastage of IT Resources. The role of the CIO becomes crucial here because he takes into account alignment of business needs, overarching business goals, future needs, and plans for scalabiltiy. These factors bring in skill sets the CIO offers to be the middle man broker between functional heads and technology. The final objective is seamless integration for seamless delivery of services using technology.

CIO's Involvment

A CIO's involvement thus in Technology Governance becomes less in operational & technology implementation but more involved in business strategy, revenue generation, business-technology process management, and being the completing cog in the entire customer relationship management. My intention here of using CRM term is intended at internal as well external customers and this includes all the partners who are involved in increasing the value chain. CIO's involvment is heavy in terms of strategy, critical data touch-points and information risk management.

My thoughts for the day,

Sam Kurien


Popular posts from this blog

IT as a Innovation Partner in Business

Usually in Business organizations and especially in organizations where R&D is a separate department itself a tension persists on keeping the IT department away from any decision when it comes to innovation or process improvement. In short the IT department is generally seen as less of a help and more of a hindrance to innovation efforts. One of the main reasons is traditionally information systems are designed to impose structure on process, achieve pre-defined goals, produce metrics and minimize need for human interaction (in some case over maximize human interaction leading to nothing but "meetings").

While Innovation activities are highly unstructured and emergent, IT cannot be ignored or kept in isolation because IT can help in visualization tools, data mining efforts, uncover hidden relationships between data and create tools of knowledge management/information repository that so desperately is needed cross functionally but especially by the innovators within a org…

Analysis of SAP’s Platform Strategy

The software industry has been through high and lows up with the constant advent of new technological innovations and rapid changes in the global economic landscapes. SAP is the leading enterprise application software giant started by Hasso Plattner. The rise of Enterprise application industries started in early eighty’s with organizations needing one single software program that was capable of serving the multiple needs and functions of various departments. One single enterprise-wide application software means integrating applications that fused together for the smooth exchange and extraction of information. For example when customer services sold a product and got stock updated in the inventory by the warehouse people and the same data could be pulled by the Finance department. Enterprise Application software’s were designed exactly to do the latter mentioned processes seamlessly. SAP started by break away engineer’s Plattner and group build the company on strong engineering fort…

How Dashboards can mislead

Read an interesting article from John Shapiro professor at Northwestern Kellog on how dashboards can mislead executives and I cannot agree more. To be honest, I love visualization of data and have pushed my data architects and report writers to give me snapshots of various measures but how often the rich data didn't mean anything as it did not align with organizational goals. Even more, what information is important to me is not necessarily relevant to other executives in the organization.  Data analytics visualized on dashboards typically describe existing measures on past phenomena, some better ones predict future events and past data and the best one prescribe a course of corrective or strategic actions.

Shapiro talks about three types of traps executives can fall for:

1. The Context Trap:  We equate empirical data to the objective. I have blatantly used the cliche "numbers don't lie." But this belief can be dangerous because we can track wrong measures or metrics…