{"id":337,"date":"2026-11-16T14:13:56","date_gmt":"2026-11-16T14:13:56","guid":{"rendered":"https:\/\/site.beachbot.dk\/?p=337"},"modified":"2026-11-16T14:13:56","modified_gmt":"2026-11-16T14:13:56","slug":"what-ai-might-change-about-being-an-enterprise-architect","status":"publish","type":"post","link":"https:\/\/site.beachbot.dk\/index.php\/2026\/11\/16\/what-ai-might-change-about-being-an-enterprise-architect\/","title":{"rendered":"What AI Might Change About Being an Enterprise Architect"},"content":{"rendered":"<p>AI is changing how organizations develop software, integrate systems and automate business processes.<\/p>\n<p>For Enterprise Architects, this raises an interesting question: <strong>What will we actually spend our time doing in the coming years?<\/strong><\/p>\n<p>Much of the discussion focuses on AI tools and new technical skills. Those are important, but I think the bigger change may be in how we apply the architectural skills we already have.<\/p>\n<p>Some activities will become easier to automate. Others may become more important as organizations introduce AI agents and create new solutions faster than before.<\/p>\n<p>Here are five areas I believe are worth paying attention to.<\/p>\n<h2>1. AI Agents and Enterprise Systems<\/h2>\n<p>As organizations move from AI assistants that provide information to agents that perform actions, enterprise integration becomes more complicated.<\/p>\n<p>An agent might retrieve information from CRM, update records in ERP or execute a workflow across several applications.<\/p>\n<p>But how should it authenticate? What permissions should it have? What happens when an API fails halfway through a process? And who is accountable if the agent makes a mistake?<\/p>\n<p>These are familiar architectural questions, but AI introduces a different level of autonomy.<\/p>\n<p>I think Enterprise Architects will need to understand how agents interact with enterprise systems, including permissions, failure handling, traceability and accountability.<\/p>\n<p>The challenge is not simply to connect agents to applications. It is to ensure they can operate safely within the enterprise.<\/p>\n<h2>2. Becoming Custodians of Trusted Enterprise Context<\/h2>\n<p>An AI agent may have access to several enterprise systems without understanding how their information relates.<\/p>\n<p>A customer in CRM may not represent the same business entity as an account in ERP. An archived policy may still be searchable even though it is no longer valid. An architecture repository may describe an integration that was retired months ago.<\/p>\n<p>These are familiar problems in Enterprise Architecture. AI makes their consequences more visible.<\/p>\n<p>If agents are expected to reason and act using enterprise information, someone needs to establish which information can be trusted and how it relates to the rest of the enterprise.<\/p>\n<p>I see an opportunity for Enterprise Architects to become <strong>custodians of trusted enterprise context<\/strong>.<\/p>\n<p>Not by taking ownership of all enterprise data, but by helping establish authoritative sources, business meaning, relationships and ownership across systems.<\/p>\n<p>There is also a practical challenge. Before building an AI architecture assistant, someone needs to negotiate access to repositories, identify application owners and discover how much of the documentation is actually reliable.<\/p>\n<p>I suspect many architecture teams will spend more time resolving these issues than experimenting with language models.<\/p>\n<h2>3. From Maintaining Repositories to Understanding the Enterprise<\/h2>\n<p>EA repositories often depend on manual updates. Application information becomes outdated, dependencies are documented inconsistently and architecture decisions remain scattered across projects.<\/p>\n<p>AI offers an opportunity to improve discovery and analysis using architecture repositories, cloud platforms, APIs and operational information.<\/p>\n<p>An architecture assistant could identify dependencies, summarize decisions and help assess the impact of proposed changes.<\/p>\n<p>But traceability to reliable sources is essential.<\/p>\n<p>If two repositories disagree about an integration, the assistant should expose the uncertainty rather than produce a confident answer.<\/p>\n<p>And operational information does not always tell the whole story. An integration that is not currently active may still be part of the intended architecture.<\/p>\n<p>I think our work could gradually shift from collecting and documenting architecture information to validating it, resolving inconsistencies and understanding the consequences of change.<\/p>\n<p>That would be a meaningful improvement over spending time manually keeping diagrams and inventories up to date.<\/p>\n<h2>4. Business Architecture and Strategic Decisions<\/h2>\n<p>This area is less about learning new technology and more about applying existing architectural judgment in a changing environment.<\/p>\n<p>AI may make it cheaper to develop software, integrate applications or automate business workflows.<\/p>\n<p>I think this will challenge traditional build-versus-buy decisions.<\/p>\n<p>An organization might find it easier to create a custom AI-enabled workflow than purchase another application. But that solution still introduces maintenance responsibilities, security concerns and dependencies on external AI services.<\/p>\n<p>We need to understand those trade-offs alongside business capabilities, operating models and investment priorities.<\/p>\n<p>And perhaps we need to become involved earlier, before a solution has already been chosen.<\/p>\n<p>The important question is not only whether something can be built, but whether it makes sense for the enterprise to own and operate it.<\/p>\n<p><strong>Just because we can build it doesn&#8217;t mean we should.<\/strong><\/p>\n<h2>5. Spending Less Time Producing Architecture Artifacts<\/h2>\n<p>Some traditional EA activities will probably become less valuable when performed manually.<\/p>\n<p>Diagram production, repetitive documentation, application inventory collection and routine compliance checks are increasingly suitable for automation.<\/p>\n<p>The underlying architectural capabilities remain important. What changes is how much time we should spend performing these activities ourselves.<\/p>\n<p>I would rather use the recovered time to investigate dependencies, challenge solution assumptions and work with business stakeholders on difficult decisions.<\/p>\n<p>For example, instead of spending days producing an application landscape diagram, we could spend more time understanding which dependencies actually matter when retiring an application.<\/p>\n<p>Or instead of checking whether a proposed solution complies with every standard, we could spend more time questioning whether the organization needs another solution in the first place.<\/p>\n<p>That also raises a question about how we measure the value of Enterprise Architecture.<\/p>\n<p>Is it the number of diagrams we produce and reviews we complete? Or is it the quality of the decisions we help the organization make?<\/p>\n<p>I think the second will become increasingly important.<\/p>\n<h2>Final Thoughts<\/h2>\n<p>I don&#8217;t think Enterprise Architects need to become AI engineers to remain relevant.<\/p>\n<p>But we do need to understand how AI changes enterprise systems, information, investments and the way architecture work gets done.<\/p>\n<p>Some of our traditional activities will become easier to automate. At the same time, the need to understand dependencies, challenge assumptions, manage complexity and guide strategic decisions is unlikely to disappear.<\/p>\n<p>If anything, AI may make those capabilities more important.<\/p>\n<p>For me, the interesting opportunity is not to use AI to produce more architecture documentation faster.<\/p>\n<p>It is to spend less time documenting the enterprise and more time helping the organization make better decisions about its future.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>AI is changing how organizations develop software, integrate systems and automate business processes. For Enterprise Architects, this raises an interesting question: What will we actually spend [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":344,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_import_markdown_pro_load_document_selector":0,"_import_markdown_pro_submit_text_textarea":"","footnotes":""},"categories":[131],"tags":[],"class_list":["post-337","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-ai"],"blog_post_layout_featured_media_urls":{"thumbnail":["https:\/\/site.beachbot.dk\/wp-content\/uploads\/2026\/11\/AI-kontor-med-strategiske-beslutninger-150x150.png",150,150,true],"full":["https:\/\/site.beachbot.dk\/wp-content\/uploads\/2026\/11\/AI-kontor-med-strategiske-beslutninger.png",1672,941,false]},"categories_names":{"131":{"name":"AI","link":"https:\/\/site.beachbot.dk\/index.php\/category\/ai\/"}},"tags_names":[],"comments_number":"0","wpmagazine_modules_lite_featured_media_urls":{"thumbnail":["https:\/\/site.beachbot.dk\/wp-content\/uploads\/2026\/11\/AI-kontor-med-strategiske-beslutninger-150x150.png",150,150,true],"cvmm-medium":["https:\/\/site.beachbot.dk\/wp-content\/uploads\/2026\/11\/AI-kontor-med-strategiske-beslutninger-300x300.png",300,300,true],"cvmm-medium-plus":["https:\/\/site.beachbot.dk\/wp-content\/uploads\/2026\/11\/AI-kontor-med-strategiske-beslutninger-305x207.png",305,207,true],"cvmm-portrait":["https:\/\/site.beachbot.dk\/wp-content\/uploads\/2026\/11\/AI-kontor-med-strategiske-beslutninger-400x600.png",400,600,true],"cvmm-medium-square":["https:\/\/site.beachbot.dk\/wp-content\/uploads\/2026\/11\/AI-kontor-med-strategiske-beslutninger-600x600.png",600,600,true],"cvmm-large":["https:\/\/site.beachbot.dk\/wp-content\/uploads\/2026\/11\/AI-kontor-med-strategiske-beslutninger-1024x941.png",1024,941,true],"cvmm-small":["https:\/\/site.beachbot.dk\/wp-content\/uploads\/2026\/11\/AI-kontor-med-strategiske-beslutninger-130x95.png",130,95,true],"full":["https:\/\/site.beachbot.dk\/wp-content\/uploads\/2026\/11\/AI-kontor-med-strategiske-beslutninger.png",1672,941,false]},"_links":{"self":[{"href":"https:\/\/site.beachbot.dk\/index.php\/wp-json\/wp\/v2\/posts\/337","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/site.beachbot.dk\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/site.beachbot.dk\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/site.beachbot.dk\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/site.beachbot.dk\/index.php\/wp-json\/wp\/v2\/comments?post=337"}],"version-history":[{"count":3,"href":"https:\/\/site.beachbot.dk\/index.php\/wp-json\/wp\/v2\/posts\/337\/revisions"}],"predecessor-version":[{"id":343,"href":"https:\/\/site.beachbot.dk\/index.php\/wp-json\/wp\/v2\/posts\/337\/revisions\/343"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/site.beachbot.dk\/index.php\/wp-json\/wp\/v2\/media\/344"}],"wp:attachment":[{"href":"https:\/\/site.beachbot.dk\/index.php\/wp-json\/wp\/v2\/media?parent=337"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/site.beachbot.dk\/index.php\/wp-json\/wp\/v2\/categories?post=337"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/site.beachbot.dk\/index.php\/wp-json\/wp\/v2\/tags?post=337"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}