Eetu Niemi, Ph.D.

Why mapping data flows is the most practical way to deliver fast value in enterprise architecture

A lean approach to enterprise architecture governance that delivers results, not just PowerPoints

How to start measuring enterprise architecture effectively—even when it feels hard

A practical take on what it really means to keep enterprise architecture useful, sustainable, and fit for purpose

And what makes it different from most other enterprise architecture book you’ve seen

Enterprise architecture (EA) offers powerful tools for understanding and managing complexity. One of the most essential is also one of the most traditional: the application map. It shows what applications your organization uses and where change is needed. Here’s how to create one that works.

In some organizations, enterprise architecture (EA) has become a loaded term. This article explores how to (re)introduce EA without the jargon.

Uncovering Enterprise Architecture Benefit Realization – Part 3. Enterprise architecture (EA) only creates value when it is actively used—in planning, decision-making, development, and governance. But there’s a simple truth behind that idea: EA doesn’t create impact through ideas or conversations alone. You also need real, usable architectural content.

Enterprise architecture (EA) content often starts strong—structured application maps, fresh capability descriptions, clear target-state diagrams. But without a plan to keep it alive, even the best models quickly become outdated or forgotten.

This follow-up article focuses on what many architects ask next: How do you actually model capabilities in a way that gets used? Capability modeling may seem straightforward—but doing it well takes thoughtful structure, clear abstraction, and a solid connection to real-world needs.

Capabilities are one of the most effective tools in enterprise architecture (EA)—and one of the most practical ways to connect EA with leadership and strategy work. They describe what an organization does, regardless of how it’s done, who does it, or which applications are involved. That makes them a powerful bridge between strategic goals and execution.

Why you can’t build enterprise architecture from the bottom up—even if it sounds agile? At first, it sounds appealing. Lean. Agile. Efficient. Why bother with a top-down architecture model if your projects are already producing solution designs? Isn’t that enough?