Skip to content
Global Bank EA Operating Model Transformation – Larkinized
Case Study

Global Bank EA Operating Model Transformation

A top-20 global bank redesigned its EA operating model to unify business, application, and technology architecture under a federated governance structure.

Client Context

A top-20 global bank with operations in forty countries engaged Larkinized to redesign its EA operating model after a decade of federated architecture groups producing inconsistent ARB outcomes. The Chief Architect reported to the CIO with dotted lines into risk and finance. Competing priorities included Basel operational resilience, cloud exit from legacy datacenters, and post-merger integration of a retail banking acquisition.

Challenge

Business, application, and technology architecture lived in separate tools and tribes—Horizzon in corporate, Sparx in markets, spreadsheets in finance. ARB review cycles averaged eleven weeks; duplicate payment hubs and CRM capabilities persisted across regions. Regulators requested clearer critical service maps before the next examination window.

Approach

Larkinized ran a six-week maturity assessment against a federated target operating model, then co-designed governance with regional lead architects. We standardized ARB intake templates, capability-based investment tagging, and a single application fact source synchronized from LeanIX to divisional Sparx repositories. Ninety-day quick wins included a global payment service heatmap and retirement of three redundant customer onboarding applications in one region.

Architecture Decisions

Federated modeling remained in divisions; corporate owned application facts and principles. We mandated architecture decision records for all tier-one investments, adopted API gateway standards for open banking interfaces, and defined escalation when regional exceptions exceeded risk appetite. Transition architectures documented interim states for core banking renewal without big-bang cutover.

Outcomes

ARB cycle time dropped forty percent within twelve months. Application rationalization identified twelve million dollars in annual run-rate savings from decommissioned duplicates. EA maturity advanced from Level 2 to Level 4 on an internal scorecard within eighteen months, with examiners citing improved service traceability in the subsequent review.

Lessons Learned

Federated EA succeeds when corporate governs facts and standards while divisions own design delivery—not when every region reinvents catalogs. Anchor sponsorship to examination and cost outcomes executives already track. Quarterly outcome reviews matter more than framework rebranding.

Need Expert Guidance?

Larkinized LLC helps organizations design, govern, and execute enterprise architecture programs that deliver measurable business outcomes.

Scroll to Top
Scroll to Top