Forrester Posits, ‘Will AI Eliminate Enterprise Architects?’ Experts Chime In

Courtesy of Shelly Palmer

By Holt Hackney

Artificial intelligence may automate many of the tasks traditionally performed by enterprise architects, but that does not mean the profession is headed for extinction, according to a new analysis from Forrester.

Instead, AI could push enterprise architects away from producing diagrams, standards and documentation and toward governance, judgment and managing the context that increasingly autonomous systems need to operate.

In a Sept. 18 article, “Will AI Eliminate Enterprise Architects?,” Forrester analysts Charles Betz, JT Thykattil and Joseph Schiavone argue that enterprise architecture is becoming more important as AI agents take on larger roles in software development, IT operations and business processes.

“Enterprise architecture is becoming more important, not less,” the analysts wrote. “But the basis of its importance is changing.”

AI is already capable of generating architecture diagrams, drafting standards, documenting systems, analyzing dependencies and summarizing technology portfolios. Tasks that previously required weeks of manual work can increasingly be completed in hours, although Forrester cautions that the quality of AI-generated work remains uneven.

That shift changes where architects can provide value.

If architectural artifacts become inexpensive and abundant, Forrester argues, enterprise knowledge and judgment become the scarcer resources. Architects may increasingly serve as curators of enterprise context, stewards of architectural knowledge and designers of governance mechanisms.

The change becomes particularly important as autonomous AI agents make more decisions. Organizations will need to establish what those systems are authorized to do, what constraints apply and how those constraints are enforced.

Forrester describes this emerging role as a “control plane for bounded autonomy.”

The analysts also envision architects helping organizations create reusable enterprise intelligence layers containing policies, standards, decision records, dependencies, business context and other information that can be consumed by both humans and AI systems.

Architecture itself could consequently become more continuous. Instead of relying primarily on periodic architecture reviews, AI could allow architectural guidance and governance to become embedded directly into technology delivery workflows.

The article accompanies Forrester’s new report, “The AI Enterprise Architect,” which examines which architecture responsibilities are likely to be automated and which could become more important.

The larger argument is that AI may threaten some of the work enterprise architects perform without eliminating the need for architecture itself. If Forrester is correct, the defining question for the profession may shift from who produces architectural artifacts to who establishes the knowledge, authority and guardrails that increasingly autonomous systems use to make decisions.

We reached out to a handful of experts – Dr. Alok MehtaMaster Scientist Leonard Greski, Dr. Magesh Kasthuri, Dr. Tushar Hazra, Daniel Lambert, M. Sc. – to get their opinions to two questions:

Question: Which parts of an enterprise architect’s job are most vulnerable to AI?

Mehta: I agree that AI will automate much of the artifact-producing work of enterprise architecture, including documentation, diagrams, inventories, technology research, initial solution options and standards. This is positive because those activities are not where experienced architects provide their greatest value. An architect’s real value lies in judgment: understanding the business, challenging unnecessary complexity, anticipating downstream consequences and balancing security, data, integration, resiliency, cost and operational risk. AI can accelerate those decisions, but it does not replace the experience and organizational context required to make them responsibly.

Greski: The fact that AI can automate the artifact-producing work of enterprise architecture is a symptom, not the root problem.  The existential threat to Enterprise Architecture is a lack of measurable results, not AI. I specifically addressed the absence of results problem in my 2022 A&G Magazine article, Getting Beyond Ourselves.  The profession has made little progress on results oriented architecture since the article’s publication.

Kasthuri: Based on my experience, some activities like review, design optimization, design strategy, cost implications, identifying risks and mitigation plans, design traceability, architectural decisions can be automated through AI but the success lies in how much can you believe the outcome of AI generated information for the above tasks. It means that you can use AI but can you believe AI for these tasks. There should be thorough audit and verification process to enable these automated agents and it cannot happen without HITL.

Hazra: There is a lot of truth in this argument. I know architecture documentation leads to a slew of activities that an enterprise architect performs. So verifying and validating AI-prepared documentation is essential. I have faced many barriers to applying due diligence, often to the point that it hinders an initiative’s progress. I argue that it ultimately pays off. Validated documentation allows enterprise architects to align business needs with technical solution options, select appropriatI assert that enterprise architects add value through standards and compliance reviews, architectural traceability and impact analysis, market outlook and vendor research, and presenting final assessments and reports.e technology, tools, and techniques, and, most importantly, maintain a regular cadence of governance for business and technology alignment and enablement.

Lambert: I agree with Forrester’s central argument. AI is unlikely to eliminate enterprise architecture, but it will substantially change where enterprise architects create value. The activities most vulnerable are those involving repetitive analysis, documentation, repository maintenance, diagramming, standards generation, dependency analysis, and portfolio assessment. Forrester notes that work that historically took weeks can increasingly be performed in hours. The architect’s role shifts toward enterprise context, judgment, governance, decision rights, accountability, and managing trade-offs.

daniel1

