"When the CEO and CIO can find middle ground and work together as true partners, the enterprise will achieve true competitive advantage..."
Within the article, the points that stood out to me were (1) the disconnect between the CEO and CIO, and (2) the CIO as a business commodity. Each deserves further consideration, especially at at time where fewer people want to be a CIO.
The disconnect between the CEO and CIO
The article states, "Clearly, the CIO and CEO have roles with notably contrasting job responsibilities... The CEO often understands the core business and customer demands better than the CIO." I'm not going to disagree with these on principle, and it's easy to see this as the world as is. At the same time, we in IT leadership have been told again and again that we must, MUST understand the business in which we operate in order to be a strategic partner and not a business commodity. Virtually every CIO success story I've read can be summarized as follows:
- CIO meets CxO
- CIO and CxO form partnership around common cause
- CIO and CxO make big initiative happen, increasing visibility for both
One of the reasons I was attracted to my current position is the shared idea that the CIO and CEO in fact have roles with notably comparable job responsibilities. Yes, we do different things for the organization (and I'm still figuring out mine). But we share the broad responsibility of both taking the "across the organization" strategic view and enabling ongoing operations. This dual responsibility distinguishes the CIO from a director of IT, who focuses more on operational excellence and continuous improvement within the technology function.
CEOs and CIOs both have the responsibility and opportunity to span the organization. |
CIO as a business commodity
So what about the CIO being a business commodity? This is certainly one way to be perceived, especially if the CIO presents as tactical rather than strategic. It's tempting to create an IT strategy, but that helps separate technology from the business. IT strategy also tends to focus on things IT thinks is important, which rarely match what the CEO is trying to do and gives the impression IT isn't part of the team.
Instead, the CIO's goal should be to ensure technology is part of each facet of the corporate strategy. Ideally, meeting this goal involves the CIO having candid, business-focused conversations with the CEO and being at the strategic table, and doesn't involve the intricacies of platform as a service or network segmentation. However, the world is far from ideal, and the CIO may have to work hard and long to get to that point, possibly exerting influence less directly to get to the table.
This all sounds great in theory.
Doesn't it? That doesn't mean it's an impossibility in practice. Where a CIO begins has everything to do with context -- not every CEO is ready to integrate technology into their everyday thinking. But they don't have to, at least not in detail. If the CEO is willing to consider technology in terms of the same goals as everything else -- help the top line, help the bottom line, and mitigate risks -- then perhaps the conversation can get underway.
No comments:
Post a Comment