Modern enterprises juggle TOGAF, Agile/SAFe, Lean Portfolio Management, and change management – but often as separate, competing worlds. The proposed unified operating model for architecture turns these into one coherent system.

1. One three-level spine for everything

Use a single structure across all methods:

• Strategic level – direction, value streams, KPIs, portfolio epics (TOGAF Strategic Architecture, SAFe Portfolio).
• Segment level – just-enough solution architecture per product/domain (TOGAF Segment, SAFe Solution/ART, capabilities & features).
• Capability level – detailed, implementable design and operation (TOGAF Capability Architecture, SAFe teams, stories & enablers).

Every artifact, role, and ceremony must clearly declare which level it belongs to and how it connects up and down.

2. Stakeholders and architects as explicit partners

• Stakeholders define outcomes, constraints, and acceptable trade-offs (they are the principals).
• Architects act as agents of stakeholders: translating concerns into structured requirements, making options and trade-offs explicit, and reconciling conflicting viewpoints.

This clarifies accountability and shifts architects from “documenters” or “policemen” to professional decision enablers.

3. One requirements backbone, many views

Instead of competing requirement hierarchies:

• Separate “what” (needs, goals, requirements, constraints) from “where/when” (portfolio, PI, sprint) and “who” (roles/teams).
• Maintain a shared requirements / concerns backbone, then:
  • View it as goals, capabilities, and constraints (TOGAF).
  • View it as epics, capabilities, features, and stories (SAFe).

TOGAF catalogs and SAFe backlogs become different views on the same underlying objects, improving traceability and reducing friction.

4. Architecture as code with minimalistic artifacts

To balance agility and rigor:

• Express architecture in markup / code-like form stored in the same repos as application and infrastructure code (“architecture as code”).
• Use minimalistic artifacts with tiers of detail:
  • Tier 1 – vision sketches
  • Tier 2 – decision-ready outlines
  • Tier 3 – full specs only where necessary (compliance, high risk)

This supports iterative delivery while preserving architectural integrity.

5. Governance as embedded, continuous guidance

Move from late, heavyweight gates to continuous, embedded governance:

• Strategic level: Lean Portfolio Management with architectural guardrails and portfolio Kanban.
• Segment level: Architects embedded in PI planning, ART events, and solution demos; early option reviews instead of late approvals.
• Capability level: Policy-as-code, quality in Definition of Done, ADRs and architecture PRs as part of normal delivery.

Governance is reframed as helping teams make better decisions, not catching them out.

6. Business value

This unified operating model:

• Reduces framework conflict and duplication of effort
• Aligns strategy, architecture, portfolio, and delivery around a shared structure
• Improves decision quality and speed, with clearer trade-offs and traceability
• Integrates human motivation and culture into architecture and governance practices

In short, it doesn’t replace TOGAF, SAFe, or LPM – it connects and orchestrates them into a single, business-focused architecture operating model.

Authored by Alex Wyka, EA Principals Senior Consultant and Principal