- Operating Model
The operating model pattern embeds “moment ownership” and decision rights into organizational design, funding, and governance so AXIS outcomes are accountable, measurable, and continuously improved rather than treated as informal cross-team collaboration.
Why it matters for AXIS
AXIS treats moments as owned promises. Without an operating model, “moment design” becomes a workshop artifact with no enduring accountability. The Business Architecture Guild defines an operating model as an abstract representation of how an organization operates across domains to accomplish its function, which is precisely the layer where ownership, decision rights, and cross-domain coordination must be codified.
Embedding moment ownership and decision rights
AXIS ownership rule
Each moment must have a single accountable “Moment Owner” (business outcome accountability), plus explicit technical and data stewardship counterparts (implementation accountability). This mirrors the event-driven division of responsibilities where producers own schema/semantics and consumers own effect semantics.
Decision rights (minimum set)
- Moment promise changes (what the enterprise is committing to deliver).
- Policy constraints (privacy, safety, compliance).
- Orchestration boundary decisions and SLA commitments.
- Contract changes for trigger/signal events and telemetry definitions.
Funding and portfolio alignment
AXIS moments should be fundable units of value realization capacity, not project tasks. Lean Portfolio Management in SAFe explicitly defines LPM as aligning strategy and execution through strategy and investment funding, agile portfolio operations, and governance, and positions portfolios as sets of development value streams that support operational value streams for customers. Map “moments” onto this structure as outcome commitments tied to value streams and funded accordingly.
RACI examples
These are reference RACI patterns (adapt per enterprise structure; unspecified):
RACI for a moment (experience outcome)
- Accountable: Moment Owner (business leader responsible for the promise and KPIs), Business architect (Documentation, architecture enablement)
- Responsible: Product/Value Stream Lead (delivery and iteration), Orchestration Architect (boundary + failure design), Data Steward (signal definitions).
- Consulted: Security/Privacy, Architecture Board, Customer Ops, Platform Team.
- Informed: Downstream domain teams impacted by contract changes.
RACI for an event contract
- Accountable: Producer Domain Owner (semantic owner).
- Responsible: Process Architect (discovery, documentation, architecture enablement), Producer engineering team (schema + change management), Platform governance (broker policy), Observability lead (correlation standards).
- Consulted: Key consuming domains, architecture governance, privacy.
- Informed: All registered consumers through contract registry publication.
Competency requirements
Competencies are framed as cross-domain because AXIS moments traverse domains:
- Business architecture literacy: value streams, stages, customer value delivery/proposition, stakeholder roles, operating model interpretation.
- Event and contract discipline: schema/semantics ownership and change management.
- Observability engineering: distributed tracing and messaging semantic conventions.
- Governance execution: compliance reviews, SLAs/OLAs, monitoring/reporting, dispensations.
- Privacy and security risk management.
Change management steps
A pragmatic change sequence that aligns operating model shifts with governance controls:
- Stand up a “moment portfolio” with owners and a minimal KPI set per moment.
- Establish contract governance gates: publish event contracts and enforce compatibility rules in delivery pipelines.
- Standardize observability: adopt OpenTelemetry context propagation and messaging conventions across producers/consumers.
- Institutionalize governance cadence: compliance reviews for major moments and major contract changes, plus monitored SLAs and exception handling.
- Expand funding alignment: treat high-impact moments as funded initiatives within portfolio governance, consistent with LPM’s investment funding and governance model.
Anti-patterns
Five operating model anti-patterns that prevent AXIS from becoming an operating discipline:
- Everyone owns the moment: diffuse accountability, no single accountable owner, producing inconsistent outcomes and endless prioritization conflict. This directly violates the notion of governance as owned responsibilities ensuring integrity and effectiveness.
- Funding only features, not outcomes: portfolio decisions ignore moment reliability as an investment unit, despite LPM framing that aligns strategy and execution through funding and governance.
- No producer contract accountability: treating schema changes as “implementation detail” instead of the primary coupling contract, contradicting guidance that producers own schema/semantics and change management.
- Governance only at design time: no runtime monitoring and reporting against SLAs/OLAs, despite governance frameworks explicitly including these as key elements.
- Privacy bolted on after observability: extensive logging without minimization and purpose controls, conflicting with minimization principles and the reality that context and baggage propagate widely.
Five-step implementation checklist
- Assign moment owners: one accountable owner per moment, published in a moment portfolio registry.
- Establish decision rights: define who can change moment promise, orchestration boundary, event contracts, and SLAs.
- Align funding: create portfolio-level allocation for top moments, consistent with investment funding and governance orientation.
- Implement governance cadence: compliance reviews for major changes, plus monitoring/reporting routines tied to SLAs.
- Build competency and enablement: train producers/consumers on contract discipline, tracing propagation, and privacy guardrails.
