Chief Operating Officer Guide: Traditional Financial Services

The Friction Points.

The operational environment for traditional financial services in 2024-2025 is defined by four converging pressure points. These are not merely annoyances; they are systemic threats to profitability and resilience.

1. The Strategic Execution Gap

According to Kearney’s 2025 research, the primary hindrance to growth is no longer strategy, but the "execution gap." While 79% of COOs intend to implement AI solutions in 2025, the infrastructure to support them is often missing. The friction arises from the disconnect between the C-suite's vision and the frontline's reality. In traditional banks, strategy is set in annual cycles, but execution happens in milliseconds. When 86% of COOs are stuck in tactical operations, the bridge between strategy and execution collapses. This leads to "zombie projects"—initiatives that consume capital but fail to deliver value because operational leaders cannot dedicate the time to steer them.

2. The Control Paradox and Cost of Error

Historically, when a risk was identified, the solution was to add a control. Over decades, this has created a calcified layer of manual, duplicative checks. EY research highlights that these manual interventions are now a primary source of operational risk, not a mitigation. In the current high-rate environment, the cost of error is magnified. A manual reconciliation error in a low-rate environment was a nuisance; today, it is a margin killer. The paradox is that by adding more manual controls to satisfy regulators, COOs are inadvertently increasing the surface area for human error and slowing down customer service.

3. The Legacy Technology Anchor

While younger CFOs and digital-native competitors demand API-first agility, the core operations of many insurers and asset managers still rely on mainframes and batch processing. The Everbank COO interview highlights this tension: the market demands real-time data, but the backend speaks COBOL. This creates a "data latency" problem where the HQ lacks real-time insight into local execution. Decisions are made on data that is days or weeks old, rendering the organization reactive rather than proactive. This is further complicated by the talent gap; finding engineers to maintain legacy systems while simultaneously hiring AI specialists is a dual-front war for talent.

4. Regulatory Fragmentation and Regional Drift

Global financial institutions face an increasingly fractured regulatory landscape. As noted by Protiviti’s 2025 Compliance Playbook, while themes like AI and financial crime are universal, the implementation is idiosyncratic. A bank operating in London, New York, and Singapore faces three distinct, often conflicting, sets of requirements for the same digital asset or payment flow. In Europe, DORA mandates strict operational resilience reporting; in the US, the focus shifts to third-party risk management under different frameworks. This fragmentation forces COOs to build redundant compliance teams, driving up costs and preventing a unified global operating model. The lack of a "single view" of risk across geographies is a critical vulnerability.

A Smarter Operating System.

To address these challenges, leading COOs are moving away from static functional models toward dynamic, journey-based operations. This requires a four-phase transformation framework.

Phase 1: Radical Instrumentation (The Digital Twin)

Before you can optimize, you must see. The first step is instrumenting the end-to-end journey, not just the touchpoints.

• The Shift: Move from measuring "departmental SLAs" (e.g., Underwriting took 2 days) to "Customer Journey Time" (e.g., From application to funded account took 9 days).

• The Method: Implement process mining tools that sit on top of legacy logs to visualize the actual flow of work, not the theoretical process map.

• Decision Criteria: If >30% of work is "rework" or "status checks," immediate instrumentation is required.

Phase 2: The "Clean Sheet" Control Redesign

Instead of adding controls to broken processes, effective COOs are using the "Clean Sheet" approach recommended by EY.

• The Framework: Map every regulatory obligation to a specific operational workflow. Ask: "If we designed this process today with current technology, would this control exist?"

• Action: Remove duplicative manual checks. Replace "maker-checker" models with "system-validate-exception" models.

• Target: Reduce manual control volume by 40-60% by shifting to automated preventative controls.

Phase 3: Intelligent Automation & AI Integration

With 79% of COOs planning AI adoption, the focus must be on industrialization, not experimentation.

• The Hierarchy of Automation:

1. RPA (Robotic Process Automation): For structured, repetitive data movement (e.g., copy-pasting from PDF to Mainframe).

2. Intelligent Document Processing (IDP): For semi-structured data (e.g., reading invoices or claims forms).

3. Generative AI: For unstructured synthesis (e.g., summarizing complex compliance mandates or drafting customer responses).

• Best Practice: Do not apply GenAI to a process until it has been standardized (Phase 2). Automating chaos only creates faster chaos.

Phase 4: The Dynamic Change Office

To solve the "Strategic Execution Gap," the Project Management Office (PMO) must evolve into a Value Realization Office (VRO).

• The Shift: Stop tracking "milestones hit" and start tracking "value captured."

• Mechanism: Link every project to a P&L line item. If a transformation initiative claims it will save 20% of effort, the budget for that department should automatically adjust upon completion.

• Governance: Weekly "blocker busting" sessions where the COO unblocks specific cross-functional issues, rather than monthly status updates.

