- Management has been unable to design an infrastructure environment and landscape that supports business results and value.
- Infrastructure is viewed as an undesirable cost, leading to underinvestment.
- The infrastructure team has been in a firefighting mode and expected to streamline operations at the same time.
Our Advice
Critical Insight
- Infrastructure teams who fail to see and meet business needs will be fired. There is increasing pressure for the infrastructure team to demonstrate its direct contribution to business outcomes. In a digitally enabled world, failing technology infrastructure can have greater impact than ever.
- Infrastructure functions not only as provider of core technical services, but also as broker to balance demand and capacity. All infrastructure design starts with translating business demands rather than technical requirements.
Impact and Result
- Translate stakeholder objectives into infrastructure requirements. Incorporate infrastructure architecture quality attributes while evaluating the current state and future state of the infrastructure landscape to align with business goals.
- Evaluate your infrastructure architecture from core services (i.e. email, internet, telephony) to obtain an end-user perspective for the range of issues, risks, and opportunities to address.
- Select the right architecture solutions to help achieve business goals. Examine potential solutions with respect to established EA principles and constraints before implementation.
- Review and recalibrate your infrastructure architecture so that it accurately reflects and supports stakeholder needs and technical environments. Actively involve and consult both stakeholders and technical teams throughout the architecture design process.
Select an EA Tool Based on Business and User Need