Practical considerations for modernizing systems, managing AI-related governance, and weighing observability trade-offs, costs, and operational controls.

The financial services industry worldwide is facing increasing pressure to modernize while maintaining resilience, security, and regulatory discipline. For technology leaders, this requires closer scrutiny of how financial systems are built, monitored, and operated.

Modernization efforts may involve integrating AI into already complex environments without compromising trust, compliance, or operational stability.

With Asia’s diverse regulatory landscape, financial institutions should account for differences across markets rather than assuming a single regional model, as financial-sector rules and digital-finance frameworks vary across jurisdictions.

Three forces driving the shift

All financial services players, including traditional banks, fintech challengers, and insurance firms, need to navigate three key changes:

  1. First, digital experience has become a major competitive factor. Customers increasingly expect reliable, real-time, and personalised interactions across touchpoints. Mobile banking performance, payment reliability, and transaction visibility should therefore be treated as service priorities rather than secondary support issues. Strategy:
    • Review whether latency, failed transactions, and login friction are already being measured consistently across channels
    • Set clear operational thresholds for user-facing performance, especially for payments, onboarding, and authentication journeys
  2. Regulatory and security pressures are intensifying. Financial institutions must operate not only with existing compliance frameworks but also with emerging AI-related governance expectations across the region. Strategy:
    • Map AI-related controls to existing risk, audit, and incident-response processes before expanding production use cases
    • Check whether governance assumptions made in one country are actually transferable to other regional markets
  3. Competition is expanding beyond traditional peers. Fintech firms continue to reshape customer expectations, while large technology players are increasing their presence in financial services. Institutions should plan for a market in which speed, resilience, and operational control all matter. Strategy:
    • Assess whether current delivery processes favor speed at the expense of resilience, or vice versa
    • Revisit third-party dependencies and concentration risks as part of service-design planning

How observability fits in

AI systems depend on the quality and accessibility of the telemetry available to them, and AI-powered observability (henceforth “AI observability” or “observability”*) can support visibility into complex distributed environments. In this context, observability refers to AI observability capabilities used to monitor digital environments and AI-related workloads. Data quality and system visibility are relevant to both automation and operational assurance.

Organizations evaluating observability solutions can also consider trade-offs, including open-source stacks, hybrid models, and in-house approaches, rather than assuming a single tooling path. Open-source observability ecosystems remain active and widely used, which makes independent comparison of cost, architecture, and staffing requirements important during planning. Strategy:

  • Compare commercial and open-source options against actual operational requirements, not category labels
  • Evaluate data-ingestion, retention, and staffing costs before expanding platform scope
  • Avoid duplicative tooling where existing logging, tracing, or monitoring systems already cover the use case

By using observability tools (when implemented effectively) to improve telemetry analysis, enterprises can help teams identify root causes more quickly and reduce operational friction. Outcomes, however, depend on architecture, governance, and how well workflows are maintained over time.

As AI moves from pilots to production use, institutions should focus on whether systems are explainable, auditable, and aligned with regulatory expectations. AI observability can support those efforts, but it is not a substitute for governance, documentation, testing, or model-risk controls. Strategy:

  • Treat observability as one operational layer within a broader control framework
  • Define measurable targets such as transaction latency, authentication success rates, and end-to-end service availability
  • Require teams to show how monitoring data supports auditability and incident review, not just troubleshooting

Engineering-led innovation

Many financial services organizations are increasing automation through CI/CD practices, automated infrastructure provisioning, and automated incident-response processes. As automation matures, governance, change control, and operational oversight become more important, not less.

High-impact outages can be expensive and can affect both customer trust and core operations. Before investing further in AI observability platforms, organizations should weigh platform, storage, ingestion, and specialist staffing costs against expected operational benefits, especially where tool proliferation is already an issue. Strategy:

  • Check whether new tooling reduces meaningful operational risk or simply adds another layer of complexity
  • Include total cost of ownership, retention policies, and staffing models in procurement reviews
  • Test whether incident escalation paths improve in practice, not only in architecture diagrams

Observability can provide end-to-end visibility across applications, infrastructure, and user experience, which may help teams identify issues earlier and respond more effectively. Its value is strongest when combined with governance, operational discipline, and clear ownership across engineering and risk functions.^

Evaluating observability in practice

In the financial services sector, observability is increasingly treated as part of the broader infrastructure used to manage complexity at scale. Even so, outcomes vary by implementation model, vendor choice, internal capability, and how well the tooling is integrated into operational processes.

Independent evaluations and comparisons, especially those that include open-source options and total-cost-of-ownership analysis, should be part of procurement and planning. In Asia, institutions should also test whether operating models are robust across multiple jurisdictions rather than optimized around a single market.

Observability may provide part of the operational foundation for managing speed, resilience, and control, but only when it is selected and implemented with clear governance, cost discipline, and measurable outcomes.

*Editor’s note: In this article, “observability” refers broadly to system visibility through telemetry such as logs, metrics, and traces. “AI-powered observability” refers to observability tools that use (generative) AI features to assist with querying, analysis, alerting, or incident response, while “AI observability” refers to the same discipline applied specifically to AI systems and workloads. The terms overlap in places depending on context, but they are not interchangeable.

^Treat observability management as a recurring governance decision, not a one-time procurement event — revisit tooling fit, cost structures, and vendor dependencies as AI workloads, regulatory expectations, and internal capabilities evolve.