Enterprise Architecture’s Quest for its Proper Identity

Updated: March 18, 2011

The two questions are:

  • Is enterprise architecture primarily about IT or is it about the entire enterprise?

  • Is enterprise architecture a "hard" discipline or a "soft" discipline?

My answers:

Enterprise architecture ought to be about the entire enterprise, because that's what the name implies. If it's really about IT, it ought to be called enterprise IT architecture. Whether or not you believe it's possible or desirable to apply architectural thinking to the entire enterprise doesn't change the fact that we ought to name things honestly. And when we name architectures, it seems reasonable to me to expect that if an architecture is implemented primarily in the domain, it ought to be called an architecture. Adding two more syllables (IT) to the seven (en-ter-prise ar-chi-tec-ture), or inserting two characters (IT) in the acronym (EA), isn't an unbearable burden. Say it - "enterprise IT architecture." Spell it - "EITA."

Rarely has the cost of honesty been so modest. If you mean the architecture of an enterprise's IT assets and capabilities, say EITA. Don't say EA unless you really mean the architecture of the entire enterprise, not just its IT assets. Even if you consider the needs of the enterprise, or the structure of the enterprise's processes, if the implementation of the architecture you're developing will be mostly in the IT domain, it's EITA, not EA. Even if you believe that architectural thinking can be meaningfully applied only to the IT function of an enterprise, it's still EITA, not EA.

Soft discipline

My answer to the second question is that I believe enterprise architecture, as scoped above, is a "soft" discipline. I think talking about "manufacturing" or "engineering" enterprises is just silly; it's another example of the kind of aggrandizement that misnaming enterprise IT architecture represents.

Even calling an enterprise a "system" is risky. We use the word system in two senses. One is a very broadly inclusive idea, often expressed as "everything is a system," in that many things can be viewed as assemblies or aggregates of smaller components. This concept of system is useful because it encourages us to take a holistic, rather than reductionist, perspective, acknowledging that the relationships between the pieces are as important as the individual pieces themselves. The other sense of "system" is the one engineers use - a system is an artifact that has been methodically designed and built from interconnected components. Calling something a system in the first sense doesn't make it a system in the second sense; it doesn't make its behavior and performance analytically tractable or deterministic.

It is simply not possible to specify an enterprise as completely, and to the same level of detail, as it is to specify a building or a locomotive or an airplane. And, for the purpose of enterprise architecture, i.e., to ensure that an enterprise's assets and capabilities are aligned with its vision, mission and strategy, it isn't necessary to do so, even if we could.

It may be possible to do so for EITA, and maybe that's where the idea that the same can be said of the enterprise as a whole comes from.

Calling something a system in the first sense doesn't make it a system in the second sense; it doesn't make its behavior and performance analytically tractable or deterministic.



If the enterprise as a whole is a system, it's a people-intensive system, and as such one might as well talk about manufacturing or engineering people.

After all, why do we call them "enterprises"? Consider the first definition of the noun "enterprise" in the Oxford English Dictionary: "A design of which the execution is attempted; a piece of work taken in hand, an undertaking; chiefly, and now exclusively, a bold, arduous or momentous undertaking." Clearly implicit in this definition is that this is something undertaken by people. There's a nod to this reality when we refer to an enterprise as a "sociotechnical system", but the "socio" too often gets short shrift while the "technical" gets the bulk of the attention.

Yes, people play a role in other "systems" - they live and work in buildings, they drive locomotives and pilot airplanes. But people don't just interact with an enterprise; in a fundamental sense, they are the enterprise. And unlike buildings and locomotives and airplanes, enterprises are continually adapting themselves, in the homeostatic sense of maintaining their integrity and identity in the face of internal and external change, and in the sense of deliberately repurposing themselves in response to such change.

Featured Research
  • 2017 Contact Center Software Cost Guide

    Are you paying too much for your contact center software? Are you satisfied with its capabilities, or do you wish it did more? These are questions most businesses don’t take the time to think about, even though contact center software is one of the most important investments that you’ll make. With a little bit of planning, you can end up saving money and still end up with better functionality. more

  • What You Need to Know About VoIP Security

    No matter the industry or area of expertise, a strong VoIP system is the perfect tool for any business looking to take both its internal and external communication to the next level. more

  • Are You Using These 5 VoIP Features?

    In large part, the success of your business depends on the strength and reliability of your team’s many communication networks—this includes your Voice over Internet Protocol system (VoIP). more

  • Video Conferencing Best Practices

    Video conferencing is quickly becoming one of the most important communication channels for both small and big businesses. As more businesses turn to this technology, expectations about the experience are also rising. It’s not enough to just offer video conferencing as a communication method. You also need to meet minimum audio and visual standards, and there’s even proper etiquette to consider. more

  • 10 Contact Center Myths Busted

    For most forward-thinking companies, the use of contact center software is on the rise. That said, in spite of contact center software’s sudden rise in popularity, a number of myths have begun to take shape. more