Finding the hidden driver behind a declining resolution-time KPI
An outsourced customer-service operation delivering support for a large international brand across 12 markets, under strict IT and data-governance rules. All reporting ran on Excel and Access data feeding a Power BI semantic model, and no data could leave the environment.
- 12
- markets affected
- 2 months
- decline window
- 8
- driver KPIs tracked
- 52 wks
- rolling correlation window
The challenge
The operation's core efficiency KPI, Case Resolution Time (CRT%), is tracked separately for escalated and non-escalated cases. It had slid for two months in a row, unevenly. The Premium segment was down in about four markets but still in a neutral band, below the bonus threshold and not yet in penalty territory. The Standard segment was down in roughly eight markets and had fallen deep into penalty territory. Leadership needed to know which of dozens of tracked metrics were actually driving the decline before committing resources to a fix.
What I built
A diagnostic dashboard in Power BI, connected to the operation's Fabric-based semantic model. Its core is a rolling 52-week correlation engine that compares CRT% against about eight candidate driver KPIs, weighted by case volume per market so that noisy low-volume markets cannot drown out the big ones. The output is a matrix with driver KPIs on one axis and market and segment on the other, colored as a heatmap. Behind each cell, a DAX measure returns more than a coefficient. It returns a plain-language verdict: "No effective correlation", "Watch" or "Critical: urgent action". A non-technical manager can read the matrix in seconds. Slicers for time, market, line of business and segment let each manager drill into their own scope.
The outcome
Instead of cross-referencing dozens of KPIs by hand, market by market, managers saw a short list of driver and market combinations marked Critical. A wide, ambiguous investigation became a prioritized action list, and this dashboard became the entry point for the root-cause work in the second case.