Eetu Niemi, Ph.D.

What 20 years in enterprise architecture taught me about models, dialogue, decision-making, and using EA to understand dependencies and manage change.

Why choosing one EA framework is usually the wrong starting point—and how to use frameworks as practical building blocks instead.

What control, dependencies, jurisdiction, and exitability mean for enterprise architects

EA becomes more useful when its meanings and boundaries are clear: what it describes, how architects support change, and what belongs to other disciplines.

A practical EA health check before holidays: clarify open issues, decisions, ownership, escalation paths, descriptions, and the autumn pipeline.

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? A practical look at why EA ownership matters across architecture work, deliverables, and real decisions.

How internal enterprise architects and EA consultants create value through different positions, access, continuity, and perspective.

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? Learn how to match EA effort to complexity, risk, dependencies, and decision impact.

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 creates the most value: strategy execution, major change, coordination, long-term decisions, and complexity.