After 20+ Years in Enterprise Architecture, I Keep Having the Exact Same Conversations
I have two recent encounters/cases where I see that enterprise architecture as a discipline is either non-existent or not properly established. Let me lay out the context and issues and hopefully we can make some progress.
- Senior care corporation
The client is a senior care corporation operating more than 50 facilities, with medical staffing, logistics, operations, and all the complexity that comes with that business. The company grew from a handful of facilities to a multi-country operation. IT support grew organically and was never really planned. Management traditionally treated IT as "the guys who fix jammed printers."
Now that they have billing, accounting, payroll, training, HR systems, intranet, customer support, internal support systems, digital channels for patients and staff, integrated diagnostics, and healthcare management systems, managing and planning the application landscape is proving to be a serious challenge.
As an architecture consulting company, we proposed performing an analysis to capture the current systems landscape, map business capabilities and actual requirements, and create a gap analysis and roadmap to identify what systems are overpaid for, what capabilities are missing, and where investments should be made. Management largely perceives this approach as unnecessary overhead or lacks confidence that it would deliver tangible value.
What is particularly striking is that there is effectively no architecture governance in place. Decisions are made tactically, locally, and reactively. The organization has reached a level of complexity where organic growth and tribal knowledge are no longer sufficient, yet there is little recognition that architecture itself is a business capability that needs to be established and managed.
- Global merchant acquirer
An established global merchant acquirer (card acceptance terminals, e-commerce, payment gateways, etc.) is undertaking several core systems migrations and replacements. Since these systems support core business capabilities, the impact and blast radius are enormous.
The interesting contrast here is that enterprise architecture teams do exist at the global corporate level. However, they largely function as governance document authors rather than active participants in delivery and transformation. They define standards, principles, and target states, but have little involvement in the trenches where critical architectural decisions are actually being made.
Problem-solving is handled by various layers of mid and senior management, multiple vendors, and delivery teams, but there is no effective architecture function coordinating target state, transition architectures, capability ownership, integration strategy, dependency management, or enterprise-wide risk assessment.
What strikes me in both cases is that the organizations are already paying the price of not having effective enterprise architecture, yet they still perceive investing in architecture as an additional cost rather than a mechanism to reduce risk, complexity, operational cost, and time-to-market.
I've been in so many of these situations throughout my career that I'm honestly baffled by how often I find myself participating in the exact same conversations. Different companies, different industries, different people—but somehow the conversations are almost identical, sometimes literally word for word.
My observation is that there is also a structural incentive problem:
- C-level management often does not fully comprehend the long-term implications of architectural decisions, technical debt accumulation, organizational complexity, and transformation risk.
- Mid-management is typically incentivized to deliver short-term outcomes and quick wins. Whether today's decisions create significant operational, financial, or technical problems five years from now is often somebody else's problem.
- Enterprise architects, when they exist, frequently end up either too far removed from execution to influence outcomes or too focused on governance artifacts to drive meaningful change.
It sometimes makes me wonder whether enterprise architecture has a value problem, or whether it simply has a marketing and communication problem.
At this point, I'm honestly more astounded, perplexed, and exhausted than curious. I've participated in these conversations so many times over the years that I'm genuinely baffled by how we keep ending up in exactly the same place, having exactly the same discussions, sometimes almost word for word.
I hear there is progress in enterprise architecture, but I just don't see it.