Implementation Guide

Transformation fails not in the design, but in the transition. Here is a practical 12-month roadmap for the COO.

Phase 1: Stabilization & Assessment (Months 1-3)

• Goal: Stop the bleeding and get visibility.

• Key Actions:

• Deploy process mining on one critical journey (e.g., Onboarding).

• Establish the "Value Realization Office" (VRO) structure.

• Freeze all non-essential manual control additions.

• Team: Core Ops Leaders + Data Analyst + External Process Architect.

• Quick Win: Identify and automate the "top 10" manual report generation tasks to free up 5-10% of team capacity immediately.

Phase 2: Optimization & Pilot (Months 3-6)

• Goal: Prove the model works.

• Key Actions:

• Launch the "Clean Sheet" redesign for the pilot journey.

• Select and configure the orchestration/automation platform (Buy vs Build decision).

• Run a "Shadow Ops" pilot: Run the new process parallel to the old one to prove accuracy.

• Pitfall to Avoid: Do not aim for 100% automation. Aim for 80% STP (Straight-Through Processing) and route the complex 20% to expert humans.

Phase 3: Scale & Institutionalize (Months 6-12)

• Goal: Roll out across regions and functions.

• Key Actions:

• Expand the platform to adjacent journeys (e.g., from Onboarding to Servicing).

• Link individual performance metrics to the new process (e.g., reward "first time right" rather than "volume processed").

• Begin legacy decommissioning for systems fully replaced by the wrapper.

• Measurement: Switch executive reporting from "Project Status" to "P&L Impact."

Team Requirements

You do not need an army of consultants. You need a "SWAT team" of:

• Product Owners: Who understand the business deeply.

• Process Engineers: Who understand Lean/Six Sigma.

• Technologists: Who understand API integration.

• Change Agents: Who can manage the cultural fear of displacement.

Regional Intelligence.

Operational success in 2025 requires a nuanced, region-specific strategy. A "one-size-fits-all" global operating model will fail against local regulatory and cultural realities.

North America (US & Canada)

• Regulatory Environment: The focus is on Third-Party Risk and Fair Lending. The OCC and CFPB are aggressive about "junk fees" and the transparency of algorithmic decision-making. Post-election policy shifts may create uncertainty regarding trade and tax, requiring agile scenario planning (PwC).

• Market Maturity: High competition from non-bank fintechs. The consumer expectation is "Amazon-like" speed.

• Tactical Advice: Prioritize speed and efficiency. Implement AI to reduce cost-to-serve. The workforce is generally more receptive to "pay-for-performance" and rapid technology adoption, but retention is a challenge. Use the "Wrapper" strategy to bypass legacy cores quickly.

Europe (UK & EU)

• Regulatory Environment: The most complex globally. DORA (Digital Operational Resilience Act) is the dominant concern, requiring proof of resilience, not just compliance. FiDA and ESG reporting are also top priorities. Data sovereignty (GDPR) restricts where processing can happen.

• Market Maturity: Open Banking is mature; consumers expect seamless third-party integrations.

• Tactical Advice: Prioritize Resilience and Governance. Automation efforts must lead with "auditability." Cultural resistance to rigid hierarchical changes can be higher; focus on "co-creation" with works councils. Operations must be designed to keep data within the EU/UK borders.

Asia-Pacific (APAC)

• Regulatory Environment: Highly fragmented. From the sophisticated, strict regimes of Singapore (MAS) and Australia (APRA) to developing frameworks in Vietnam or Indonesia. Cross-border payment regulations are a specific hurdle (FSB).

• Market Maturity: Mobile-first is the default. In many markets, consumers skipped the "desktop internet" phase. Super-apps (WeChat, Grab) set the UX standard.

• Tactical Advice: Prioritize Flexibility and Mobile Integration. Operations must support digital wallets and QR codes natively. Talent in hubs like Singapore is expensive and scarce; consider distributed operational hubs in emerging markets (e.g., Philippines, India) but ensure strict oversight to manage the "HQ vs. Local" insight gap.

Proof it Works

Navigating the technology landscape requires a neutral, outcome-based evaluation. The market is flooded with vendors promising "AI-in-a-box," but for traditional financial services, the architecture matters more than the algorithm.

Platform vs. Point Solutions

• The Platform Approach (End-to-End): Suites like ServiceNow, Pega, or Appian that layer over legacy systems to orchestrate work.

• Pros: Unified data model, easier governance, single audit trail.

• Cons: High initial cost, longer implementation, risk of vendor lock-in.

• Best For: Core customer journeys (Onboarding, Claims, Lending).

• Point Solutions (Best-of-Breed): Specialized tools for specific problems (e.g., AML screening, Reconciliation, ID Verification).

• Pros: Faster time-to-value, superior specific functionality, lower initial risk.

