# Benchmarking analytics performance in banking
A large European retail bank once discovered that 40% of its "active" dashboards had not been opened in over six months, yet the analytics team's internal scorecard showed "100% delivery" against its roadmap. Delivery and impact are not the same thing. This lesson is about telling them apart.
Banks have more data infrastructure than almost any other industry: core banking systems, trading platforms, risk engines, fraud models, regulatory reporting pipelines. But most performance conversations stop at "did we ship the project," not "is the analytics estate healthy."
Healthy means: data arrives on time, models stay accurate, pipelines don't silently break, and the people who are supposed to use insights actually do. Each of those has a measurable proxy. Leaders who can't name their bank's numbers on these four fronts are managing analytics by anecdote.
Before benchmarking anything, know what's flowing through the estate:
Each source has a different refresh expectation. Core banking positions might update daily; payments data flows in near real time; regulatory submissions are periodic (monthly, quarterly). Benchmarking without knowing the expected cadence of the *source* is meaningless.
These are the metrics that determine whether anything built on top of the data can be trusted.
Data quality dimensions (a framework used across the industry, echoed in guidance from the Basel Committee's BCBS 239 principles on risk data aggregation):
Governance metrics:
A worked example. Suppose a bank's loan book has 500,000 active accounts. A data qualitydata qualityThe degree to which data is fit for purpose: accurate, complete, consistent, timely, valid and unique. Poor quality data undermines analytics, reporting and AI.View full definition → audit finds 12,500 records with a missing or stale collateral valuation.
Completeness rate = (500,000 - 12,500) / 500,000 = 97.5%A 97.5% completeness rate sounds high, but if the missing 2.5% concentrates in the commercial real estate book, the risk exposure is far more material than the percentage suggests. Always segment quality metrics by portfolio, not just aggregate.
This is where "are we actually delivering" gets tested.
Banks increasingly report data pipeline SLA (Service Level Agreement) adherence: the % of scheduled data jobs completing within their time window. Industry estimates for mature bank data platforms put target uptime around 99.5% for critical regulatory and risk feeds (estimate, no single public benchmark exists; treat internal targets as institution-specific).
Fraud and credit risk models decay as customer behavior shifts. A common benchmark:
A model untouched for two years, still "in production," is a red flag regardless of past performance, because the population it was trained on no longer matches today's customers.
This is the most neglected benchmark. Common metrics:
A useful gut-check ratio:
Adoption rate = Monthly active users / Total licensed usersIf a bank has 3,000 staff licensed for a BIBITechnologies and processes that turn raw data into actionable insights via reporting, dashboards and analysis, so teams can decide based on facts rather than intuition.View full definition → tool like Tableau or Power BIBITechnologies and processes that turn raw data into actionable insights via reporting, dashboards and analysis, so teams can decide based on facts rather than intuition.View full definition →, but only 450 log in monthly, that's a 15% adoption rate. Compare that to the cost of licenses and the "we deployed self-service analytics" narrative gets a lot less impressive.
Knowledge check
1. A bank's analytics team reports '100% delivery' on its roadmap, yet many dashboards go unused for months. What does this scenario primarily illustrate?
2. According to the lesson, what does it mean for a bank's analytics estate to be 'healthy'?
3. Why does the lesson emphasize that different banking data sources have different refresh expectations before benchmarking performance?
4. Select ALL correct answers about why 'did we ship the project' is an insufficient benchmark for analytics performance in banking.
Select all the correct answers.
5. Select ALL correct answers about the categories of banking data sources described as needing distinct performance tracking.
Select all the correct answers.
A credible analytics health scorecard for a bank's leadership should include, at minimum:
| Category | Example metric | Why it matters |
|---|---|---|
| Data qualityData qualityThe degree to which data is fit for purpose: accurate, complete, consistent, timely, valid and unique. Poor quality data undermines analytics, reporting and AI.View full definition → | Completeness, accuracy % by portfolio | Prevents bad decisions downstream |
| Governance | Lineage coverage, remediation time | Regulatory exposure, audit readiness |
| PipelinePipelineAll active sales opportunities across the stages of the sales process, together with their combined potential value and probability of closing.View full definition → health | SLA adherence % | Are decision-makers working with stale data? |
| Adoption | MAU/licensed users, dashboard shelf-life | Is analytics actually used, or just built? |
None of these substitute for business outcomes (loss reduction, faster approvals), but they are the leading indicators. If pipelinepipelineAll active sales opportunities across the stages of the sales process, together with their combined potential value and probability of closing.View full definition → uptime is poor or adoption is low, the business outcome numbers will eventually suffer too.