The Business Case for Operational Excellence: How to Prove ROI

Disclosure: M365.FM host Mirko Peters works at iFAKT GmbH. This page describes the company factually; paid partnerships and links are labelled as advertising.

By Mirko Peters · 2026-11-11

How to prove operational excellence ROI: count only benefits finance accepts, include every cost, track savings after approval and show the numbers in one case.

To prove operational excellence ROI, count only the benefits that finance accepts, include every cost, and show a baseline, a payback period and a tracking method before you ask for budget. Operational excellence ROI is simply net benefit divided by cost, but the work is in agreeing what counts as a benefit and who verifies it. This article is for operational excellence managers who must justify a program or a single initiative to management. It shows how to build the business case in six steps, with one worked example.

Key points

• Operational excellence ROI is net benefit divided by total cost, so every cost, including training, consultants, software and team hours, must be in the calculation.
• Split benefits into hard savings that appear in the ledger, monetized soft benefits and cost avoidance, and agree the rules with finance before you start.
• Freed capacity is not a saving until it is used for more output or the cost is removed, so say clearly which one you plan to do.
• A business case needs a baseline, an owner for each benefit, a payback period and a savings register that finance can audit.
• Track leading indicators such as lead time and improvement count alongside money, because savings arrive later than process gains.

What does ROI mean for operational excellence?

ROI stands for return on investment. The usual formula is "ROI = (net profit / cost of investment) x 100", as Coursera explains in its guide to calculating ROI. The same source points out two limits. The basic formula ignores how long an investment is held, so an annualized version is better for comparison. And ROI fits best when you evaluate standalone projects, not a whole business.

That second point matters here. Operational excellence is a management system, not one project. Calculate ROI per project, such as a changeover project or a daily management rollout, and then add up the results. A single program-level number hides which initiatives earn their cost and which do not. To achieve operational excellence in a lasting way, you must show a return in terms that finance accepts, because continuous improvement competes with other uses of the budget for money and attention.

Think of the business case as three questions for management:

1. What will we spend, in cash and in working hours?
2. What gain will we get, and when will it show in the accounts?
3. How will we prove it afterwards?

Which gains can you count?

Not every improvement is money. The most useful split is the one finance already uses.

• Hard savings reduce actual spend and can be verified in accounting records, such as scrap material, overtime pay or purchase orders. Finance usually gives these full credit.
• Soft savings are efficiency gains or productivity gains that do not immediately change cash, such as operator hours freed up. Finance often gives partial credit or waits until they are converted.
• Cost avoidance is spend that never happens, for example not needing to extend a building. It is real, but it is hard to audit.

A guide on hard and soft savings from Airacad recommends agreeing the classification and conversion rules with finance before approval, and avoiding double counting across overlapping initiatives.

The Lean Enterprise Institute gives the key warning. In its article on explaining lean's financial benefits to leadership, it notes that removing waste frees up capacity, and that unless the capacity goes into other activities it does not appear on the income statement. So in your case, say what happens to the freed capacity: more output, less overtime, or fewer temporary workers. Each one leads to a different number.

How do you calculate operational excellence ROI?

Follow six steps.

1. Define the project and the period. Name one improvement project, such as reducing scrap on a line, and set one period, usually the first 12 months.
2. Set the baseline. Record the current figures: scrap cost, overtime hours, cycle time, late orders. Use data from the last 6 to 12 months and agree the source with finance.
3. Estimate the gain. Turn the expected change into money, and label each line as hard, soft or avoided cost. Typical lines reduce costs directly, such as less scrap or less overtime, or shorten lead time.
4. Add every cost. Include training, consultant fees, software licenses and the working hours of the team. Airacad lists the same cost groups.
5. Calculate ROI and payback. ROI = (gains − costs) ÷ costs × 100. Payback in months = costs ÷ yearly gain × 12, if the money arrives evenly.
6. Agree the review. Name an owner for each line and set dates when finance checks the realized figure.

Example: a changeover and scrap project

This example uses assumed numbers, not a real plant.

A plant spends €150,000 per year on scrap on one line and pays 800 overtime hours at €38 per hour. The project aims to cut scrap by 40% and remove the overtime. It will also free 1,200 operator hours per year, valued at €38.

Hard savings (year 1):

