Six Reasons Why EA Should NOT be Assigned to the IT Department
6. EA ≠ IT Architecture
5. True EA leads to redistribution of authority, which is beyond CIO jurisdiction.
4. EA value proposition (i.e. standardization vs. innovation) is solely business realizable.
3. The primary goal of EA is to build coherent enterprises, not better IT systems.
2. Synthesis takes precedence over analysis.
1. EA failure is an organization failure, not an IT failure
Hi Stefan,
- I believe EA should be build based on Strategic Business decision.(Vision & Mission)
- Strategic Business decision is what triggers Objectives and Goals.
- Objective and Goals triggers Business Architect and its Business Requirement.
- Business Requirement is what triggers IT Architect and its Technical Specification.
So again EA ≠ IT Architecture and should not be assigned to IT department for following reasons:
- IT Architect is dependent on Business Architect.
- Business Architect is what drives Vision & Mission, Strategic Business Decision, Objects and Goals of organisation.
What is your opinion???
Hi Daniel,
yes, I agree to your thesis EA ≠ IT-Architecture and to almost all of your statements.
But you need a department which do the operative EA, the quality supervision etc. , the let's name it the "back office" of the EA. Where do we put it?
Definitely not to the business organisation department, they often don't understand IT as well as the IT-department understands business organisation. And IT is a big and complex part.
So, the IT-department is the best option to place the operative EA.
Of course, the IT-department can't define the business strategy, but it detects technical future trends and/or technical needs and affects the business strategy.
Business Requirements -> IT-Architecture is not a one-way-road.
