Enterprise Architecture creates the most value when it helps an organization make better decisions. Maya Enterprise Architect Erkki explains why EA should be less about documenting everything and more about giving leaders the visibility to decide what to change, where to invest and what to simplify.
Most large organizations already have Enterprise Architecture in some form. There are application maps, architecture principles, technology standards and diagrams describing how different parts of the organization fit together.
But having architecture documentation doesn't necessarily mean that architecture influences the decisions shaping the business. When investment priorities are discussed, can leaders see what they mean for the wider technology landscape? When a system is modernized, is it clear what depends on it? And when several transformations happen at the same time, do we understand how they affect each other?
For Erkki, this is where the difference between documenting architecture and actually using it becomes important.
“EA becomes useful when it stops being a history record of the enterprise and starts influencing the future.”
The purpose isn't to give leadership every technical detail. It is to provide enough visibility into cost, complexity, dependencies and risk to make better decisions and reduce surprises later.
It's easy for Enterprise Architecture to become a catalogue of systems, integrations and technologies. That information has value, but documentation is a means, not the outcome. The real question is what decisions the information helps you make.
According to Erkki, EA should particularly help leaders decide where to invest, what to modernize or retire, and which risks to address first.
“The role of EA is to make the consequences and trade-offs of those choices visible before resources are committed.”
This becomes particularly important when individually sensible decisions start accumulating. A new application solves one business need, another project introduces a new platform, and an ERP transformation changes core processes and data while an AI initiative depends on those same systems.
Each decision may make perfect sense on its own. Together, however, they can create complexity and dependencies that only become visible later. Enterprise Architecture provides the wider view and helps leaders understand how individual choices affect the organization as a whole.
One of the traps in Enterprise Architecture is assuming that more documentation automatically means better architecture. Erkki sees it differently.
“The underlying analysis may be complex, but the leadership message must be clear: what is changing, why it matters and what decision is needed.”
Architects may need to understand applications, integrations, data flows, technologies and dependencies in considerable detail. Business and technology leaders usually need something different: a clear view of the consequences and trade-offs behind the choices in front of them.
This is also why EA shouldn't become another approval layer. Its role is not to make decision-making heavier, but to give leaders enough context to make better decisions.
For a CIO who already has architecture documentation but doesn't feel that EA is influencing decisions, Erkki wouldn't start by documenting more. He would start with the decisions the leadership team is struggling to make and then determine what architecture information is needed to support them.
Those decisions could concern which applications to modernize, where technology risk is accumulating, which capabilities require investment or what the target landscape should look like after a major transformation.
Especially in the beginning, Erkki recommends resisting the temptation to document a small part of the organization perfectly.
“Breadth matters more than depth. An 80% view across the enterprise with 20% depth is usually more useful than deeply documenting only 20% of the organization.”
A broad view gives leaders a map for making decisions. It helps reveal relationships and dependencies across the organization, while more detail can then be added where a particular decision requires it.
Tools such as SAP LeanIX can make architecture information easier to connect, maintain and analyze, but a tool doesn't create the capability on its own. Without clear use cases, ownership and connection to actual decisions, even a sophisticated EA platform can become another repository.
The better measure of Enterprise Architecture is therefore not how many applications have been documented or how complete the diagrams are. A much more useful question is whether the organization is making better decisions because EA exists.
As Erkki summarizes:
“The broad view gives leadership a map for making decisions. The narrow view may be accurate, but important dependencies and consequences may remain invisible.”
When EA provides that view, it stops being primarily a record of the organization as it exists today. It becomes a practical leadership capability for understanding the consequences of change before decisions are made.
Looking to make Enterprise Architecture more relevant to business and transformation decisions? Let’s discuss where to start.