How do I explain data ROI to my board?

Boards don't respond to engineering metrics. Story points, deployment frequency, dashboards shipped, model accuracy, none of it lands. What lands is capital allocation language: cost, return, ratio, sunset, reinvestment.

The job isn't to dumb the data function down. The job is to translate it into the same instrument the board uses for every other investment.

The translation

• "We shipped 14 dashboards" becomes "We displaced €240K of manual reconciliation work."
• "Adoption is up 30%" becomes "Three products moved above a 3.0 Portfolio ROI Ratio."
• "The team is at capacity" becomes "CDSI is at 7.8, capacity drain is the bottleneck, not headcount."
• "We need more engineers" becomes "Sunsetting two products with sub-1.0 ratios frees the capacity."

The three numbers a board actually uses

Portfolio ROI Ratio (per product)

FTE Debt displaced ÷ PCU-V. This is the data function's equivalent of a P/E ratio. Boards understand it instantly because the structure is identical to how they evaluate any other line of investment.

FTE Debt across the business

The total euros lost to data friction, broken down by business unit. This number tells the board what the data function is being asked to fix, and what's at stake if it isn't.

CDSI on the team

A single number that tells the board whether the team's capacity is going to planned work or to firefighting. A high CDSI is a leading indicator of attrition, missed commitments, and the next major incident.

The narrative arc

Open with the FTE Debt number (the problem). Show Portfolio ROI Ratios for the top 5 products (the assets). End with the CDSI trend (the constraint). Make the ask in capital terms: "Reinvest the capacity freed by sunsetting these two products into the three with ratios above 3.0."

This is the same shape as a CFO's quarterly capital review. That's the point.

• → How to measure data team ROI
• → What is Impact Operations?
• → What is PCU-V?