So, you’re busy working away at your models. The team is busy discussing the nitty, gritty things around taxonomies and ontologies. Others are creating detailed elaborations of different aspects of one of the dimensions of your enterprise architecture. You look at the work and say, “Damn this is good stuff!”
So now what?
The art of Enterprise Architecture is about influencing the stakeholders inside and outside of our organization that an EA will help them be more successful. How will they find out if we don’t tell them?
On the surface, this is really pretty 101 stuff. It really boils down to really answering the Who, What, When, Where, Why and How questions. I always start with Who.
Who do I want to communicate with and Why should they care anything about what the EA team has to say? That means that you need to take the time to know and…
View original post 756 more words
The crazy mind mapper... 
“The art of Enterprise Architecture is about influencing the stakeholders” indeed but the science is the work (blueprints, taxonomy…) the influencing is based upon. Without that, what would the influencing be about?
Influencing before delivering the enterprise architecture is like putting the cart before the horse.
Definitely agree Adrian, in other words, I would say: “if you didn’t do your homework, before going in front of your stakeholders… Don’t be surprised to get naked and throw away” 😉 Cheers!
Enjoy your holidays and merry Christmas to you Adrian.