<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Roles on ProBase</title>
    <link>https://probase.ch/tags/roles/</link>
    <description>Recent content in Roles on ProBase</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Wed, 11 Mar 2026 18:07:26 +0100</lastBuildDate>
    <atom:link href="https://probase.ch/tags/roles/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Role Concepts in EAM</title>
      <link>https://probase.ch/blog/2026/02/28/role-concepts-in-eam/</link>
      <pubDate>Sat, 28 Feb 2026 00:00:00 +0000</pubDate>
      <guid>https://probase.ch/blog/2026/02/28/role-concepts-in-eam/</guid>
      <description>&lt;h2 id=&#34;role-concepts-in-eam&#34;&gt;Role Concepts in EAM&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#role-concepts-in-eam&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;h3 id=&#34;why-roles-in-eam&#34;&gt;Why Roles in EAM?&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#why-roles-in-eam&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;p&gt;Enterprise Architecture Management (EAM) operates within the tension between strategy, organization, IT systems, and operational processes. Without clearly defined roles, there is a risk that architecture work remains purely documentary or is carried out in an uncoordinated manner by various parties.&lt;/p&gt;&#xA;&lt;p&gt;Roles in EAM therefore fulfill several central functions:&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;1. Clarifying Responsibilities&lt;/strong&gt;&lt;br&gt;&#xA;Architecture decisions affect many areas of a company. Roles ensure clarity on who prepares, makes, or is accountable for decisions.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
