Applicability
This concept applies to any project, driven by underlying DBJ ADM wheel. Examples:
- Wheel 1: LLM Adoption wheel — authorizes or rejects LLM introduction into a capability
- Wheel 2: Cloud Migration wheel — authorizes transition from on-premise to cloud hosting
- Wheel 3: Data Governance wheel — establishes data ownership, classification, and retention rules
Each wheel is the same structure. Each wheel’s artifacts are specific to its topic.
One wheel or many wheels
The DBJ ADM is designed to scale — from a single wheel covering an entire small organisation, to many concurrent wheels each scoped to a domain, programme, or capability cluster in a large enterprise. The concept is flexible by design; it does not impose full TOGAF rigour on organisations that cannot sustain it.
A single wheel is appropriate when the organisation is small, the IT landscape is simple, or the engagement is narrowly scoped. One wheel, one set of deliverables, one governed cycle.
Multiple concurrent wheels arise naturally in larger organisations or complex engagements. Each wheel is independently scoped and governed. They may overlap in time. EA coordinates them — ensuring their Conceptual outputs are coherent with each other and that no two wheels produce conflicting Principles or Architecture Visions.
Not every wheel triggers the full BPT response A wheel scoped to a purely Conceptual outcome — a capability assessment, a standards review, a compliance audit — produces deliverables that land only in the Business repository. No Product segment is triggered, no Technology segment acts. The wheel closes when its governance artifacts are accepted. This is a complete and valid outcome.
Conceptual deliverables are stored in the “Business Repository” and are applicable across several domains. (Example: “We will host on a public cloud”)
What does not change is the structure. Regardless of how many wheels run, or how small the organisation:
- Every wheel
- follows the DBJ ADM structure
- uses Requirements Management and REQ traceability
- deliverables land in the correct BPT repository
- EA role is clear: It governs all DBJ ADM “wheels”
- even if EA is one person
The DBJ ADM does not replace an organization’s existing governance practice. If a mature practice exists, the wheel integrates with it. What the wheel provides is the minimum viable structure for organizations that have none.