The book [[Enterprise Architecture as a Strategy]] suggests a [[Simplicity|Simple]] diagram is [[Enough is Hard to Recognize|enough]] to articulate the key aspects of a company's [[Enterprise Architecture]]. The book also states that EAs are better represented in principles, policies, and technology choices that are made. There are some common elements and considerations you should have, but there is no "one" Core EA Diagram to adhere to; instead it's better to use what makes sense to you. There are archetypical diagrams for each of the [[Four Types of Company Operating Models]]. # 4 Elements of EA Diagrams & 4 Operating Models | | Diversification | Coordination<br>(shared data) | Replication<br>(same process) | Unification | | ---- | ---- | ---- | ---- | ---- | | Shared Processes | ❌ | ❌ | ✅ | ✅ | | Shared Data | ❌ | ✅ | ❌ | ✅ | | Key linking/automation tech | ✅ | ❌ | ✅ | Optional | | Key customers | ❌ | ✅ | ❌ | ✅ | Not all of the four elements are important across all the 4 operating models. The EA Diagram for each can be kickstarted using a template like the ones below I made in [[Excalidraw]]: ## Diversification ![[Pasted image 20240209163137.png]] ## Coordination ![[Pasted image 20240209162706.png]] ## Replication ![[Pasted image 20240209163702.png]] ## Unification ![[Pasted image 20240209163435.png]] # Example Delta Airline's Core Business Processes are: 1. Operational Pipeline 2. Business Reflexes 3. Customer Experience 4. Employee Relationship Management ![[IMG_1442 Medium.jpeg]] # Pros & Cons of the Method > [!success] Pros > - By keeping the graphic small, it's easily consumed > - By keeping the graphic simple, it's easy to yield net positive [[Per Capita is more Important than Gross|ROI]] > [!failure] Cons > - The graphic is vague > - The graphic doesn't spur action, context is still needed **** ## Source - [[Enterprise Architecture as a Strategy]] ## Related - [[Diagram Types (index)]] - [[EA Visions]] - [[Diagram Types (index)]]