I believe that the enterprise architecture (EA) function should also include organizational development (OD) as a key discipline in order to be effective. The underlying metaphor which many EA professionals use to view and understand corporations is that of a “machine”. The use of this metaphor brings us to discuss EA in terms of “design”, “structure”, “building”, “repairing”, etc.
Although this metaphor might be appropriate for discussing and managing technological issues, it is far too simplistic to manage the human impacts of EA visions and decisions. Despite this, all too often, we see or hear about situations in which this impact is managed by “planning”, “orchestrating” and “controlling”; all these words relate to the “machine” metaphor and have a connotation of “control” of the situation. Typically, one can only “facilitate”, “support” and “foster” change; all words which do not have a connotation of “control” but rather of “influence” on a situation. Hence, EA initiatives are greatly hindered by the natural resistance to change by all individuals when this change is managed by “control”.
Organizational learning is another important contribution that OD can bring to the EA function. EA roadmaps will most often require the enterprise to develop new knowledge and skills in order to implement them effectively as well as sustain that implementation. Despite this, the management of these learning needs is often second in importance to the implementation. An approach such as this can only eat away at the “value added” of the roadmap.
Process facilitation and human system intervention are other important skills from the OD domain which EA professionals should learn in order to :
-Build helping relationships;
-Facilitate problem solving;
-Give feedback;
-Help project teams become more effective;
-Be aware of group psychodynamics;
-Enable “grassroot” EA roadmaps.
I believe that the contributions of Schein, Lewin, Block and Senge should be part of the book collection of all EA professionals.