Listen to this framework
The Return on Employee (RoE) Framework
Return on Employee (RoE) Framework
Developed in response to AI business cases that treated headcount reduction as the primary value metric. Applied across mid-market transformation engagements, government capability programmes, and the UN ESCAP AI for Developing Countries Forum (Bangkok, 2026).
AI business cases built around headcount reduction create organisational resistance, undercount actual value, and produce the wrong implementation incentives. Return on Employee measures AI value through the increase in productive capacity per person, a metric that captures what AI actually does in knowledge-work environments without requiring job elimination to show a positive return.
Why headcount reduction is the wrong metric
- It measures AI value by the number of roles eliminated, creating a business case that staff actively resist and leadership is reluctant to publicise.
- It ignores quality improvement, decision speed, error reduction, and the capacity to take on work that was previously uneconomical.
- It requires job eliminations to show a return, which means the business case disappears if the organisation chooses to redeploy people rather than reduce headcount.
- It treats AI as a cost-cutting tool rather than a capacity multiplier, a framing that systematically underestimates the strategic value of AI programmes.
What RoE measures instead
- Hours reclaimed: Manual task time eliminated per person per week × loaded hourly cost × headcount.
- Decision quality lift: Improvement in output accuracy, error rate, or decision correctness × revenue or risk exposure at stake.
- Portfolio capacity increase: Additional clients, projects, or tasks handled without proportionate headcount growth.
- Cognitive bandwidth returned: Hours shifted from routine execution to higher-value analysis, client engagement, or strategic work, quantified by the marginal value of that time.
(Hours freed × loaded hourly cost) + (Decision quality lift × revenue at risk) + (Portfolio capacity increase × margin per unit)
BCG 2023 benchmark: average RoE for knowledge workers with AI = USD 42,000 per employee per year
Application: Build the RoE calculation into the business case before deployment begins. Establish the baseline (current hours per task, current error rate, current portfolio capacity) before the AI system goes live: you cannot calculate improvement without a pre-AI baseline. Present RoE alongside cost metrics in leadership reporting to prevent the business case from collapsing if headcount reduction is not the chosen path.
The free tool scores you. The paid formats put the framework to work on your own programme, with me in the room.
What is Return on Employee (RoE)?
A way of measuring AI value through the increase in productive capacity per person, instead of headcount eliminated. It captures hours reclaimed, decision quality lift, portfolio capacity increase, and cognitive bandwidth returned to higher-value work.
Why not just measure headcount reduction?
Headcount-reduction business cases create resistance staff actively work against, ignore quality and speed improvements, and disappear entirely if the organisation redeploys people rather than cutting roles. RoE stays valid regardless of which path is chosen.
How do you calculate RoE?
(Hours freed × loaded hourly cost) + (decision quality lift × revenue at risk) + (portfolio capacity increase × margin per unit). A pre-AI baseline for hours per task, error rate, and portfolio capacity has to be established before deployment, since you cannot calculate improvement without one.
What is a realistic RoE benchmark?
BCG's 2023 benchmark put average RoE for knowledge workers using AI at roughly USD 42,000 per employee per year. Treat that as a reference point, not a guarantee, since it depends on the baseline and the tasks involved.
I built RoE after sitting through one too many AI pitches where the business case was really a headcount case wearing a technology costume, and watching staff in the room figure that out in real time. People aren't stupid. They know when the slide is really about them. Measuring hours reclaimed and capacity returned instead of jobs cut isn't softer accounting, it's more honest accounting, and it's also the version people don't quietly sabotage. Build a case people want to see succeed.
