• English
  • Nederlands
HOME
SEARCH
CONTACT
NEWSLETTER
 
 
 
CONTENT
About us
Call for contribution
Contributions
The CIO talks
Proceedings
Blogs
Master thesis
Forum
Wiki
Events calendar
Links
Login/Register
advertisements
Zoek je een baan?
Zoek je hulp?
Zoek je een opleiding?
Zoek je een boek?
Zoek je een tool?












 
 
BLOGS
What is wrong with the concept "Business Architecture"?
Alcedo Coenen   
Monday, 06 August 2007
There seems to be a insistent issue to get the "Business Architecture" concept clear, in particular to the "business" itself. Whenever I use the term or hear colleagues using it, the first reaction always contains something like "but it ís IT, isn't it?", even after repeated explanations that it is not IT but about the business. In some cases the explanation causes reactions like "Oh, but that is not architecture, we call that business strategy or organisational structure". In fact, when you listen to business managers talking about their strategies, that ís all "business architecture", except that it isn't written down on paper.

That leads me to the statement that the word 'Architecture' has a dangerous association that does not fit the core characteristics of "business". The core of business is negotiation, regardless whatever product the business is about; it is about adding value to the buyer, and receiving value in return, preferably a bit more value back than you give. Negotiation is a psychological play, with communicative tricks, in order to get this value difference big enough. Essential to this play is that you don't tell everything; you don't tell that the product is made very cheap, that you have a smart solution for cheap production, or you don't tell all details about the intellectual sophistication that is behind the product; what you do tell is how attractive it is for the buyer. Structuring this kind of activities is contradictory to this essential characteristic of the business, because structuring means you make things very explicit. Architecture is an instrument for engineers. Engineering is completely different from doing business, because it is about construction: making solid things that work. This kind of activity needs full explicit specifications, otherwise you may be unhappily surprised by the behaviour of your material. Business managers don't need specifications, they need instruments for influencing people. Business managers are never fully explicit, and therefore don't like the architecture concept: it makes things too explicit.




Be the first to write a comment
RSS comments

Only registered users can write comments.
Please login or register.




Share / deel
Del.icio.us!Google!Technorati!Yahoo!
 

Via Nova Architectura is not responsible for the content of blogs, but authors and readers are asked to adhere the following guidelines. Authors are strongly encouraged to check facts, cite sources, present balanced views, acknowledge and correct errors. Respect copyright, fair use and financial disclosure laws. Please do not disparage organizations, or individuals. Being critical of someone's practice is acceptable, when it is done in a professional manner. Prevent usage of marketing statements. Comments should be relevant to the specific post they are attached to. Spam, flaming, personal attacks, and off-topic comments are not permitted. Readers are requested to notify This e-mail address is being protected from spam bots, you need JavaScript enabled to view it of any violations. The editor holds the right to remove any statements that, in the editors opinion, infringe the above guideline(s). The author receives a notification of this action.
feed image
ISSN: 1877-2994