The Missing Link Between Application and Enterprise Architecture

I very often meet frustrated project managers and application architects complaining about smart-ass enterprise architects armed with high-level PowerPoint slide-ware about transformation, innovation and consolidation. It is unclear to these people how enterprise architecture (EA) can help them in their daily lives and they therefore see EA as a gatekeeper and resist the enterprise-wide perspective. But, why do we see this missing link again and again and how can we bridge the gap?
An EA tells the organization where they are on the IT map and identifies a transition plan for building a desired “to-be” architecture whose scope encompasses all of the computing of an enterprise. Application architecture designs, implements and maintains specific IT-systems. Hey, what is the problem?! The way I see it, the problem is the missing link is between the top-down EA work that defines and sponsors strategic IT projects and the bottom-up needs of business managers and innovative application architects.
I think governance and communication is two of the key ingredients if we want to bridge the gap between EA and application architecture. We need to define a clear link between processes for system development, project management, vendor management, capital planning, and strategic planning. It must be clear for the project managers and application architects how the EA program will help them in their daily lives and it must be clear to the EA program that they can not live in an ivory tower disconnected from the practical concerns of everyday life in the IT engine room.
I have seen some great example of how EA programs are reaching out to application architects. But, unfortunately, most of the programs I have seen are struggling to find the missing link. If any of you have experiences with this “missing link” please let me know. I will be working with my colleagues from IBM on this issue. Maybe they have some shelf-ware that can help us