• Cons: Integration nightmare, "swivel chair" operations for staff, fragmented data.

• Best For: Highly technical, regulated niches (e.g., Sanctions screening).

Build vs. Buy Decision Matrix

In 2025, the default should be Buy and Configure, not Build and Maintain.

• Differentiation Test: Does this process differentiate us in the market?

• Yes (e.g., Proprietary Trading Algorithm): Build internally to protect IP.

• No (e.g., KYB, General Ledger, HR): Buy SaaS. There is no alpha in building a better payroll system.

The "Wrapper" Strategy

For legacy-burdened institutions, the most successful technical approach is often the "Wrapper" or "Hollow Core" strategy.

• Concept: Leave the mainframe (core banking/insurance system) as a dumb ledger. Build a modern orchestration layer (API gateway + Workflow engine) on top.

• Benefit: You get digital agility without the risk of a "big bang" core replacement.

Evaluation Criteria Checklist

When selecting tools, COOs must ask:

1. ** lineage:** Can the tool prove exactly where the data came from for DORA/OCC audits?

2. Interoperability: Does it have pre-built connectors to our specific legacy core (e.g., Fiserv, Guidewire)?

3. Scalability: Can it handle peak volumes (e.g., Black Friday or End-of-Month) without latency?

4. Talent: Is there a marketplace of developers who know this tool, or will we be dependent on the vendor for every change?

Frequently asked questions

How long does it take to see ROI from an operational transformation?

While full transformation is a 12-24 month journey, you should structure the program to deliver self-funding 'quick wins' within 3-4 months. For example, automating manual reporting or reconciling a specific high-volume account usually pays for itself in under 6 months. According to industry benchmarks, a well-executed intelligent automation program typically delivers 3x ROI within the first 12-18 months. If you aren't seeing tangible P&L impact by month 6, the scope is likely too broad or the governance is too weak.

Do we need to replace our legacy core systems to modernize operations?

No, and in most cases, you shouldn't start there. 'Rip and replace' projects have a notoriously high failure rate in financial services. The modern best practice is the 'Hollow Core' or 'Wrapper' strategy: keep the legacy system as a stable ledger of record, but build an orchestration layer (API gateway + workflow automation) on top of it. This allows you to modernize the staff and customer experience immediately while mitigating the risk of core migration, which can be deferred until the outer layer is stable.

How do I manage the talent gap and fear of AI displacement?

Transparency is non-negotiable. Research from Kearney indicates that fear of displacement is a major productivity killer. Address this by reframing AI as 'augmentation' rather than 'replacement.' Show staff that AI will handle the 'robot work' (copy-pasting, data entry) so they can do the 'human work' (complex decision making, client relationships). Create a clear 'upskilling' track: turn your manual claims processors into 'AI Exception Handlers.' This retains tribal knowledge while modernizing the skill set.

How do we handle the conflict between cost cutting and regulatory compliance?

You must break the mental model that 'better compliance = more people.' In reality, manual compliance is expensive and risky. The most cost-effective compliance strategy is automated preventative controls. By embedding rules into the workflow (e.g., the system won't allow the trade to proceed without the document), you reduce the need for expensive 'cleanup' teams and potential fines. Frame your automation investments to the Board not just as 'efficiency' but as 'regulatory risk reduction'—this often unlocks different budget buckets.

Should we build our own AI models or buy off-the-shelf solutions?

For 90% of operational use cases in traditional financial services, you should buy and configure. Building proprietary AI models requires massive data science talent and ongoing maintenance that is rarely a core competency for a bank or insurer. Use established platforms (e.g., Microsoft Copilot, specialized fintech SaaS) for standard tasks like document processing or code generation. Reserve 'building' only for the 10% of use cases that generate true competitive advantage, such as proprietary trading algorithms or unique underwriting risk models.

How do regional regulations like DORA impact our global operating model?

Regulations like DORA (EU) move the goalposts from 'compliance' to 'resilience.' It's no longer enough to have a plan; you must prove you can recover. This means your global operating model cannot just rely on low-cost offshoring if those locations don't meet the resilience standards of the EU regulator. You may need to adopt a 'federated' model where critical data and processes for EU clients remain within the EU (or equivalent jurisdictions) to satisfy sovereignty and resilience requirements, rather than a single global shared service center.

15-25% (Complex Products) → 70-80%

Straight-Through Processing (STP)

For standardized journeys like Retail Account Opening or Simple Claims.

60-65% → 45-50%

Cost-to-Income Ratio

Driven by automation of back-office functions and legacy system rationalization.

18-24 months → 6-9 months

Transformation ROI Timeline

Achieved by focusing on high-volume, low-complexity 'quick wins' first.

60-70% of total controls → <20%

Manual Controls %

Shift to automated, preventative controls embedded in the workflow.