Why Enterprise Architects are vital for Change Management - Part 1: What is EA anyway?
As a Manager of Organizational Change I have come to appreciate working with technology sources tremendously, in particular with Enterprise Architects. In my previous career as an expert for Organizational Communication & Development - working in lighthouse/pioneer projects and transitions of large corporate M&As long before this was even called change management - I had known IT people from some assignments facilitating teams, or teaching MBAs. When I got deeper into the IT world some 10+ years ago I remember thinking two thoughts:
Wow. This is a completely separate culture within companies, much different from all other departments, you won't get anywhere in here without speaking what I affectionately call 'Geekspeak' (Watching 'The IT-Crowd' does help to overcome the culture clash, though..).
And secondly, among my colleagues & friends or the (IT) Change Management Group at gpm-ipma, Germany's largest PM association, we absolutely agreed: If Change in Organizations goes wrong, it's almost always a "people problem".
I would like to reflect my view on this world back to you, maybe provide you with some fresh insights, and I'll start with the definition of Enterprise Architecture. There should really not be too many problems here, one could always look up wikipedia (how I dread the day I find out wikipedia is blatantly incorrect - always cross-check, boys & girls), or use common-sense.
Do companies know what to look for in an Enterprise Architect?
Flipping through companies' job postings, however, on the requirements side, one finds some must-haves that clearly display lack of ability to think on a metalevel. Partly, to be sure, because it makes measuring or filtering candidates' skills difficult.
Taking the term 'Architect' as a metaphor might be helpful. An Architect plans & monitors the building process of a house, she needs to know about plumbing or electrician requirements, yet doesn't have to be a plumber or electrician herself (*or himself - men are obviously included ;). Of course some time way back in her learning phase there might have been an internship, apprenticeship or practical studies field.
Back to Enterprise Architects and the metalevel. If an EA only needs to know ABOUT administrating systems, writing code etc. how can one assess if her skills are enough for a sophisticated job such as planning a business, its processes and technology?
I hear "Ask an expert" from the 3rd row. I am thus flinging this question to you, the experts among you. What criteria for skills and methods of Enterprise Architecture are indispensable to you, which parts do you value most? Is it more business or more techie or 50:50? How would you separate myth from reality? What are the obstacles in the daily routine? What difference does project management methodology contribute, scrum or waterfall?
I'd appreciate your input, to get a discussion going. Cheers!
And since I love thinking in terms of questions, here are the ones the next part(s) will revolve around: How does Enterprise Architecture relate to the many other Architecture job titles that seem to be in blooming season? Solution(s) Architect, Data Architect, Information Architect, Business Architect.. And what makes it invaluable for Change Managers to work closely with Enterprise Architects to ensure the success of the project?
Tune in..