Aggregated enterprise architecture wisdom
In two previous postings we have discussed the necessity of separating the what of architecture from the how (see here) and concluded that it is both useful and important to distinguish between a logical, ideal-world architecture description for a so…
In a previous post we discussed two levels of architecture description within ArchiMate: the service level describes the what and the underlying components and processes describe the how. The motivation for making this distinction was also discussed:…
Can You Make Sense of the Enterprise One of many reasons for why many enterprises experiences that organizational change projects fail and their respective leaders and managers only discovers that there are significant problems with the way the members of … Continue reading →
Who owns enterprise architecture? A practical look at why EA ownership matters across architecture work, deliverables, and real decisions.
“You can think of an enterprise as a physical algorithm for creating value.”
The question of how well you understand your own enterprise has always mattered. But it has never mattered more than now. As organizations race to embed AI acro…
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.
Why some enterprise architecture practices create activity without impact—and how to recognize when architecture work does not influence real decisions.
How enterprise architecture helps manage shadow IT and low-code solutions as local tools evolve into shared systems with structural impact.