CIOs have been taking some bashing recently, including a recent post by Joe McKendrick sighting a recent Software AG report:
"CIOs seem to be missing in action when it comes to getting involved in SOA. Only 18% of companies participating in a new survey, sponsored by Software AG, report their CIO's office plays a role in their SOA steering committee. This 'may suggest that SOA isn't viewed as strategically within IT as many have been led to believe.'
Plus, this lack of CIO involvement 'suggests that achieving SOA's goal of improving IT's alignment with the business may be difficult as the individual most responsible for this activity, the CIO, is not actively involved with their enterprise's SOA initiatives.'"
As I covered before in my post "Should you fire your CIO?" many CIOs are really hindering SOA progress, and a new CIO with a more progressive agenda can make all of the difference. The issue is, typically, CIOs may view SOA as a "technical thing" and "tactical," and thus don't attend those meetings. In many cases I view this as the fault of the project leaders who, as we covered before, have a tendency to view SOA as a technical, not an architectural, problem.
However, this really shines a bright light on the issues around SOA, and perhaps architecture in general, pertaining to these issues not being high on the priority list within some organizations. However, solving tactical problems sure is, and they continue to layer on the applications and hardware without a lot of forethought as to how these applications work and play well together within the context of architecture.
Hopefully the CEO is taking notice, and will redirect efforts for more strategic purposes.