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.
- Intel says it's been hit with 32 separate lawsuits over Spectre, Meltdown
- Security lessons from the 2018 Pyeongchang Winter Olympics
- From banks to Bitcoin: Trickbot shifts online hustle to cryptocurrencies
- Don't panic about the new 'Prime' Meltdown and Spectre CPU exploits
- Poor patching, user education leave healthcare providers sitting ducks for cyber attacks