What DA-ARB Does Differently

Most ARBs engage at the end — when decisions are already made, commitments are in place, and the cost of changing course is high. DA-ARB engages progressively, from the earliest moment a design decision is forming, and scales the depth of that engagement to the actual risk and complexity of the work. The result is governance that teams choose to engage with early — because early engagement is genuinely useful, and because teams that engage early earn a streamlined formal review. Three principles distinguish the approach: **Proportionality.** Governance intensity matches decision significance. Low-risk work moves through with minimal overhead. High-risk work receives the attention it warrants. The board does not treat a configuration change and a new platform architecture as equivalent governance events. **All three manifestations of architecture.** Architecture exists simultaneously as documented (explicit), understood by the people working with it (embodied), and enacted in running systems and organisational routines (embedded). Most governance processes engage only with documents. DA-ARB is designed to engage all three — through structured documentation, through dialogue with submitters, and through the Monitor stage that tracks what is actually happening in production. **Commitment over compliance.** Governance that produces procedural compliance without genuine understanding will revert. DA-ARB is designed so that teams progressively develop real conviction about why architectural standards exist — moving from awareness through genuine adoption, not just formal acknowledgement.

The Eight-Stage Funnel

DA-ARB operates as an eight-stage model. Governance effort scales proportionally as the work progresses and decisions become more consequential. **Stage 1 — Self-Assessment** Every initiative begins here. The initiating team completes a structured self-assessment that surfaces architectural risks, establishes evaluation criteria, and determines which subsequent stages are warranted. Designed as a quality detection mechanism — making it easier to surface a risk than to conceal one. **Stage 2 — Information** Curated architectural standards, reference materials, decision frameworks, and precedents — available continuously to any team at any time. **Stage 3 — Guidance** Active, tailored direction from the DA-ARB for each initiative that reaches this stage. The first stage at which the board engages per initiative rather than per organisation. **Stage 4 — Advice** Substantive and collaborative. Subject matter experts join the core board as the topic demands. The character of this stage is conversational — the aim is to improve the work, not to assess it. **Stage 5 — Design and Architectural Review** A formal review conducted before deployment for initiatives that exceed a defined risk or complexity threshold. Because earlier stages have already shaped the work, the review functions as confirmation rather than discovery. Teams with active prior engagement records qualify for a streamlined review. **Stage 6 — Monitor** Production-phase advisory governance. The board receives compliance signals from operational monitoring functions, classifies them against a five-degree compliance spectrum, and issues Compliance Position Statements. This is where the embedded reality of architecture — what is actually running and how it is actually behaving — enters the governance process continuously. **Stage 7 — Audit** Examines whether the architecture in production remains coherent with the approved design and the understanding of those responsible for it. Informed by the Monitor stage's accumulated Compliance Position Statements. **Stage 8 — Learn** Converts governance experience into organisational knowledge. Updates architectural standards, shares lessons with the wider EA community, and challenges the governance framework itself. The mechanism by which DA-ARB stays alive and evolving rather than fixed.

Who It Is For

DA-ARB is most effective in organisations where: - Architecture and execution are entangled — decisions emerge progressively rather than being designed once and built exactly - Governance currently functions as a gate rather than a service - Architecture standards are acknowledged on paper but not genuinely adopted in practice - The organisation is navigating significant regulatory or technical change — EU AI Act compliance, platform consolidation, AI adoption — where architectural governance needs to do more than enforce checklists ---

Relationship to Interweaving and iEA

DA-ARB is a constructed method within the Interweaved Enterprise Architecture (iEA) framework. It applies Interweaving principles directly to governance design: recognising that architecture exists in three forms, that the people affected by decisions should be engaged when they can most meaningfully contribute, and that governance serves both control and the building of shared commitment. It is not a standalone product. It is deployed as part of an architectural engagement — configured to the organisation's context, risk profile, and existing governance structures.