Data Product · Analytics
Insurance Analytics Platform
Cut ad-hoc reporting requests by 40% across three teams by getting everyone to agree on eight KPI definitions first.
- My role
- Data product owner
- Timeframe
- 2024 – 2025
- Skills shown
- KPI definition · Stakeholder alignment · Self-serve analytics
The problem
The operations team lived on ad-hoc data pulls. Every question — “how’s claims throughput this week?”, “where’s churn risk concentrated?” — turned into a manual data request and a one-off chart. Analysts were a bottleneck, decisions lagged the data, and nobody agreed on what the numbers even meant.
How I approached it
I treated this as a data product, where the real deliverable wasn’t a chart — it was a shared definition of truth.
- KPI framework first. I worked with stakeholders to define 8 operational KPIs — claims throughput, risk exposure, churn signal, and more — with explicit formulas. Agreeing on definitions was 80% of the value.
- Self-serve over bespoke. Instead of answering questions one by one, I delivered a self-serve Power BI dashboard that let the team answer their own, which emptied the request queue.
- Unstructured signal, too. I added sentiment analysis across 500+ free-text records to surface operational risk signals that the structured fields missed.
Outcome
- 40% reduction in ad-hoc reporting requests — analysts got their time back.
- 8 KPIs with agreed definitions became the team’s shared operating language.
- Real-time risk signals surfaced from text that previously went unread.
What I learned
The dashboard was the easy part. The durable win was forcing a definition for each metric — once “churn signal” meant one specific thing, every downstream conversation got faster. Data products succeed on alignment before visualization.