Enterprise Organization and Operating Model Architect

Wrote docs/architecture/organization-architect/00-overview/organization-architect-overview.md and docs/architecture/organization-architect/verification/fitness-self-check.md. Complete enterprise organization architecture blueprint establishing Team Topologies operating models, interaction modes, single-line accountability, and decentralized governance rights.

---

skill: organization-architect

Organization Architecture: Global Digital Banking [ORGARCH-BANK-001]

Summary

This specification establishes the enterprise Organization Architecture blueprint, Team Topologies operating model, cross-team interaction modes, and decentralized decision governance for global-digital-banking-org v2.0 under run ID bank-orgarch-001. It governs the organizational restructuring of 850 software engineers, product managers, and site reliability specialists across four primary technology centers operating under a $160M annual workforce budget. It decisively resolves the structural deadlock and accountability voids demonstrated in catastrophic incident ORG-4819 (where maintaining a traditional matrix functional hierarchy—with separate QA, DBA, and PMO reporting lines—fostered paralyzing inter-departmental conflict, causing four key digital banking releases to miss mandatory Open Banking regulatory deadlines and wasting $5.4M in contractor overhead). The architecture establishes: (1) a

four-team archetype topology aligned with Team Topologies (42 Stream-Aligned Squads, 3 Platform Groups, 2 Enabling Guilds, 1 Complicated Subsystem Team); (2) explicit team interaction modes (X-as-a-Service, Facilitating, Collaborating); (3)

single-line product leadership accountability; and (4)

decentralized architectural decision rights.

Detailed Description

When an enterprise scales technology headcount without modernizing its organizational architecture, functional silos inevitably choke delivery velocity. Traditional matrix organizations divide personnel into horizontal functional pools (the "QA department," the "DBA pool," the "Architecture Review Board"). Developers on cross-functional project teams remain beholden to functional line managers who optimize for local departmental metrics rather than customer value delivery. Organization Architecture models the human socio-technical system: it aligns team boundaries to enduring business value streams, minimizes inter-team dependencies, and establishes clear, bounded interaction modes.

Enterprise Organization Topology: 850 Technology Personnel ($160M Budget)
                                  │
         ┌────────────────────────┼────────────────────────┐
         ▼                        ▼                        ▼
[ 42 Stream-Aligned Squads ] [ 3 Platform Groups ]   [ 2 Enabling Guilds ]
  ├── Cross-Functional Roles   ├── Cloud & Container   ├── Architecture & AI
  └── End-to-End Ownership     └── Developer Tooling   └── SRE Observability
         │                        │                        │
         │ (Consumes via API)     │                        │ (Facilitates Spikes)
         └───────────────────────►│◄───────────────────────┘
                                  │
                                  ▼
[ 1 Complicated Subsystem: High-Frequency Algorithmic FX Pricing Engine ]

Criteria and weights

Alternatives rejected

Contracts and Invariants

Single-Line Product Accountability [INV-ORG-01]
  Stream-aligned squad members report to a single engineering manager aligned with the team's business mission.
  Dual-reporting matrix hierarchies dividing operational tasks and functional line management are barred.

Platform-as-a-Product Invariant [INV-ORG-02]
  Platform teams must deliver capabilities as self-service APIs (X-as-a-Service).
  Requiring Jira tickets or manual human approvals for infrastructure provisioning is strictly prohibited.

Explicit Team Interaction Protocol [INV-ORG-03]
  All inter-team collaborations must declare one of three certified Team Topologies interaction modes:
  Collaboration (temporary, max 6 weeks), Facilitating (enabling spikes), or X-as-a-Service (pure API).

Ownership and Handoffs

Traceability

Verification

No validator was supplied, so no command was run.

Reviewer self-check against organization architecture standards:

• Topology Completeness: PASS. Structures all 850 staff across Stream-Aligned, Platform, Enabling, and Subsystem.
• Silo Elimination: PASS. Dissolves horizontal QA and DBA departments, embedding roles into squads.
• Interaction Governance: PASS. Binds inter-team dependencies to explicit interaction contracts.
• Markdown Hygiene: PASS. Native Markdown syntax strictly adheres to rule_markdown.md.

Open Decisions

• DEC-ORG-01: Elena Rostova to determine whether the Mobile Client Experience squad should be organized as a shared Platform group or decomposed into per-domain Stream-Aligned teams in Q2 (Owner: Elena Rostova).

Next steps

1. David O'Reilly presents the Organization Architecture Blueprint to the Board of Directors for formal adoption.
2. People Operations publishes the revised single-line reporting structure, dissolving legacy functional QA and DBA departments.
3. Platform Engineering launches the internal developer portal offering self-service AWS EKS and Kafka provisioning.

---

skill: organization-architect

Global Digital Banking Organization — Fitness Self-Check [ORGARCH-BANK-FIT-001]

Summary

This fitness self-check evaluates the enterprise organization architecture against three critical red-capable domain failure probes: anemic model, cross-context transaction, and duplicate language. All targeted probes pass by design construction. A self-check is supporting evidence, never the authoritative gate. Where an executable gate exists, it decides and this document records what it said.

Detailed Description

Residual Risk

• Temporary transitional friction and anxiety among middle managers whose functional empire boundaries are dissolved. Accepted by David O'Reilly with comprehensive leadership transition coaching.

Traceability

Verification

No validator was supplied, so no command was run.

Open Decisions

None.

Next steps

1. Architecture Guild incorporates organization topology linters into internal engineering management dashboards.
2. People Operations conducts monthly reviews of team cognitive load and inter-squad ticket dependencies.
3. Conduct semi-annual socio-technical health surveys evaluating team autonomy and platform self-service satisfaction.