The document outlines challenges faced by enterprise architecture (EA), highlighting that application teams perceive interactions with EA as non-essential and prioritize their own design choices over EA governance. EA lacks visibility and control in application architecture decisions, leading to low prioritization of compliance requests and insufficient budget for EA programs. Additionally, the career progression for technologists within EA is not clearly defined, further complicating the effectiveness of EA initiatives.

1. IDEAS TO REVITALIZE EA

2. WHAT IS THE PROBLEM?
• App teams consider interactions with EA mostly as non-essential
• E.g. Without TRT/ARB, teams go ahead with their design, choice of technologies
• They consider TRT as mere formality
• App Meta-data and Portfolio requests are mostly served on low priority by app teams
• EA Governance & Architecture/Design Standards Compliance requests are considered non-essential and low-priority
by app teams unless camouflaged with ACLC, External Audit, etc.
• Most of the times, EA doesn’t get it’s due credit with CIO – no sufficient budget for EA programs (EA
Tool, Trainings, Subscriptions, etc.)
• No direct control or formal touchpoints with key branches of EA viz. Data Architecture, Security
Architecture, Infrastructure Architecture

3. WHAT IS THE PROBLEM?
• EA has no control while app teams define solution & application architecture –
even for complex programs
• EA has no visibility into various reusable assets developed by app teams
• EA has no visibility with key technologists and potential architects embedded
into app teams
• Overall career progression path for technologists is not well defined