How do I measure data team ROI?
Measure three things: the cost the business pays for data friction (FTE Debt), the true monthly carrying cost of each data product (PCU-V), and where team capacity actually went (CDSI). The ratio of FTE Debt displaced to PCU-V is a Portfolio ROI Ratio a CFO can evaluate.
Most attempts to measure data team ROI fail for the same reason: they measure what the team produces (dashboards, pipelines, models) rather than what those outputs return to the business.
A CFO can't approve or defend a budget based on "we shipped 14 dashboards last quarter." They can act on "those dashboards eliminated €240K of manual reconciliation work."
The three-metric framework
1. FTE Debt, the business-side return
Measures the cost to your business when data products don't work the way people actually work. Calculated as hours lost to workarounds × fully-loaded hourly cost.
This is the numerator of your ROI ratio. A data product that eliminates €50K/month in FTE Debt while costing €8K/month to sustain has a Portfolio ROI Ratio of 6.25, a number a CFO can evaluate.
2. PCU-V, the product carrying cost
The true monthly cost of sustaining each data product: infrastructure + incident response + support load + change requests. Most data budgets only account for infrastructure. PCU-V surfaces the full carrying cost, typically 2-4× the infrastructure number once human time is included.
3. CDSI, the capacity allocation
Where the team's capacity actually went, vs. the plan. A team with CDSI above 8 is spending most of its capacity on unplanned work. CDSI explains why ROI is low even when the team is busy: they're busy on the wrong things.
The Portfolio ROI Ratio
For each data product:
Portfolio ROI Ratio = Value generated ÷ PCU-V
Value is measured as FTE Debt displaced, decision linkage (decisions enabled × financial weight), or cost avoidance (incidents prevented × historical cost). A ratio below 1.0 means the product costs more to sustain than it returns. Sunset candidate, regardless of usage.
What to do with the numbers
- Ratio above 3.0, invest further.
- Ratio between 1.0 and 3.0, monitor.
- Ratio below 1.0, sunset or redesign.
The CEO and CFO use these ratios to make portfolio decisions, the same way a fund manager decides where to redeploy capital.
Common mistakes
Measuring velocity instead of value. Story points and deployment frequency are engineering metrics, not business metrics.
Using adoption as a proxy for ROI. A dashboard used 1,000 times that produces no decisions is a cost, not a return.
Ignoring the business side. ROI calculated only on the data team's budget misses half the equation, the FTE Debt the business is paying because the products don't work as needed.
Related reading
Next Step
Want this measured for your portfolio?
A 30-minute working call maps where capacity is leaking and what it would take to recover it. No slides.
Pressure-Test your data org