Explicit vs Hidden
My experience with EA has been, unfortunately, negative in that where EA has been called out as a specific function with EA-specific goals, it has failed. I believe that the failure is resultant of the separation of EA and its domain-specific activities from strategy, solution development and performance management. Where I've seen it successful, is when it is built into the solution development model and has business goals attached. The methods of delivery will be modified and the deliverables will also change to accomodate EA necessities - and this is a good thing - as those artifacts can then be reused for other solution-specific work. The downside to this "bottom-up" method is that rework may result as the EA view will necessarily be incomplete. This risk, IMO, is worth it as at least some progress will be made and the EA will be effectuated and developed through work that is meaningful to the organization. In other words, please stop calling it out as "EA" - no one wants it as a separate, check-the-box, stage gate and when allowed, EA practioners can get carried away to no immediate positive result.