What Is Enterprise Architecture—and Where Should It Stop?
EA becomes more useful when its meanings and boundaries are clear: what it describes, how architects support change, and what belongs to other disciplines.
Eetu Niemi, Ph.D.
A Small Enterprise Architecture Function Health Check Before the Holidays
A practical EA health check before holidays: clarify open issues, decisions, ownership, escalation paths, descriptions, and the autumn pipeline.
Enterprise Architect, Is Your Jargon Scaring People Away?
Why enterprise architecture jargon becomes a problem, when it helps, and how architects can explain complex ideas so people can use them.
Who Owns Enterprise Architecture?
Who owns enterprise architecture? A practical look at why EA ownership matters across architecture work, deliverables, and real decisions.
Internal Enterprise Architect or Enterprise Architecture Consultant?
How internal enterprise architects and EA consultants create value through different positions, access, continuity, and perspective.
The Architecture Questions I Ask Before an Initiative Starts
A practical enterprise architecture question for early initiatives: reveal scope, dependencies, and impact before solution design moves too far.
How Much Enterprise Architecture Is Enough?
How much enterprise architecture is enough? Learn how to match EA effort to complexity, risk, dependencies, and decision impact.
Should You Sell Enterprise Architecture to Leadership as a Framework?
Why leadership rarely cares about TOGAF, EDGY, or other architecture frameworks—and cares much more about better decisions, coordination, and change execution.
Where Enterprise Architecture Adds the Most Value
Where enterprise architecture creates the most value: strategy execution, major change, coordination, long-term decisions, and complexity.
Architecture Work or Architecture Theater?
Why some enterprise architecture practices create activity without impact—and how to recognize when architecture work does not influence real decisions.
When Personal Tools Become Enterprise Systems
How enterprise architecture helps manage shadow IT and low-code solutions as local tools evolve into shared systems with structural impact.
The Hidden Cost of Missing Architecture
Why the absence of enterprise architecture increases hidden costs. Understand structural patterns that make change more complex, slower, and harder to coordinate.