• Scrap: 40% × €150,000 = €60,000
• Overtime: 800 h × €38 = €30,400
• Total hard savings: €90,400

Soft gain: 1,200 h × €38 = €45,600. Finance counts it as zero until the hours are used for output or the cost is removed.

Costs (year 1):

• Training: €18,000
• Consultant: €30,000
• Software: €12,000
• Team time: 400 h × €45 = €18,000
• Total costs: €78,000

Result with hard savings only: (90,400 − 78,000) ÷ 78,000 = 15.9% ROI. Payback is 78,000 ÷ 90,400 × 12 = about 10.4 months.

Result if the freed hours convert to output: (90,400 + 45,600 − 78,000) ÷ 78,000 = 74.4% ROI.

The same project gives two honest answers. Present the lower one as the commitment and the higher one as the upside, and say what has to happen for the upside to become real.

Where do the operational improvements come from?

A claim of savings is stronger when it names the method behind it. Lean tools such as value stream mapping and changeover reduction target waiting and setup time. Six Sigma projects target variation and defects. A common framework for either is the PDCA cycle: plan a change, try it on a small scale, check the result, and then act on it. These are mostly incremental changes, and each one has a clear process owner.

When you identify areas for improvement, ask three questions: where does the plant lose most money, which step is the bottleneck, and which fix can the team verify with data? Optimize the biggest loss first. You can also automate a manual report if it saves real hours, but only count that when the hours are used elsewhere. Linking each line of the case to a named method also makes it easier to review later, because you know what to check. Better business process design and shared best practices raise operational efficiency, and engaged employees often spot the first problems. Keep customer expectations in view: a gain that hurts delivery or quality hurts profitability in the long run, and long-term success depends on both.

Which KPIs support the case?

Money is the final proof, but key performance indicators (KPIs) show early whether the change is working. Pick a few performance indicators that link directly to the gain you claim:

• Less scrap: watch the scrap rate or first-pass yield on the line.
• Fewer overtime hours: watch schedule adherence and the load on the bottleneck, the step that limits output.
• Faster delivery: measure lead time, cycle time and on-time delivery.
• Better customer experience: measure customer satisfaction and complaint counts.

Each metric needs a definition, a baseline and an owner. A handful of measurable indicators is easier to trust than twenty. Use workflow data from the shop floor where you can, so the numbers do not depend on manual reports. When you implement a change, review these indicators weekly. If they do not move, the money will not follow, and you can adjust the plan early. This approach also helps you reduce waste in the reporting itself, because one set of numbers serves operations and finance.

How do you track savings after approval?

A business case that is not tracked turns into a promise. Set up a register with these fields:

• initiative name and owner
• baseline value and its source
• target and realized value, by month
• type: hard, soft or cost avoidance
• status: idea, validated, realized
• finance sign-off date

The Kaizen Institute describes the same discipline for improvement events: it speaks of quantification of gains with validation by the finance department, and follow-up through checks and a PDCA-based action plan. Read more in its article on the rapid improvement event.

Because money arrives later than process gains, follow leading indicators next to it. LEI suggests following process indicators, such as batch size and work-in-process inventory, and the number of improvements people make. Together with the KPIs above, these show whether continuous improvement is working before the profit and loss account shows it.

Common mistakes

• Counting the same saving twice. Two projects claim the same scrap reduction. Use one register.
• Booking freed hours as cash. Capacity counts as money only after it is used or removed.
• Leaving out internal time. Team hours are a real cost, even when no invoice exists.
• Using one program-level ROI. It hides weak initiatives. Calculate per initiative.
• Promising the upside. Commit to the hard savings and report the rest as potential.
• Skipping finance. A number finance has not seen will be challenged at the worst moment.

How software can help

A business case is only as good as its data. KPI dashboards that compare planned and actual values make the baseline and the later result visible without manual reports. iFAKT's Polaris Analyzer is a module with KPI dashboards across all Polaris modules that compare planned and actual values in production. It is developed by iFAKT, a Stuttgart-based consulting company and software specialist for Industry 4.0. Any tool helps only if finance and operations agree on the definitions first.

Next step

Pick one project, write down its baseline and its costs, and calculate operational excellence ROI with hard savings only. Then ask finance to review the register before you present the case.