Should I reduce my data team size?
Possibly, but not before you measure what each product costs to sustain (PCU-V) and what the business loses if it disappears (FTE Debt). Cutting headcount without a portfolio view usually moves the work to the business rather than eliminating it.
Possibly. But not before you know what the team is actually sustaining, and what the business will lose if that capacity disappears.
Cutting headcount without a portfolio view is the most expensive mistake a CFO can make in a data function. The team looks like a cost center. The work they're quietly absorbing, incidents, support, maintenance, redistributes to the business the moment they leave.
The question to ask first
Before reducing team size, answer:
- What does each data product cost to sustain? (PCU-V)
- What does the business lose if it disappears? (FTE Debt)
A data team of 8 sustaining 40 products has a different headcount conversation than a team of 8 sustaining 12. The number of people is the same. The portfolio picture is completely different.
When reducing makes sense
Reducing team size is defensible when:
- PCU-V analysis shows a significant portion of the portfolio has a Portfolio ROI Ratio below 1.0 (costs more than it returns).
- Those products can be sunset or simplified, freeing the carrying cost that currently justifies the headcount.
- CDSI shows the remaining capacity goes to planned work, not firefighting, meaning the team isn't secretly running a support desk.
When reducing destroys value
Reducing team size is destructive when:
- The team's capacity is consumed by unplanned work (high CDSI). Cutting headcount moves that work to the business, not to zero.
- FTE Debt is already high. The business is already compensating for data gaps with manual work; removing people widens the gap.
- No portfolio audit has been done. You're cutting before you know what you're cutting.
The right sequence
- Run PCU-V on the full portfolio. Identify what each product actually costs to sustain.
- Run FTE Debt by business unit. Identify where the business is already compensating.
- Identify sunset candidates (PCU-V higher than return). Retire those first.
- Measure CDSI. Understand where current capacity actually goes.
- Make the headcount decision with the portfolio in view.
A well-run portfolio reduction often finds that sunsetting 30% of products frees enough capacity to right-size the team naturally, without a layoff.
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