Aggregated enterprise architecture wisdom
In our blog series on Capability-based Planning, we’ve aimed to empower you with enough knowledge to implement Capabilities and Capability-based Planning in your organization. We’ve looked at the concept ‘capability’ and its use in decision-making and planning, how to design Capability Maps and how Capability-based Planning relates to other disciplines. Although you may now be…
How much enterprise architecture is enough? Learn how to match EA effort to complexity, risk, dependencies, and decision impact.
Enterprise architecture often creates value indirectly. This article explains how distance to value creation affects visibility, influence, and compensation in architecture expert roles.
Throughout this five-part series, we’ve watched our fictional cleaning robot manufacturer, Garry’s Robots Ltd., transform their chaotic product development process by implementing a standardized prioritization framework. After establishing a data foundation, creating scoring structures, and securing organization-wide buy-in, they’re ready for the final critical phase: making their new prioritization approach sustainable. Even well-designed frameworks can…
Practical guide to choosing the right entry point for enterprise architecture—without getting stuck in analysis paralysis. In enterprise architecture (EA), both current-state and target-state documentation are essential. But when launching or scaling your EA efforts, which one should come first?
A collection of Enterprise Architecture terms and definitions from a variety of sources: EA3 Cube, Introduction to Enterprise Architecture, The Common Approach to Federal Enterprise Architecture (FEAF-II), ISO 42010:2011 and TOGAF 9. 00
A practical enterprise architecture question for early initiatives: reveal scope, dependencies, and impact before solution design moves too far.
Why leadership rarely cares about TOGAF, EDGY, or other architecture frameworks—and cares much more about better decisions, coordination, and change execution.
Why many enterprise architecture deliverables go unused and how to make architecture artifacts actually support real decisions and create measurable impact.
Why strategic traceability often looks rigorous—but changes very little
How architectural benefits actually form—before anything can be measured in hard numbers
According to McKinsey Partner Megha Sinha, who counsels Fortune 500 C-suites on AI and product transformation, companies can’t be AI-first without being product-first.