BPT Domains are regions of gravitational pull for organization roles, circling around them.
- Business roles to the Business Domain
- BA roles around the Products Domain
- Engineers and DevOps around the Technology Domain
The BPT loop is not free-for-all, first comes first served. Different roles are assigned to different segments. That fact defines jurisdiction — the boundary within which a role operates, decides, and is accountable.
Jurisdiction is not hierarchy. A Business Leader is not senior to an Engineer in the BPT loop. They operate in different domain with different role bound concerns. (hint: EA is the only role whose jurisdiction is the whole organisation).
Roles and Jurisdictions
| Roles | Jurisdiction | Activities |
|---|---|---|
| Business Leaders, Clients, Product Owners, BAs | Business | Declares products, owns outcomes |
| Product Owners, BAs, QAs | Product | Bridges Business declarations and Technology capabilities — the alignment point |
| Engineers, Developers, DevOps | Technology | Implements what Product defines |
| Enterprise Architects | Organisation | Overarching — governs the meta-layer, guides all transitions without bottlenecking |
BA — Business Analyst. QA — Quality Assurance.
Enterprise Architecture jurisdiction
EA’s jurisdiction is the whole organisation — not a segment, not a project. This is what makes it the governing role.
- Defines the principles that guide all four BPT transitions (Require / Develop / Deploy / Evaluate)
- Ensures Product decisions maintain Business-Technology coherence
- Governs without slowing the cycle
- Measures alignment health through Evaluate feedback
- Runs the DBJ ADM wheel — the governance project container.
EA does not implement, does not manage products, and does not operate infrastructure. It governs the structure within which all of those happen.
Why this works
- Organisations at sufficient CMM level have implicit governance structures — roles respect boundaries because the organisation is mature enough to enforce them
- Product management becomes the operational manifestation of architecture — the alignment point is staffed and accountable
- The loop tests architecture decisions against reality continuously — Evaluate is not optional activity
- The question “Is Business aligned with Technology?” becomes measurable rather than political slogan
Domain naming and role naming
The BPT domain are named Business, Product, and Technology. The roles inside the Technology segment are primarily Engineers and DevOps — Engineering describes the roles, Technology is the domain name. This distinction matters when reading diagrams and deliverables: the domain name is always Technology.
Definitions and terms may appear in singular or plural depending on the size of the organisation. It is rare for there to be only one product or one team. The model scales — see One wheel or many.