Analytics as a Cost Center — Ergest Xheblati

Summary

Xheblati reframes the purpose of analytics: it isn’t to answer questions, it’s to improve operational performance. The core analogy is induced demand — building more dashboards is like widening a highway. You don’t reduce traffic, you create more of it. Two incorrect assumptions drive the vicious cycle:

The need is answering questions. Teams treat analytics as a question-answering service, which creates unbounded demand. Every answer spawns three new questions. The backlog never shrinks.
Stakeholders know what to ask. They don’t. Without analytical fluency, stakeholders generate increasingly exotic questions that consume capacity without improving decisions.

The result: more data capacity leads to more exotic questions leads to more cost leads to “what’s the ROI of the data team?” — which is the cost-center death spiral.

Mental Model: Induced Demand for Data

Just as adding highway lanes induces more driving (not less congestion), adding dashboard capacity induces more requests (not better decisions). The fix isn’t more supply — it’s reframing the service around operational outcomes, not question throughput.

This connects directly to 06-reference/concepts/analytics-as-craft — treating analytics as a craft means orienting around judgment and impact, not ticket velocity. Xheblati’s broader pattern-thinking approach shows up in 06-reference/2026-04-04-sql-patterns-xheblati, where he applies the same structured reasoning to SQL itself.

The cost-center trap is the organizational symptom described in 06-reference/2026-04-03-missing-analytics-executive — when analytics lacks executive-level sponsorship, it defaults to service mode and gets evaluated on throughput rather than strategic value. This is relevant to how 01-projects/phdata/index positions its analytics offerings: leading with operational improvement rather than “we’ll answer your questions.”