- Forrester Councils
- Councils Overview
- log in
Posted by Jeff Scott on May 3, 2010
The current metaphors for EA can be useful at a conceptual level to help non EAs understand what all the fuss is about. Most people understand the role of the building architect and the city planner and can make at least a rough association to what enterprise architects do. But many architects take these metaphors much too literally and much too seriously. They try to fashion their practice to align with the metaphor instead of taking the metaphor concept and creating a new way to apply it in their IT or business space.
The enterprise architect as building architect
I use this metaphor myself when I am talking with non architects. Conceptually, it is a very rich metaphor that almost everyone can identify with. Even though most people have never seen a complete set of blueprints, they have seen enough examples to get the point. Unfortunately, this metaphor breaks down pretty fast.
The enterprise architect as city planner
Though not quite as rich a metaphor as the building architect, city planning is a concept that most people can understand. Again, it breaks down pretty fast.
So what would be a better metaphor for EA or do we really need one at all? And metaphor or not, shouldn’t we be defining the practice of EA by what we do, instead of what we named it?
Save Money On Your Next Software Negotiation
Work with our software negotiation experts to save 10–20% on your next contract »
Lead BT Transformation
Develop customer-obsessed strategies to drive growth »
Forrester's CX Index
Predict how actions to improve CX will affect revenue performance.
Measure the customer experiences that matter most »