Aggregated enterprise architecture wisdom
If you look for a great book on how to deal with the implementation and adaption of an Service-Oriented Architecture the book SOA for Profits is what you are looking for. The book was published back in 2007 but is still highly relevant. The focus is on handling the needed interaction with stakeholders to collaborate […]
In my last post I have written about embracing emotions to induct innovation. This was triggered by a good conversation on the Sapphire Now around Enterprise Architecture. Even though my approach to Enterprise Architecture is somewhat different than th…
We all possess the gene to want to solve problems when faced with them. It’s human nature. People form organizations and this gene sometimes manifests itself in organizational titles and roles invented to address organizational challenges. This is natural too. For example, when support organizations face the challenge of aligning to business organizations, we see…
Over the past couple of weeks, our American University of Sharjah IT teams have been working on creating a simple Service Coverage Matrix. We found that we had a knowledge gap with the distributed IT support structure at AUS. Not everyone knew who was the primary and the secondary service support analysts for all the technology […]
The post Helping Your Helpdesk appeared first on Enterprise Architecture in Higher Education.
In EA, we came to the rather original situation where everybody has his own EA approach and there are more frameworks than we can count. How many frameworks does one need though to design, document develop the same system and…
Technology today allows thieves to copy sensitive data, leaving the original in place and thus avoiding detection. Published in October 2012, the Jericho Forum® Data Protection white paper reviews the state of data protection today and where it should be heading to meet tomorrow’s business needs. Continue reading →
John Gotze and I have published a new peer-reviewed paper in the Journal of Enterprise Architecture with the title: A Systemic-Discursive Framework for Enterprise Architecture. You can download the paper from here (note: this requires AEA membership). If you are not a member of AEA let me know and I will send you a PDF copy of the paper.
This article examines, through a case study of an Australian government agency, the systemic and discursive properties of Enterprise Architecture adoption in a government enterprise. Through the lens of Luhmann’s generalised systems theory of communication, the authors argue that the manner in which organisational communication is organised throughout the Enterprise Architecture adoption process has a noticeable impact on successful implementation. Two important conclusions are made: Firstly, successful Enterprise Architecture adoption demands sustainable resonance of Enterprise Architecture as a discourse communicated in the enterprise. Secondly, misunderstanding and reshaping Enterprise Architecture as a management discourse is an inherent premise for high quality adoption. The authors propose a new theoretical model, the Enterprise Communication Ecology, as a metaphor for the communicative processes that precede, constrain, and shape Enterprise Architecture implementations. As a result, Enterprise Architecture as a discipline must adopt a systemic-discursive framework in order to fully understand and improve the quality of Enterprise Architecture management programs.
Enjoy!
John Gotze and I have published a new peer-reviewed paper in the Journal of Enterprise Architecture with the title: A Systemic-Discursive Framework for Enterprise Architecture. You can download the paper from here (note: this requires AEA membership). If you are not a member of AEA let me know and I will send you a PDF copy of the paper.
This article examines, through a case study of an Australian government agency, the systemic and discursive properties of Enterprise Architecture adoption in a government enterprise. Through the lens of Luhmann’s generalised systems theory of communication, the authors argue that the manner in which organisational communication is organised throughout the Enterprise Architecture adoption process has a noticeable impact on successful implementation. Two important conclusions are made: Firstly, successful Enterprise Architecture adoption demands sustainable resonance of Enterprise Architecture as a discourse communicated in the enterprise. Secondly, misunderstanding and reshaping Enterprise Architecture as a management discourse is an inherent premise for high quality adoption. The authors propose a new theoretical model, the Enterprise Communication Ecology, as a metaphor for the communicative processes that precede, constrain, and shape Enterprise Architecture implementations. As a result, Enterprise Architecture as a discipline must adopt a systemic-discursive framework in order to fully understand and improve the quality of Enterprise Architecture management programs.
Enjoy!
Using Stories to Cross the “Attention Chasm”Many people believe that the attention of audiences follow a U-shaped curve, where audiences remember mainly what said first and last during presentations, leaving a significant chunk of presented material in…
Using Stories to Cross the “Attention Chasm”Many people believe that the attention of audiences follow a U-shaped curve, where audiences remember mainly what said first and last during presentations, leaving a significant chunk of presented material in…
Upon reading the article titled As Chocolate Is To Peanut Butter, Strategy Is To Tactics, by Nacie Carson, author of The Finch Effect, two questions came to mind. How does the team leader/manager identify which of their organization’s strategic outcomes they can impact, either directly or indirectly and how much impact can they actually have?
The post Business Architecture enables Tactical “doers” to implement Strategy – Part 2 appeared first on Louise A Harris on Enterprise Business Architecture.
What’s the best kind of place to do enterprise-architecture and similar work? What are the best environments, for which parts of the work? And why? This was a fun set of questions that came up in my Twitterstream earlier this…