Productivity and process training often produce impressive time savings. The temptation is to multiply the hours saved by an hourly cost and call the result a financial benefit. But time saved is not the same as cash saved.

A typical example

A team handles 100,000 transactions a year. After training, the average handling time drops from 12 to 10 minutes.

  • Time recovered: 2 minutes × 100,000 ÷ 60 ≈ 3,333 hours
  • At $30 per hour: 3,333 × $30 ≈ $99,990

It looks like the training created almost $100,000 of value. The trainer's question should be:

What did the organisation actually do with the time that was saved?

Three very different outcomes

1. Reduced overtime

The organisation actually spends less. This can create a relatively direct financial benefit — and it shows up in the payroll data.

2. Additional output

Employees use the time to process more customers or more work. The value may come from additional revenue or margin, not from the wage rate.

3. Capacity creation

Employees absorb increased demand without the business hiring more people. The value may be based on avoided staffing cost.

If none of these happened — the time simply disappeared into the working day — the honest financial benefit may be close to zero, however real the improvement felt.

Cost saving vs cost avoidance

The same discipline applies to costs:

  • Cost saving — actual expenditure decreases. Annual contractor cost falls from $200,000 to $150,000: a $50,000 saving.
  • Cost avoidance — the organisation prevents an expected future cost. Expected remediation of $100,000 becomes an actual $60,000: a $40,000 avoided cost.

Both are legitimate, but they are not the same thing, and executives will expect you to label them correctly.

A simple conversion checklist

  • Name the business change (what is measurably different?).
  • Choose the conversion method — revenue, margin, avoided cost or redirected capacity.
  • Confirm the data source that proves it happened.
  • Apply attribution before calculating ROI.

Convert carefully, and your ROI numbers will survive the conversation they were built for.