It Is NOT an Enterprise Architecture if...
- Your CxOs don't know what it is, and don't care what it says.
- Your strategic thinkers do not agree with what it says.
- It covers one area of the Businesss without considering the whole (and yes, IT is one part of the Business).
- It does not start with a single big picture that can be drawn on one piece of paper (and still be legible).
- There is more than one of it. (Question: "Do you have an EA?", Answer:"Oh yes! We have lots!").
- It tells you what the present looks like without telling you what the future is supposed to look like.
- It tells you how to work out the answer instead of telling you what the answer is.
- Using it is a burden for your projects instead of a boon.
- It is easier to ignore it than it is to follow it.
- What it says has not been agreed with the business leaders.
- It can be interpreted in many ways to suit many agendas.
- No one is looking at it and saying "That's it! That's what I wanted!".
- You cannot implement it in stages.
- It takes many people and many months to develop before it becomes useful.
- It is deemed to be complete. (My work here is done *whoosh*).
- You have to understand all of it before you can deliver a part of it.
The Enterprising Architect