This aligns closely with Forrester’s argument that architecture artifacts were never the ultimate objective; they demonstrated an architect’s understanding of the enterprise. As AI makes artifact production inexpensive and fast, that enterprise understanding becomes the scarce asset. This transition is explored in this article, “Building AI-Enabled Enterprise Architecture Workflows,” which examines how AI can transform traditional EA activities into intelligent, automated workflows that accelerate analysis, generate and maintain architecture artifacts, and enable architects to focus more on strategic insight, governance, and decision-making.

A second, potentially more disruptive change concerns the EA tooling model itself. If AI can generate models, maintain enterprise knowledge, analyze portfolios, identify dependencies, and answer architecture questions dynamically, organizations may reconsider whether every EA capability requires a traditional SaaS repository. This parallels the broader SaaS-exit argument: organizations should reconsider subscriptions when their economics or rigidity no longer make sense, potentially replacing selected SaaS functionality with purpose-built software they control.

daniel 2

The second model is particularly relevant for smaller organizations that do not currently have an EA tool or a mature EA practice. Implementing a traditional EA SaaS platform such as LeanIX or Ardoq, while also investing in AI agents and workflows, can represent a high combined cost in licensing, implementation, integration, configuration, training, and ongoing administration. For many smaller organizations, that level of investment can be difficult to justify.

AI can now create another path. Organizations can begin building an EA practice around AI-enabled EA workflows without first implementing a dedicated EA SaaS platform. Capabilities, value streams, application portfolios, dependencies, roadmaps, and other architecture information can be generated, analyzed, maintained, and visualized through AI-driven workflows connected to existing enterprise data sources. This makes it possible to establish a practical EA capability at a much more affordable cost, while adding a dedicated EA platform later if scale, governance, or repository requirements eventually justify it.

This does not eliminate the need for authoritative architecture information. In fact, that information becomes even more important in an AI-driven enterprise. What changes is the assumption that it must reside in a conventional EA SaaS repository. It can instead form part of a broader, AI-consumable enterprise knowledge and context layer, governed by enterprise architects and used by AI agents to support architecture analysis and decision-making.

Question 2: If AI agents increasingly make technology and business decisions in real time, does enterprise architecture need to evolve from periodic human review into an always-on governance layer — and, if so, what should enterprise architects be doing today to prepare for that transition?

Greski: What is described by Forrester as an “always-on governance layer” would be implemented as operational telemetry of business capabilities and the systems that support them. Enterprise Architects should learn how to define and implement “minimally invasive” telemetry that ensures not only conformance to non-functional requirements, but also the ability to quantify value generated by business capabilities. Since telemetry is usually implemented by engineering and operations teams because they are the people who are called to solve problems during business operations, Enterprise Architecture departments don’t have sufficient “skin in the game” to own the telemetry. They must earn the right to participate in decision-making by becoming more accountable for the economic value produced by an organization’s business capabilities.

Kasthuri: Yes. We are already doing it for some of our work through AI assisted review process (design, architecture, code, test report) and built customized skills for agents to autonomously do L1 (technical) and L2 (process oriented and risk implications) review procedures. This is an AI-assisted review process and helps to elevate the review process/adherence and quality of delivery.

Mehta: Yes. As AI agents increasingly make technology and business decisions in real time, architecture cannot rely primarily on periodic human review boards. Enterprise architects should begin defining the guardrails, decision rights, reference architectures, security and data policies, observability requirements and escalation mechanisms within which those agents operate. The architect’s role will become more hands-on and closely connected to execution. We are moving from architects who produce architecture to architects who operate architecture. AI will generate many of the artifacts; experienced architects will provide the context, governance and judgment that determine whether what gets built belongs in the enterprise. This perspective is also reflected in my earlier article, “Architects Will Define the Next Generation of IT.

Lambert: Yes. As AI agents increasingly participate in software delivery, operations, business processes, analytics, and eventually business and technology decisions, periodic Architecture Review Boards will be too slow. Enterprise architecture must evolve toward an always-on governance layer that provides trusted context, policies, constraints, decision rights, and automated controls. Enterprise architects should begin building machine-consumable architecture knowledge, explicit decision policies, traceable standards, context graphs, and automated compliance mechanisms while defining where agents can act autonomously and where human approval remains mandatory. This closely reflects Forrester’s concept of architecture becoming the “control plane for bounded autonomy.

Hazra: Enterprise Architects will have to evolve over time. In fact, it is already happening. AI is impacting EA, and eventually EA impactsAI.  As AI increasingly creates diagrams, inventories, mappings, standards analyses, and first-draft roadmaps, the architect’s value will come from directing that intelligence toward coherent, executable business change. In my upcoming article in Architecture and Governance Magazine, I present a framework for Intelligence Architecture. In my humble opinion, EAs will be leading:

  1. Lead a team or an organization with proactive and  proficient discipline in nurturing AI-assisted architecture
  2. Learn to architect AI-enabled enterprises
  3. Cultivate a framework to strengthen business and operating-model expertise
  4. Modernize architecture governance with emerging trends
  5. Increase the authority, influence, and change-leadership capability
  6. Measure realized value continuously