How to get started with Enterprise Architecture? The topic of having common language and information. Part 2/4

One of the key things I have found most important when starting discussions around enterprise architecture (EA) matters is to communicate and understand people by using their own everyday language. Even if speaking the same language (e.g. English), it doesn’t necessarily mean people understand things the same way. One word written and spelled the same way can have different contextual meanings for different persons (for example, term ‘product’ might mean to a retailer the combination of the sales package and the stuff inside the box but for the manufacturer it might mean that the sales package is just the material part and the thing inside the package is the actual product). Therefore, you need to be able to define and explain a meaning of a word or a phrase using other words than the word or phrase itself.

Terminology can change depending participants of discussions. When asking ‘what do you mean with that thing’ or ‘what is your definition for that term’, I have found that there are no stupid questions when driving for common understanding between people. Therefore, when starting any kind of enterprise architecture related discussions or work, start it by creating a glossary of concepts and terms first, and also try to understand how different terms relate to each other.

After making that vital glossary of key business terms (data about terms and their definitions), create also a conceptual information model showing how terms relate to each other. Understanding the context how different kinds of terms and words are used in business and how they relate to each other is also the basis for the information architecture creation which is very important part of your enterprise architecture deliverables.

Since EA’s purpose is to create a systematic big picture of all matters related to an organization, using the language of the organization makes your enterprise architecture more understandable for everyone. When discussing with Enterprise Architects about enterprise architecture, there is a good chance we are already using a common vocabulary of EA methodologies, especially if architects are familiar with e.g. TOGAF or some other EA frameworks. But do not expect any other person than another Enterprise Architect to understand that EA jargon. Therefore, it is crucial to speak the language of the business.

So, if you are an Enterprise Architect, as a first thing you need to create a glossary of the business, learn the terms and adopt them by creating a conceptual information model of the key concepts and their relationships. That is also one of the most valuable enterprise architecture deliverables you’ll make and keep up to date. If you are a business stakeholder, help those persons trying to construct a business glossary since you’ll find it a very useful tool later on in your own work when discussing with people about your business.

Ari Anturaniemi

Chief Consultant, Enterprise Architecture

fi.linkedin.com/pub/ari-anturaniemi/3/572/a51/