The relationship between the CIO and the architects that work for them often lacks a clear line of communication, which can result in a major gap between what the CIO really wants in a well-architected environment and what the architecture team ultimately delivers. Why? Although the CIO might have a high-level understanding of EA's value to the company, he is less likely to provide a clear problem set for enterprise architects to attack, resulting in too much emphasis on architecture design and too little on solving specific problems. Over time, it is primarily this lack of defined goals that leads EA teams into trouble when budgets get tight. Getting a clear set of CIO aligned EA goals positions EA to become a more valued member of the IT organisation.
Stories by Jeff Scott
As CIOs strive to evolve IT from a Solid Utility or Trusted Supplier to a fully integrated business partner, they need the ability to describe IT functions in business terms. Business-IT alignment will only occur when both parties develop a common understanding of what's important to the business, how this relates to the business model and the supporting technology, and where to prioritize investments for measurable improvements. Business capability maps provide a framework to capture, assess, and communicate these needs. These maps put technology strategies such as SOA and application consolidation in the context of the business process, functions, and capabilities they affect, as well as help enterprise architects design application and information architecture.