http://blogs.msdn.com/nickmalik/archive/2006/04/22/581343.aspxThe role of an enterprise architect is not well understood. That much is clear. Some folks say that EA is at one end of the scale, while Web 2.0 is at the other. Those people are not enterprise architects. They are missing the point. Web 2.0 is abouten-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/nickmalik/archive/2006/04/22/581343.aspx#581824Mon, 24 Apr 2006 04:29:06 GMT91d46819-8472-40ad-a661-2c78acb4018c:581824Doug MutartThis really resonated with me.  As the enterprise architect, I've been asked by the CIO to take responsibility for making sure IT does the right things the right way (i.e. governance) and let the app dev and ops directors worry about getting things done.  That makes sense, but therein lies the challenge, since neither ops nor dev groups share all of the same values as me. So while I can get the architects to do the right things the right way and put enteprise concerns before project or operational concerns, it's still a challenge to get the ops and dev community to value that as well. Even if they "get it", they still end up valuing what their bosses value. The job of the architect is now to get everyone to value the same things to the extent possible through outreach, example, and carrot/stick.