AMBIT — Architecture Methodology for Business & IT — is HighGrain's practice framework for establishing, running, and improving enterprise architecture practices. It is grounded in empirical research: systematic study of what organisations that achieve sustained business-IT alignment actually do, as opposed to what frameworks designed from first principles say they should do.
The distinction matters. Most enterprise architecture frameworks were designed by committees, consultancies, or individuals reasoning from first principles about what EA should look like. AMBIT's conceptual basis is different: it reflects what demonstrably works in real organisations, observed empirically across many cases over many years.
This grounding is not incidental. It is the reason AMBIT makes the claims it makes. Every structural choice — the six artefact types, the three processes, the four governance forums, the maturity stages — reflects what the evidence shows about how successful EA practices are organised.
Research describes. AMBIT prescribes.
The empirical research that informs AMBIT is descriptive: it documents what successful practices have in common. AMBIT is prescriptive: it translates that evidence into structured, actionable guidance for practitioners who need to know how to build and run a practice — not just what the literature reveals.
These are distinct contributions. An organisation that reads the research knows what a successful practice looks like. An organisation that implements AMBIT knows how to build one. AMBIT is the bridge between evidence and execution.
The six Ambits
AMBIT organises the full scope of an EA practice into six domains. Each domain is called an Ambit — from the Latin ambitus, meaning the circuit or compass of something. Together they go all the way around the subject.
1Ambit · Alignment Management
The three continuously running alignment processes — Strategic, Initiative, and Technology — together with the investment portfolio, the Governance Forums and the architect positions that constitute the operational machinery of the practice. The scope of operations.
2Ambit · Alignment Mechanics
The practical instruments: artefact templates, modelling approaches, software tools, governance assessment forms, straw-man architecture technique, practice measurements, architecture debt management, and the agility calibration framework that adjusts all of the above to organisational context. The scope of instruments.
3Ambit · Alignment Matrix
The taxonomy of six artefact types and their properties. Every planning document in a successful EA practice belongs to one of these six types. The Matrix is the backbone of the entire framework — without it, the other five Ambits have nothing to organise around. The scope of artefacts.
4Ambit · Alignment Meetings
The interaction cadence that keeps the practice alive: the D-E-A conversation pattern and the eight recurring meeting types through which artefacts are produced and decisions made official. The scope of conversation.
5Ambit · Alignment Models
The conceptual models through which architects understand their context: the Organisational Model, the Actor Model, the Transformation Driver Model (how IT investment decisions are actually made), the Discussion Point Hierarchy, the Initiative Typology and the Initiative Hierarchy. The scope of context.
6Ambit · Alignment Maturity
The practice lifecycle: how an EA practice is established (two distinct paths), how organisational acceptance is earned, how maturity is recognised and sustained, and the role of external consulting in a practice that must ultimately be self-sufficient. The scope of time.
What AMBIT is not
AMBIT is not a certification programme. There is no AMBIT examination or designation. Architectural competence develops through practice, not through passing tests.
AMBIT does not mandate specific artefact formats, specific tooling, or specific governance structures. Real EA practices are highly context-specific. The framework provides the models and patterns that successful practices share — which organisations adapt to their own context rather than implement literally.
AMBIT is not a static framework. Because it is grounded in empirical evidence rather than committee consensus, it updates when the evidence updates. As new research emerges and as practice surfaces patterns the current framework does not fully capture, AMBIT evolves. The commitment is to the evidence, not to preserving a version.
How this series is organised
The remaining seventeen articles work through the six Ambits, deepening from framework overview to operational detail. Parts II and III cover the Alignment Matrix and the three Alignment Processes — the core working machinery of AMBIT. Part IV covers the six artefact types individually. Parts V and VI cover the architects who run the practice and the lifecycle through which it matures.
Readers working with a specific element of AMBIT can go directly to the relevant article. Readers building a new practice from scratch will benefit most from reading in sequence through Part III before specialising.