FAQ: Enterprise Architecture Webinar Series — Clearing the Myths, Resetting the Practice

This post focuses on myths, misconceptions, and the architecture corrections that EA series delivers

1. Why are you saying 120–200 IT projects ≠ Enterprise Architecture? Isn’t that what EA teams actually manage?

Myth: EA is a catalog of IT projects, APIs, applications, and compliance tasks.

Reality: If EA becomes a project inventory, it loses its purpose.Enterprise Architecture is meant to explain how the enterprise actually works — strategy, processes, systems, rules, components, and operations (P1–P6).

This series shows why large IT project counts signal fragmented enterprise anatomy, not maturity.

2. Why do different industries have different numbers (130, 170, 220 IT projects)? What does that even mean?

Myth: More IT projects = more digital progress.

Reality: More IT projects usually indicate:

• scattered decision-making

• duplicated logic

• disconnected departments

• unclear ownership of rules and processes

This series demystifies industry-specific patterns and shows how One Enterprise, One Anatomy™ reduces the chaos.

3. We already have TOGAF/SAP/BizArch frameworks. Why do we need this?

Myth: A framework automatically creates enterprise architecture.

Reality: Frameworks give boxes and arrows.They do not:

• diagnose failures across departments

• map P1–P6 execution breakdowns

• show how strategy, process, logic, and operations drift apart

• reveal why IT delivers but the enterprise doesn’t move

This series explains how ICMG Enterprise Anatomy™ provides a practical diagnostic model, not a theoretical one.

4. Is Enterprise Architecture just IT modernization with a new name?

Myth: Enterprise Architecture = IT modernization.

Reality: EA is the alignment of strategy → process → systems → logic → components → operations. IT modernization may fix technology, but often leaves:

• policy logic untouched

• process variations unmanaged

• data rules unclear

• departmental drift unaddressed

This series shows how architecture fixes problems above the IT layer, not inside it.

5. Why is each industry getting its own briefing? Isn’t architecture the same everywhere?

Myth: EA is generic — one version works for all sectors.

Reality: While P1–P6 is universal, every industry has:

• unique decision cycles

• different rule engines

• different operational bottlenecks

• different fragmentation patterns

Airlines ≠ Retail ≠ Banking ≠ Pharma. The series highlights industry-specific anatomy failures and corrections.

6. Why are directors and chief architects the target audience? What about CIOs and CTOs?

Myth: EA is the CIO’s side responsibility.

Reality: This series is aimed at people responsible for restoring enterprise coherence — typically Directors of EA, Chief Architects, Senior Architects, and Strategy–IT translators.

CIOs gain value too, but the core execution corrections sit with the EA leadership.

7. Will this series focus on tools, applications, and technology stacks?

Myth: EA = tools (ArchiMate, ABACUS, AWS, etc.)

Reality: Tools help only when the underlying enterprise anatomy is clear. This series clarifies the anatomy first — then shows how tools can be aligned to it.

8. We already have 1000+ pages of architecture documentation. Why redo this?

Myth: Document volume = architectural clarity.

Reality: 90% of documentation hides the real problem: no single, consistent view of how the enterprise works.

This series shows how to collapse complexity into a single coherent model — readable by leadership and actionable by teams.