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.
- Sitting ducks for cybersecurity breaches, small businesses get new options
- GCHQ: change your passwords now even if Uber says it contained the breach
- Christmas rush brings great deals to online shoppers – and new risks for their employers
- Dell, Lenovo, HP will patch hundreds of devices affected by Intel's buggy embedded CPU
- As unencrypted data becomes “negligence”, business leaders are taking encryption strategy away from IT