How much is your data team's friction actually costing you?
Most of what you pay your data team is invisibly paid again by the rest of the business: hours lost to broken or misfit data products. That cost is FTE Debt — hours lost to workarounds × fully-loaded hourly cost — and it's the largest invisible line item on most data portfolios.
FTE Debt is the ongoing cost to your business caused by data products that don't fit how people actually work, measured in euros per month.
The formula
FTE Debt = Hours lost to workarounds × Fully-loaded hourly cost
Example: 30 people losing 35% of their time to data friction, at an average fully-loaded cost of €85,000 per year:
30 × 35% × €85,000 = €892,500 per year.
Most of that cost is invisible on the P&L because it's distributed across payroll rather than appearing as a line item.
What counts as FTE Debt
- Hours spent manually reconciling data in Excel because dashboards aren't trusted.
- Time lost searching for numbers that should be in one place.
- Management time spent resolving conflicting figures in meetings.
- Effort spent QA-ing reports that should be reliable by design.
- Manual work that exists because a data product was built for the team's convenience, not the user's workflow.
What does NOT count
- Time spent on legitimate analysis and decision-making.
- Productive waiting (dependency on external systems).
- One-off tasks with a known end date.
Why FTE Debt is hard to see
Unlike cloud costs or headcount, FTE Debt doesn't appear on a single invoice. It's distributed across every department, embedded inside "normal" working hours. A VP of Marketing spending 10 hours a week validating a dashboard isn't filing a support ticket, they're just doing their job, less effectively than they should be.
This is why most CFOs significantly underestimate the real cost of a data function. The team's budget is visible. The cost the team creates for the rest of the business is not.
How to measure it
- Interview 2-3 business unit leaders. Ask: "How many hours per week does your team spend working around data that isn't right?"
- Multiply by fully-loaded hourly cost (salary + benefits + tools + overhead ÷ annual hours).
- Annualise. The number is almost always larger than expected.
First-pass estimates are Low confidence, that's fine and by design. The goal is to make the invisible visible, not to produce an audit-grade figure on day one.
FTE Debt vs. technical debt
Technical debt is the cost of shortcuts taken in engineering. FTE Debt is the cost of those shortcuts (and other product failures) paid by the rest of the business. They are related but measured differently: technical debt is an engineering estimate, FTE Debt is a payroll calculation.
Who uses this metric
FTE Debt is one of three metrics in the Impact Operations system, alongside PCU-V and CDSI. Together they give a CEO and CFO a portfolio-level financial view of data investment.
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