Twenty articles. One framework. One discipline.
I want to close with something that is less about AMBIT and more about the kind of framework I am trying to build.
Most EA frameworks are frozen. They are written, published, certified, and then periodically revised in ways that reflect commercial considerations as much as new evidence. The version you implement today is essentially the same framework someone implemented years ago, regardless of what the discipline has learned in the interim.
AMBIT is grounded in empirical research — in what organisations that genuinely achieve business-IT alignment actually do. That grounding creates an obligation that a theoretically constructed framework does not have: the obligation to update when the evidence updates.
As the underlying research develops, as other researchers contribute to the empirical body of knowledge on EA practice, as my own work with organisations surfaces patterns that the current framework does not fully capture, AMBIT changes. Not arbitrarily — every change needs justification from the evidence or from observed practice. But the commitment is to the evidence, not to preserving a version.
What AMBIT does not yet handle well
- The interaction between EA practices and platform engineering organisations, where the traditional boundary between architecture and engineering is dissolving.
- The implications of AI-assisted architecture for which decisions still need human judgement and which can be delegated to tools.
- The governance of technology investment in highly federated organisations, where the concept of an organisation-wide IT landscape is more aspirational than real.
What a framework cannot do
AMBIT describes the shape of a mature EA practice. It does not — cannot — tell you how to build the trust with your CFO that makes Strategic Alignment possible. It does not tell you how to navigate the political dynamics of an organisation where IT and business have a history of adversarial relationships. It does not tell you how to demonstrate value quickly enough to survive the first funding cycle.
- How to build trust with senior executives who have been disappointed by IT before.
- How to navigate organisational politics when competing departments have conflicting investment priorities.
- How to demonstrate value quickly enough to survive the first budget cycle.
These are human problems. They require human judgement, contextual reading, and the kind of practical wisdom that accumulates through experience rather than through reading frameworks. AMBIT gives you a map. It does not give you the navigational skill to use it in every terrain.
What it does give you, I hope, is a coherent picture of what you are building toward — a mature practice in which business and IT leaders genuinely understand each other, in which IT investment reflects strategic intent, in which the IT landscape is being actively maintained rather than passively accumulated, and in which architects are trusted partners in organisational decision-making rather than technical reviewers attached to delivery projects.
That is the ambition. The scope, range, and sphere of operation that gives the framework its name.