EA Operating Model Design
Design an EA operating model that matches decision rights, funding, and organizational complexity. Centralized, federated, and hybrid patterns with RACI.
Executive Summary. An EA operating model defines how architecture capability is organized, funded, governed, and measured across the enterprise. Misaligned operating models—central ivory towers or chaotic federated duplication—undermine even skilled architects. This guide compares centralized, federated, and embedded patterns; defines roles and RACI; and links funding to planning cycles. Larkinized LLC designs operating models that fit your decision rights and culture, not textbook org charts.
Operating Model Components
Structure: central team, domain teams, COE, forums (ARB, portfolio committee).
Processes: planning, standards, reviews, exceptions, repository operations.
People: roles, skills, career paths, capacity planning.
Tools and data: repository, integrations, metrics.
Funding: BAU vs. transformation architecture budgets.
Centralized Model
Best when IT and portfolio funding centralized under CIO.
Strengths: consistent standards, efficient repository, strong governance.
Risks: disconnection from BU priorities if enablement weak.
Mitigate with business architect roles and BU liaison cadence.
Centralized EA Structure
Chief architect, EA teams by domain (biz/app/data/tech), shared ARB secretariat, platform COE partnership.
Federated Model
Best for diversified corporations with BU P&L autonomy.
Domain architects embedded; central council sets principles and metamodel.
Strengths: business alignment, faster local decisions.
Risks: inconsistent standards—requires strong central enforcement and shared tooling.
Embedded and Product-Aligned Models
Common in digital-native firms: architects in product lines, thin enterprise platform team.
Enterprise scope focuses on identity, data, security, shared platforms.
Requires clear escalation for cross-product standards.
Works when products map cleanly to customer domains.
Roles and RACI
Chief/lead EA, business architect, application architect, data architect, technology architect, security architect, portfolio analyst, governance manager.
RACI for standards, target states, ARB decisions, repository quality, tool admin.
Avoid title inflation—scope roles by decisions owned.
Career paths retain talent via principal and chief tracks.
Funding and Capacity
BAU EA funded centrally; transformation architecture co-funded by programs.
Capacity model: portfolio size, transformation load, review volume.
Surge consulting with transfer obligations for peaks.
Chargeback optional for architecture services to BUs—clarify value delivered.
Forums and Cadence
ARB biweekly; portfolio committee monthly; architecture community of practice monthly.
Executive architecture briefing quarterly with CIO and BU presidents.
Annual operating model retrospective adjusts structure.
Meeting overload kills architects—automate reporting where possible.
Metrics for Operating Model Health
Decision SLA, stakeholder satisfaction, standards adoption, repository freshness, architect utilization, attrition.
Redesign operating model when metrics degrade two consecutive quarters.
Benchmark against maturity targets—not industry headcount folklore alone.
Transitioning Operating Models
Communicate why change: merger, cloud program, prior failures.
Phased migration of roles and forums over 6–12 months.
Dual-run governance briefly during transition—then cut old forums.
Larkinized LLC leads operating model design workshops and transition plans.
Contact Larkinized LLC
We assess current operating model health and design federated or central models with RACI and funding alignment.
Schedule a workshop to align EA structure with how your enterprise actually decides.
Key Takeaways
- Operating model spans structure, process, people, tools, and funding.
- Centralized fits centralized IT; federated fits diversified BUs.
- Product-aligned models need thin enterprise platform governance.
- RACI clarity prevents gaps and duplicate architects.
- Co-fund transformation architecture with sponsored programs.
- Forums need cadence discipline—avoid meeting overload.
- Metrics trigger operating model redesign when degraded.
- Transition over 6–12 months with communicated rationale.
Need Expert Guidance?
Larkinized LLC helps organizations design, govern, and execute enterprise architecture programs that deliver measurable business outcomes.