In one discussion about Business Architecture on LinkedIn, Ron Segal of Methodologist wrote "Too often there seems to be an expectation (amongst clients and 'architects' alike) that architecture is concerned with specifying the detail, rather than conceptual, structural, and strategic." Unfortunately, this is true.
We have to answer a simple question: are the Architects the state record writers only (producing the descriptions only) or Architectes are those who create and improve things based on the descriptions? I vote for the latter.
IMO, it is a mission of Architects - the Business and Technical ones - to promote, propagate the right expectations about the subject, disciplne and busienss values of Architecture as conceptual, structural, and strategic vision of different parts of the enterprise. Why is this so? It is simply because the consistent, coherent and agile vision of the enterprise may be achieved at such level of abstraction as concept, strategy, fundamental tasks and values (while the enterprise management besides the C-level executives concerns about particualr isolated tasks and objectives). Architects are supposed to architect, not only record and maintain whatever practice exists.
The first year of my BLOG is getting to the end. I have started it with an optimistic Phoenix of Service Orientation when many misunderstood the Anne Thomas Manes' statement about death of SOA. And I am finishing the year with a call to all Business and Technical Architects to do our job - to architect, to leave Designers their 'bread', to drive management to the right things, and to preserve and guard the business objectives and strategies by all means.
Happy Holidays to all of you and your families! Much more creative achievements in the coming 2010 year!
Leave a comment