The short video below is one of the most concise and meaningful descriptions of Enterprise Architecture. If I'm honest, I've been very wary about using the Enterprise Architect label
for two main reasons:
negative experiences of 'detached from reality gurus'
synonymous with arcane and unwieldy frameworks.
The last point had the effect of burying Enterprise Architecture within IT where it's seen as a set of standards to be followed (e.g. COBIT or ITIL ) 'tick-box' fashion. Now I should say I've nothing against standards, indeed they're crucial for security and data privacy for example.
But I argue that Enterprise Architecture, whilst helping areas where strong standards & policy must apply, is really about 'dot-joining' all relevant aspects of the enterprise so it can de-risk and facilitate change.
As has been said before, the biggest risk in a so called 'Digital Transformation' is culture not technology. So in my book, the Enterprise Architect should equally proficient in EQ (emotional intelligence) as they are in IQ. I also read this equally interesting article today:
As Roger Evernden says, all organisations have an Enterprise Architecture, but many don't have an 'Enterprise Architect' (me: yet some with another job title). What do you think are the top three characteristics of a 'Enterprise Architect' in our, now undeniable, VUCA world?
A little old now, but this is the video I just stumbled upon by Roger Evernden that prompted this post.
Adaptive Change Design is aligned with both ThoughtWorks' and Roger Evernden's perspectives. But should we continue to call the role 'Enterprise Architect', or something else?