More Signal. Less Noise

During a recent Enterprise Architecture class, I received an unexpected lesson in clarity from my hearing aids (due to decades of flying jet aircraft). They weren’t working well — voices sounded muffled, and understanding people required more effort than it should have. Frustrated, I removed them, and to my surprise, I could hear better.

That moment offered a powerful metaphor for Enterprise Architecture.

When EA Becomes the Earplug

Enterprise Architecture is meant to help organizations understand themselves. We work to make strategies, capabilities, information, applications, technologies, stakeholders, investments, risks, dependencies, and transformations more comprehensible. We build models, establish repositories, create roadmaps, define principles, introduce frameworks, conduct assessments, and develop viewpoints. All of these can be enormously valuable. Yet there is an uncomfortable possibility we must occasionally confront:

“What if the organization can understand itself better when it removes EA from the conversation?”

Consider the executive who receives a 70‑page architecture presentation when what they truly need are answers to three simple questions: What should we do? Why should we do it? What happens if we don’t?

Or the project team navigating elaborate governance and terminology when what it really needs is help identifying a critical dependency. Or the business leader staring at a beautifully constructed model and quietly wondering, “What am I supposed to do with this?” At that point, architecture may still be technically correct — but it is no longer functioning as a hearing aid. It has become an earplug.

Amplification Isn’t Understanding

A poor hearing aid may amplify and clarify sound, but louder isn’t alone isn’t necessarily clearer. If conversation, traffic, air conditioning, and background chatter are all amplified equally, the listener may actually understand less. The real challenge is distinguishing signal from noise.

Enterprise Architecture faces the same dilemma. Organizations are swimming in information — strategies, initiatives, projects, requirements, capabilities, processes, applications, technologies, data, risks, regulations, metrics, investments, organizational structures, customer expectations, vendor proposals, transformation programs, and now, vast quantities of AI‑generated content.

The architect’s job cannot be to amplify all of it. We must help the enterprise determine what matters, what connects, what conflicts, what is changing, what requires a decision, and what should happen next.

“That is signal. Everything else risks becoming noise.”

A Better Measure of Architecture Success

Perhaps it is time to rethink how we measure architecture maturity. Instead of asking only how sophisticated our practice has become, we should also ask:

“A mature EA practice should reduce cognitive burden, not increase it.”

We should ask: How much easier does our architecture make the enterprise to understand? Does architecture improve the quality and speed of important decisions?

A mature EA practice should reveal dependencies rather than merely document them. It should expose choices rather than obscure them. It should translate complexity without pretending complexity doesn’t exist. And above all, it should help people act.

The goal isn’t fewer models for their own sake. The goal is greater clarity — more signal, less noise.

Authored by Dr. Steve Else, Chief Architect & Principal Instructor