What is the key to effective enterprise architecture? In a word: influence. I rarely see an EA team that can’t build a reasonably good architecture, but I also rarely see an EA team that can successfully drive support for even the best of architectures. The most elegant architectures are worthless unless they are widely adopted and utilized. We don’t need more elegant architecture models; we need more eloquent architects.
Over the past few years I have asked hundreds of architects two simple questions. First: “What is more difficult – building architecture or implementing architecture?” Every single architect without exception tells me architecture is much harder to implement than to build. My second question is more telling: “Where do you spend the majority of your time?” Their answer: “Building architecture and my architectural skills.” Even though EAs clearly understand the problem, they don’t address it. Why is that? I think it is because deep down inside, they don’t want to.
Building organizational influence is long and difficult work. It requires an entirely different skill set than architecting. The focus is on people and relationships rather than technologies and concepts. Most architects don’t feel comfortable here. Instead of acknowledging reality and dealing with it, often architects try to avoid it by putting the problem on someone else’s back. “EA can’t succeed without executive sponsorship.” “Someone needs to give us more authority and control.” The fact is, very, very few EA teams actually get anything close to this. The majority don’t even get significant support from their CIO. And yet, somehow, many succeed. How? By building personal and organizational influence. The bottom line to EA success is organizational impact. How much are you having?
This comment was originally posted at eBizQ (http://www.ebizq.net/blogs/ebizq_forum/2010/07/what-is-the-key-to-effective-enterprise-architecture.php).