<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Ole Olesen-Bagneux on Medium]]></title>
        <description><![CDATA[Stories by Ole Olesen-Bagneux on Medium]]></description>
        <link>https://medium.com/@olesenbagneux?source=rss-cbcef8118550------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*YWMrI7J0T6jO2bXhAVcAwQ.png</url>
            <title>Stories by Ole Olesen-Bagneux on Medium</title>
            <link>https://medium.com/@olesenbagneux?source=rss-cbcef8118550------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 20:35:32 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@olesenbagneux/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[A new stack for a new era]]></title>
            <link>https://medium.com/analysts-corner/a-new-stack-for-a-new-era-ce4d578da020?source=rss-cbcef8118550------2</link>
            <guid isPermaLink="false">https://medium.com/p/ce4d578da020</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[ai-agent]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[data-visualization]]></category>
            <dc:creator><![CDATA[Ole Olesen-Bagneux]]></dc:creator>
            <pubDate>Sun, 21 Dec 2025 04:13:07 GMT</pubDate>
            <atom:updated>2025-12-21T04:13:07.859Z</atom:updated>
            <content:encoded><![CDATA[<h4>Why is the Data &amp; AI Stack replacing the Modern Data Stack?</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cPKQgGEuBK2eRNQRNvp5Rg.png" /><figcaption>We have left the era of the Modern Data Stack for good</figcaption></figure><p>In the past era of the Modern Data Stack a global community of data researchers, practitioners, software vendors, and consultants gathered in a planetary movement to work on the perfection of data engineering for data science.</p><p>The goal was clear: data was the ultimate raw material for innovation, a source of enterprise growth.</p><p>And the ambition of the modern data stack — in its heydays — was the detailed tooling of every single component in data engineering and also (to a lesser extent) data science. No other overview has reached the same level of influence than<a href="https://www.linkedin.com/preload/#"> Matt Turck</a> MAD landscape, updated every year with precise insights in technological evolution and always grouped in the most intuitive categories — the MAD landscape is still highly relevant.</p><p>Then ChatGPT 3.5 was released.</p><p>That effectively put an end to the era of the modern data stack. VC funding changed from data technologies to AI technologies, and the modern data stack was from that point on (it has not stopped yet) experiencing extensive consolidation/rebundling into data intelligence platforms. Data intelligence platforms are used in the context of even bigger even ecosystems that unites user experience, data management and operations carried out through workflows — potentially redefining how software is created altogether.</p><p>We are now witnessing a technological configuration that can be characterized as the Data &amp; AI Stack, where;</p><p>- data providers and data consumers are augmented with AI, eg. the Data Analyst as an AI Data Analyst benefitting from a text to SQL to text architecture.</p><p>- metadata management is augmented with AI, e.g. metadata data curation through automated description and tagging, natural language search and conversational search.</p><p>- the entire purpose of the the data &amp; AI stack is shifting from purely data engineering/science/governance to facilitate generative architectures, and especially agentic architectures, that could potentially rewrite the entire codebase for how companies design execute their value chains, possibly turning Software as a Service upside down to Service as Software, as clusters of code generated at a specific point in time for a specific task at hand.</p><p>The Modern Data Stack era is over.</p><p>This is the era of the Data &amp; AI stack.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ce4d578da020" width="1" height="1" alt=""><hr><p><a href="https://medium.com/analysts-corner/a-new-stack-for-a-new-era-ce4d578da020">A new stack for a new era</a> was originally published in <a href="https://medium.com/analysts-corner">Analyst’s corner</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How can we enable data intelligence?]]></title>
            <link>https://medium.com/analysts-corner/how-can-we-enable-data-intelligence-9a8c3d3867b3?source=rss-cbcef8118550------2</link>
            <guid isPermaLink="false">https://medium.com/p/9a8c3d3867b3</guid>
            <category><![CDATA[metadata]]></category>
            <category><![CDATA[data-management]]></category>
            <category><![CDATA[knowledge-graph]]></category>
            <category><![CDATA[data-intelligence]]></category>
            <category><![CDATA[ontology]]></category>
            <dc:creator><![CDATA[Ole Olesen-Bagneux]]></dc:creator>
            <pubDate>Wed, 26 Nov 2025 09:20:19 GMT</pubDate>
            <atom:updated>2025-11-26T09:20:19.544Z</atom:updated>
            <content:encoded><![CDATA[<h4>Two competing interpretations of data intelligence are emerging.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JGjk_nutpEKsJAiZGea6Yg.png" /><figcaption>What is data intelligence?</figcaption></figure><p>Recently, some technology vendors have begun promoting their data platforms as intelligence platforms. Needless to say, such platform have — at least have the intention — to be an ontology at the metadata layer. And as such this is further testimony of the ambition for technology companies to provide an intelligence layer above data.</p><p>A data platform, intended for data engineering, consists of all the functionality that data engineers perform, when storing, transforming, and transporting data. And it is a logical step, to want to provide a metadata layer on top.</p><p>However.</p><p>Is that data intelligence?</p><p>Data Intelligence really means something else. Sure, you can depict your data platform at a metadata layer, but does that give you an overview of your data? No, not really. It gives you an overview of the data in your data platform. Does it give an ontology? Yes, if you build it correctly… But it will be a very siloed ontology — it will represent only one data platform.</p><p>Data intelligence is about making as much of your enterprise data discoverable, governable, usable. That takes looking further than _one_ platform. However well functioning that platform is.</p><p>This ambition is important in the present, and it is only getting more important in the future. Digital sovereignty is on the rise, and data intelligence has to be independent of any given data platform intended for engineering. Enterprises are moving towards technological, legal, and economic freedom from technology providers. And they should!</p><p>There is no right or wrong in data architecture, only choices with consequences. But you have to ask yourself:</p><p>What enables true data intelligence? <br>What should your ontology represent? <br>Where is the data you want to govern?<br>Should abstract metadata force you to use specific data technologies?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9a8c3d3867b3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/analysts-corner/how-can-we-enable-data-intelligence-9a8c3d3867b3">How can we enable data intelligence?</a> was originally published in <a href="https://medium.com/analysts-corner">Analyst’s corner</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How do we, as humans, reclaim our right to intention, to initiative, when it comes to AI?]]></title>
            <link>https://olesenbagneux.medium.com/how-do-we-as-humans-reclaim-our-right-to-intention-to-initiative-when-it-comes-to-ai-130305221e6f?source=rss-cbcef8118550------2</link>
            <guid isPermaLink="false">https://medium.com/p/130305221e6f</guid>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Ole Olesen-Bagneux]]></dc:creator>
            <pubDate>Mon, 24 Nov 2025 11:35:44 GMT</pubDate>
            <atom:updated>2025-11-24T11:35:44.119Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tDbLaTZVwSK0hYLfk6xELw.png" /></figure><p>How do we, as humans, reclaim our right to intention, to initiative, when it comes to AI? AI is sometimes seen as a threat, as something that will disrupt, and that is correct, but what happens when we turn the power of the relation between humans and AI around? What do we want to do with AI? What is our intention — what can we imagine it to be? How can we enable that, what initiatives can we take? In sum, how do we <em>humanize</em> our AI strategy?</p><p>Join me on this Data, Explored webinar for a talk with author, Data &amp; AI strategy Director <a href="https://medium.com/u/7ee28a17c721">Tiankai Feng</a> from ThoughtWorks to listen in and be part of the conversation, here:</p><p><a href="https://www.actian.com/webinars/data-explored-episode-4-humans-before-ai/">https://www.actian.com/webinars/data-explored-episode-4-humans-before-ai/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=130305221e6f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is the typical mistake when using AI for semantics?]]></title>
            <link>https://medium.com/analysts-corner/what-is-the-typical-mistake-when-using-ai-for-semantics-624ba108c589?source=rss-cbcef8118550------2</link>
            <guid isPermaLink="false">https://medium.com/p/624ba108c589</guid>
            <category><![CDATA[language]]></category>
            <category><![CDATA[agentic-ai]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[data-catalog]]></category>
            <category><![CDATA[large-language-models]]></category>
            <dc:creator><![CDATA[Ole Olesen-Bagneux]]></dc:creator>
            <pubDate>Thu, 13 Nov 2025 05:38:23 GMT</pubDate>
            <atom:updated>2025-11-13T05:38:23.553Z</atom:updated>
            <content:encoded><![CDATA[<h4>Using a business glossary in a data catalog as example</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Jn7slVpkHn9PtFaTc5gc3Q.png" /></figure><p>Because AI can answer us in language, some can be led to believe that AI can give us language. It cannot, and if we try using AI in this way, the consequence is that AI doesn’t work at all. It comes down to this: Unique actions versus repetitions.</p><p>Here’s an example:</p><p>Some technology vendors will try to convince us that AI can generate a complete business glossary for data catalogs, simply by extracting it from tabular metadata. The illusion will be a seductive display of words intended to capture the essence of an enterprise, following the laws of semantics perfectly, creating a thesaurus structure of broader terms, preferred terms, variant terms, related terms, narrower terms and perhaps excluded and opposing terms.</p><p>In reality, this is a catastrophic approach to using AI for semantics.</p><p>Creating a business glossary is a unique action. It’s human interpretation at its very best, and it must be protected and valued. Humans need to create business glossaries for them to work in data catalogs.</p><p>What is the end result if AI creates business glossaries? A horrible process of manually or even automatically tagging datasets with imprecise terms, pestering search and making discoverability of the data that truly matters impossible. In short: A failure.</p><p>What is the end result if humans create business glossaries? A functional setup for actually using AI. Once precise, well crafted terms have been created by humans, the boring, repetitive job of tagging datasets and data products can be automated with AI. You can have an agent doing it at scale, and review its work. The more precise a business glossary you have given them, the better they will perform. And then your data catalog implementation takes off.</p><p>That’s how AI should be used for semantics: Value the unique actions and automate the repetitions.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=624ba108c589" width="1" height="1" alt=""><hr><p><a href="https://medium.com/analysts-corner/what-is-the-typical-mistake-when-using-ai-for-semantics-624ba108c589">What is the typical mistake when using AI for semantics?</a> was originally published in <a href="https://medium.com/analysts-corner">Analyst’s corner</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What’s wrong with the DAMA wheel?]]></title>
            <link>https://medium.com/analysts-corner/whats-wrong-with-the-dama-wheel-b080ccb327ac?source=rss-cbcef8118550------2</link>
            <guid isPermaLink="false">https://medium.com/p/b080ccb327ac</guid>
            <category><![CDATA[data-governance]]></category>
            <category><![CDATA[data-engineering]]></category>
            <category><![CDATA[business-process]]></category>
            <category><![CDATA[data-management]]></category>
            <category><![CDATA[data]]></category>
            <dc:creator><![CDATA[Ole Olesen-Bagneux]]></dc:creator>
            <pubDate>Wed, 05 Nov 2025 09:05:21 GMT</pubDate>
            <atom:updated>2025-11-07T11:22:46.237Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iqqp-QtxQ0isxC9JfPnTxA.png" /></figure><p>For years, the DAMA wheel has been a popular reference for data management practitioners all over the world. But the wheel has also been instrumental in thinking of data management in a way that is wrong.</p><p>What the DAMA wheel does really well is to structure the content of the Data Management Book of Knowledge — the DAMA DMBOK. It’s the various chapters of the book, distilled in a simple, easy to understand diagram in slices, with a center that ties it all together: Data governance. As such, the DAMA wheel effectively communicates all the elements of data management.</p><p>What the DAMA wheel does really poorly, unfortunately, is to depict how data management is actually performed — as a process. Data management is not performed by ‘spinning the wheel’ and checking all the boxes along the way.</p><p>Perception is reality. The DAMA wheel played a regrettable role in making generations of data managers believe data management was performed by simply knowing the elements in the wheel. But that is not how data management is performed — it’s simply the elements of data management set up in a logical display. Elements you need to know, if you are in data management. But data management as a process — a business process — can not be depicted like this. It should be depicted in a distinct process notation, e.g. Business Process Mapping Notation (BPMN).</p><p>The DAMA wheel should be kept. But it continues to play a bittersweet double role — as a successful key to understanding data management and as a confusing blocker of how to perform it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b080ccb327ac" width="1" height="1" alt=""><hr><p><a href="https://medium.com/analysts-corner/whats-wrong-with-the-dama-wheel-b080ccb327ac">What’s wrong with the DAMA wheel?</a> was originally published in <a href="https://medium.com/analysts-corner">Analyst’s corner</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[OK OK — I’m Staying on Medium]]></title>
            <link>https://olesenbagneux.medium.com/ok-ok-im-staying-on-medium-26e6751276e3?source=rss-cbcef8118550------2</link>
            <guid isPermaLink="false">https://medium.com/p/26e6751276e3</guid>
            <dc:creator><![CDATA[Ole Olesen-Bagneux]]></dc:creator>
            <pubDate>Tue, 04 Nov 2025 12:41:05 GMT</pubDate>
            <atom:updated>2025-11-04T12:41:05.704Z</atom:updated>
            <content:encoded><![CDATA[<h3>OK OK — I’m Staying on Medium</h3><p>Since I said I would be leaving, people started following me. This was <em>not</em> my intention with saying I wanted to leave. But, apparently this platform is still somewhat alive.</p><p>All in all... I’m staying on Medium.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=26e6751276e3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I’m leaving Medium soon]]></title>
            <link>https://olesenbagneux.medium.com/im-leaving-medium-soon-8537b26bbf0c?source=rss-cbcef8118550------2</link>
            <guid isPermaLink="false">https://medium.com/p/8537b26bbf0c</guid>
            <dc:creator><![CDATA[Ole Olesen-Bagneux]]></dc:creator>
            <pubDate>Wed, 22 Oct 2025 16:15:32 GMT</pubDate>
            <atom:updated>2025-10-22T16:15:32.820Z</atom:updated>
            <content:encoded><![CDATA[<p>Find me here:</p><p><a href="https://www.linkedin.com/in/ole-olesen-bagneux">https://www.linkedin.com/in/ole-olesen-bagneux</a></p><p>And here:</p><p><a href="https://substack.com/@oleolesenbagneux">Ole Olesen-Bagneux | Substack</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8537b26bbf0c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Is medium still alive?]]></title>
            <link>https://olesenbagneux.medium.com/is-medium-still-alive-24441ecdd50e?source=rss-cbcef8118550------2</link>
            <guid isPermaLink="false">https://medium.com/p/24441ecdd50e</guid>
            <dc:creator><![CDATA[Ole Olesen-Bagneux]]></dc:creator>
            <pubDate>Tue, 23 Sep 2025 14:24:13 GMT</pubDate>
            <atom:updated>2025-09-23T14:24:13.710Z</atom:updated>
            <content:encoded><![CDATA[<img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=24441ecdd50e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Fundamentals of Metadata Management is now Published]]></title>
            <link>https://olesenbagneux.medium.com/fundamentals-of-metadata-management-is-now-published-21b7cd59077b?source=rss-cbcef8118550------2</link>
            <guid isPermaLink="false">https://medium.com/p/21b7cd59077b</guid>
            <category><![CDATA[metadata]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[metadata-management]]></category>
            <category><![CDATA[decentralization]]></category>
            <dc:creator><![CDATA[Ole Olesen-Bagneux]]></dc:creator>
            <pubDate>Mon, 11 Aug 2025 12:45:30 GMT</pubDate>
            <atom:updated>2025-08-11T12:45:30.398Z</atom:updated>
            <content:encoded><![CDATA[<h4>Joe Reis has written the foreword</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Fp5au1LA39k4iF4QVAlgfw.jpeg" /><figcaption>Fundamentals of Metadata Management now available world wide</figcaption></figure><p>It is with great pleasure that I can announce to my readers everywhere that Fundamentals of Metadata Management is available in bookstores worldwide.</p><p>Writing this book was hard and very rewarding. It needed to be written.</p><p>Fundamentals of Metadata Management can be used in companies globally. It reflects the enterprise reality of metadata management, and with this I mean the real reality. It’s a reality that is often neglected for all sort of reasons, and many data leaders and brilliant architects have reached out already confirming the message of my book is spot on. Thank you!</p><p><a href="https://medium.com/u/fbb114418d3e">Joe Reis</a> kindly accepted to write the foreword. Joe, to see you so majestically explain my ideas and sense that you really believe in them too is impressive. It’s stunning to see someone like you — that embodies such an excellent technologist and such an exquisite author, in one and the same person — praising my work. I’m very grateful.</p><p>I did three keynotes about this book while writing it, and I owe so much to the data community because if it: First for people being thrilled about my book announcement in Paris, then boosting my energy in Helsinki and finally celebrating the main idea, the Meta Grid, in Austin.</p><p>Some <a href="https://medium.com/u/fbfa235a954c">O&#39;Reilly Media</a> books get the honor of being sponsored after they are approved by the editorial board — ensuring that they are technology agnostic. I’m proud to announce that my book has recently received a double(!) sponsorship from <a href="https://www.actian.com/lp/fundamentals-of-metadata-management-ebook/">Actian</a> and <a href="https://www.hcl-software.com/fundamentals-for-data-driven">HCLSoftware</a>. Meaning that you can read an online version for free. I’m very proud of this.</p><figure><img alt="two covers of Fundamentals of Metadata Management, one with Compliments of Actian and one with Complimnets of HCLSoftware" src="https://cdn-images-1.medium.com/max/1024/1*I8XwVH7tURsVhM3GCU1ZpA.png" /></figure><p>The concept of Meta Grid has gotten a lot of attention, and I have tried to balance this hype lately a bit, because I want to this idea to stick, also longer than a tech hype cycle. There are many that are good at hyping ideas, but my ideal is Bill Inmon — a person that conceived a concept as massive as the data warehouse and fought for it for decades. Bill is my hero. The Meta Grid is never going away, and I hope my book will help many readers for many years to come.</p><p>I’m grateful for everyone that have followed my process of writing this book, asked questions, provided advice, cheered, and challenged.</p><p>If you read my book, you will learn that the Meta Grid is a secret key to succeed with AI and gain control of your enterprise IT landscape. <br> <br> To everyone I know — do stay in touch.</p><p>tagging some friends here on <a href="https://medium.com/u/504c7870fdb6">Medium</a>: <a href="https://medium.com/u/d42af743e48b">Jean-Georges Perrin</a>, <a href="https://medium.com/u/97abd6c0aad1">Piethein Strengholt</a>, <a href="https://medium.com/u/9eab94e66722">Eric Broda</a>, <a href="https://medium.com/u/8ed06b3d7235">Omar Khawaja</a>, <a href="https://medium.com/u/8d1141841617">Sanjeev Mohan</a>, <a href="https://medium.com/u/10f7a02f604f">Andrew Jones</a>, <a href="https://medium.com/u/cc31500af829">Luis Arteaga</a>, <a href="https://medium.com/u/e713e1f31a">P Platter</a>, <a href="https://medium.com/u/6c74ca64a522">Winfried Adalbert Etzel</a>, <a href="https://medium.com/u/d24b10fee172">Grace G Lau</a>, <a href="https://medium.com/u/66631cffd15f">HCLSoftware</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=21b7cd59077b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is an Enterprise Architecture Management tool?]]></title>
            <link>https://medium.com/analysts-corner/what-is-an-enterprise-architecture-management-tool-857dbc871459?source=rss-cbcef8118550------2</link>
            <guid isPermaLink="false">https://medium.com/p/857dbc871459</guid>
            <category><![CDATA[enterprise-architecture]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[metadata]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[information-technology]]></category>
            <dc:creator><![CDATA[Ole Olesen-Bagneux]]></dc:creator>
            <pubDate>Thu, 05 Dec 2024 03:46:07 GMT</pubDate>
            <atom:updated>2024-12-05T03:46:07.235Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yv56uWfa8DCXYA39LA7MDA.png" /><figcaption>The core capability of an Enterprise Architecture Management tool: Planning the future IT landscape</figcaption></figure><h4>Towards a mechanical planning of the future IT landscape</h4><p>In this short post, I discuss what an Enterprise Architecture Management (EAM) tool is and how an EAM should be understood in relation to metadata management in general. First, we need to briefly describe enterprise architecture as a discipline.</p><h4>Enterprise architecture</h4><p>Enterprise architecture is an IT architectural discipline that demands substantial experience. Therefore, companies rarely have many enterprise architects employed. In general, enterprise architecture can be either logical — based on frameworks — or empirical — based on evidence of practices [1].</p><p>Ideally, enterprise architecture is not a discipline performed only by enterprise architects, but merely facilitated by these. Enterprise architecture is to some extent to be performed by everyone working with IT, from the IT operations architects to strategic leaders in the IT department all the way to the Chief Information Security Officer (CIO). The scope of stakeholders may expand outside of the IT department, but is typically limited to people with a relatively deep technical understanding.</p><p>Enterprise Architecture is a discipline that ensures a fit, functional and economically rational IT landscape. In order to deliver on that purpose, the heart of the enterprise architecture a is the capability map. A <em>capability</em> consists of people, processes and technology, that altogether deliver a distinct set of capabilities. Everything that a company is capable of doing, is the core metadata of the enterprise architecture, and laid out in the capability map.</p><h4>Enterprise architecture management tools focus at the future</h4><p>Enterprise architecture is often supported by specific technologies, known as Enterprise Architecture Management tools (EAM). EAM’s are intended for strategic decision making about <em>the future state</em> of an IT landscape. The EAM is therefore a distinct way to look into the future, based on existing knowledge and consequences of potential choices, rather than merely assumptions — and you can imagine that this requires solid, high-quality metadata.</p><p>The EAM must reflect the current state of the IT landscape, however it’s not intended to maintain the solidity of that overview alone. Accordingly, the EAM tool relies on other metadata repositories to reflect the current state of the IT landscape, typically the IT Service Management (ITSM) + Configuration Management Database (CMDB), cloud platform consoles and others, as illustrated in by the diagram in the top of the post.</p><p>The EAM tool must be aligned with these repositories and reflect them without containing the same level of detail as those, and also without taking over their responsibility: The EAM tool looks into the future and cater for that. It does not and should not maintain the in-depth surveillance of the current IT landscape — but it should certainly depict the current IT landscape in diagrams, reports and overviews.</p><p>If you try to force the EAM tool to be the metadata repository that <em>maintains</em> the overview of your current IT landscape, then you push the EAM tool towards external capabilities rather than its intended scope. The EAM tool will only deliver poorly on these external capabilities.</p><p>Also, EAM Tools are structured or contextualized to the many frameworks that enterprise architecture as a discipline is performed via the Open Group Architecture Framework (TOGAF).</p><p>The entire purpose of the EAM tool is to manage a company’s capabilities when looking into the future, and to be able to answer questions like:</p><ul><li>What will be the consequences of replacing our current CRM system with this CRM system?</li><li>What are our on premise dependencies and how would that affect a cloud migration?</li><li>Why do we have three applications delivering on the same capability, which ones could we most easily descope technically and what would be the economic benefit?</li></ul><p>To answer these types of questions about the future state of the IT landscape, many types of metadata are necessary, such as list of applications, integrations, components, projects, cost, strategy, technology categories, people, roles, teams and departments within the company.</p><p>Accordingly, the metamodels of EAM’s depicts these types of metadata. In the diagram below, you see one metamodel example from Ardoq :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*EOSaeQ07yA1Ok9H1" /><figcaption>An example of Ardoq’s flexible metamodel</figcaption></figure><p>Some vendors of EAM’s are: <a href="https://www.ardoq.com/">Ardoq</a>, <a href="https://www.leanix.net/en/">SAP LeanIX</a>, <a href="https://bizzdesign.com/">Bizzdesign</a></p><h4>Summary</h4><p>Enterprise Architecture Management tools allow plan the future IT landscape of companies. In order to do so, they rely on other metadata repositories, with which they are intricately interconnected. The EAM itself is a metadata repository too, in the sense that it depicts the IT landscape in the intersection of present and future.</p><p>[1] O. Olesen-Bagneux, <a href="https://medium.com/analysts-corner/enterprise-architecture-is-the-gathering-of-empirical-evidence-9a2c33b4d4cd">Enterprise architecture is the gathering of empirical evidence</a>, <a href="https://medium.com/analysts-corner">Analyst’s corner</a>, Jan 25, 2024</p><p>[2] <a href="https://www.ardoq.com/">Ardoq</a> is powered by a knowledge graph and therefore has a flexible metamodel. This has many advantages, that you can read about here (even though the book is about data catalogs, the arguments also hold true for EAM’s): O. Olesen-Bagneux, <a href="https://www.amazon.com/The-Enterprise-Data-Catalog/dp/149209871X#customerReviews">The Enterprise Data Catalog</a> (2023), O’Reilly</p><p>On Medium, <a href="https://medium.com/@olesenbagneux">Ole Olesen-Bagneux</a> writes exclusively for <a href="https://medium.com/analysts-corner">Analyst’s corner</a>. Currently, he is sharing thoughts from his upcoming book: <a href="https://www.oreilly.com/library/view/fundamentals-of-metadata/9781098162818/"><em>Fundamentals of Metadata Management</em></a><em> </em>(O’Reilly, 2025). You can also follow Ole on <a href="https://www.linkedin.com/in/ole-olesen-bagneux/">LinkedIn</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=857dbc871459" width="1" height="1" alt=""><hr><p><a href="https://medium.com/analysts-corner/what-is-an-enterprise-architecture-management-tool-857dbc871459">What is an Enterprise Architecture Management tool?</a> was originally published in <a href="https://medium.com/analysts-corner">Analyst’s corner</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>