The title for this post is a bit of a mouthful but many companies will feel the need to take control of a spiralling, siloed technology landscape.
Gaining control of your IT architecture begins with the definition of enterprise wide architecture principles and standards. Developing and enforcing these guidelines helps companies maintain the most appropriate and efficient systems, applications and processes, and to minimize unnecessary complexity, duplication, and costs.
Some examples of application architecture principles are:
- Common use applications (global single instance, ERP, CRM, financial/ HR shared services)
- Technology independence
- Maximizing the effectiveness of the end user
- Adherence to open standards
- Optimizing and re-allocating IT spend (buy vs. build, virtualization, platform as a service, infrastructure as a service, software as a service)
Without a high degree of collaboration between business and IT leaders, companies probably will not adhere to even the best guidelines. To promote adherence, it is important to show how each architecture principle and standard helps the company to achieve its goals and objectives. Architecture principles and standards are made relevant by connecting them to the strategy of the company. This changes the conversation from “lack of conformance with IT standards” to “lack of support for the company’s strategy” when managers resist complying with architecture principles and standards.



