Value Leak 03 · For CEOs and Heads of Data
Your data team has the right tools and is still drowning in tickets
You bought the modern stack. Snowflake, dbt, Looker, a transformation layer, an observability layer. Your engineers are still drowning in tickets. The roadmap keeps slipping.
The leak is not the tools. It is that nobody is defining which business capabilities the tools should produce. The tech team is focused on how data moves. Nobody is defining where it needs to go to create value.
Inside Impact Operations, this is a capacity problem and it has a number: CDSI. Here is how to score it, retire the tools that don't lower it, and shift your team back to Build.
The Diagnosis
Three signals you have this leak
You have a high-performance engine but no steering wheel. The three signals below tell you whether your stack is producing capabilities or just consuming capacity.
Signal 01
Modern stack, medieval throughput
You have Snowflake, dbt, and Looker. Your engineers are still drowning in tickets. The tech stack is great on paper. It speaks the language of architecture, not answers.
Signal 02
Capacity drains into Run, not Build
Most of your team's week is spent keeping existing data products alive: incidents, support, definition disputes. The new capabilities the business asked for keep slipping.
Signal 03
Nobody can defend the next tool purchase
Procurement gets another request. Nobody can prove the previous tool reduced friction. The CFO sees tools added, never retired, and asks the obvious question.
The metric that scores this leak is CDSI (Capacity Drain & Support Index). Healthy range: 4.2–7.2. It runs continuously inside the Impact Operations method.
The Fix
Score capacity, then realign the stack to capabilities
Stop measuring throughput in tickets. Start measuring it in CDSI delta. The fix is three steps, in this order.
Step 01
Measure capacity drain with CDSI
CDSI (Capacity Drain & Support Index) scores how much of your data team's capacity is consumed by Run work versus Build work. Healthy organisations sit between 4.2 and 7.2. Above that, you are paying for a team that cannot ship the roadmap.
Step 02
Shut down the 'Feature Factory' mentality
Realign your tech stack to deliver Business Capabilities instead of architectural milestones. We move from 'We built a pipeline' to 'We enabled a 5% increase in conversion through real-time insights.' The shift is in the language, the roadmap, and the way the team is staffed.
Step 03
Retire tools that don't lower CDSI
Every tool gets a CDSI delta target. If it doesn't move the score, it doesn't stay. That is how a data stack becomes auditable and how 'Capabilities over Tools' becomes a budget conversation, not a culture poster.
Free Download
Capacity Drain (CDSI) Self-Assessment
A 10-question scorecard. Score your team in 10 minutes, see whether you sit inside the healthy 4.2–7.2 band, and get the three highest-impact moves to lower it.
We email the file directly. One-click unsubscribe in every message. No cookies, no tracking pixels.
Related Reading
Go deeper
Methodology FAQs
Essays
Related Value Leak
→ Insight velocity: when your data arrives too late to drive a decisionThe Strategy Stress-Test
Want your CDSI scored?
A 30-minute session. We baseline your CDSI, identify the two tools costing you the most capacity, and sketch the realignment.