Enterprise Architecture is just common sense, isn't it???

Well come on, it is ! Let's not get too complicated about this. You wouldn't build an extension onto your house without a plan, would you? or at least letting the builder have a look at what needs doing? The look of bewilderment on the faces of IT Project Managers when I tell them I have come to their organisation to gather together all the aspects of their business and details of their technology and place them into a structure using methodology X (Zachman, TOGAF, etc.) ,you would think I had just outlined a project to bounce ping pong balls off the moon. " I don't understand why we need to do this! My project is failing, do you really think I have time for this?" It's a times like these you need a Homer Simpson button.... DOH!!

Breaking whatever you are doing down into small chunks or levels of abstraction is simply logical, everyone does it. Questioning yourself about what you are doing, what your motivations are, When you have to do it and how you are going to do it are just natural. Structuring these abstracts into a framework just prevents you having to explain to the MD, for the tenth time, why you can't change the application to include a Extra Sensory Perception module until the TA has interpreted the BA's spec.

I understand it, please tell me there are others.