EA · AI · ROI
Where AI Strategy meets EA

Architecture nature is static. Architecture does not change after the building starts
DBJ Method uses simplified TOGAF EA artifacats to govern dynamic smooth running of the business.
Part of DBJ Method, “BPT” is an loop workflow made of three domains: Business, Products and Technology. Business declares the Product, and Technology is implementing the Product
The guiding principle of DBJ Method is to tailor the TOGAF artifacts, into the framework for plain sailing. DBJ Method is optimal path for a feasible business running
This Method exists to facilitate safe journey from the chaos of legacy to AI enabled organizaton. On the other side of the bridge
Detour for a very quick general AI Guidance
DBJ Method is based on TOGAF. DBJ Method is a runtime flow keeping the organisation running in a feasible fashion. Repeatedly raising the AI Readines level.
The Method engagement has two stages:
In the first step DBJ Method prepares clients for architecture-led delivery by putting them on firm (DBJ simplified) capability maturity foundations.
DBJ Method Practitioners are leading their client’s current organisational maturity to the (DBJ) ACMM Levels L0–L5. In this step DBJ Method Practitioners:
DBJ Method defines and documents architecture processes — moving the organisation from ad-hoc (L1) to defined (L3). By using this Method, DBJ Method Practitioners:
For full detail on the DBJ Method maturity model see DBJ CMM.

Continuous operational cycle
Once on-boarded to maturity Level 3 (or above), the client organisation enters the BPT Loop — a continuous cycle of three clearly decoupled segments: Business, Product and Technology, connected by constan flow of organization events.
BPT Method delivery-focused operational methodology is creating AI-ready organisations.
BPT Loop is using deliverables from projects based on DBJ ADM “Wheel”. These deliverales are organized into three repositories infroming the three BPT segments.

DBJ Method provides to the customer organization, the bridge over which users of the method cross from the chaos of Legacy to the feasibility of AI.
The future Clients future Architecture takes the natural position: it governs the loop.
![]() |
|---|
| © dbj@dbj.org | CC BY SA 4.0 |