Building a Business Case for a Lean Six Sigma Programme
Lean Six Sigma (LSS) has a proven track record in manufacturing, financial services, healthcare, and public administration -- but every programme still needs executive approval, and executives ask the same questions every time. What will it cost? What will we get back? How long will it take? What does success look like? The organisations that answer these questions rigorously get funded. The ones that answer them vaguely do not.
A well-constructed business case for an LSS programme does not rely on enthusiasm or benchmarks from other industries. It is grounded in your organisation's own data, structured to show a credible path from current-state costs to future-state savings, and governed by a model that makes results trackable over time.
Start With the Cost of Poor Quality
The cost of poor quality (COPQ) is the foundation of any credible LSS business case. COPQ quantifies what your organisation is spending on things that would be unnecessary if processes worked correctly the first time. It falls into four categories: internal failure costs (rework, scrap, defects caught before they reach the customer), external failure costs (warranty claims, customer complaints, returns, regulatory penalties), appraisal costs (inspection, auditing, testing to find defects), and prevention costs (training, process design, error-proofing).
Most organisations dramatically underestimate their COPQ because they only count the costs that appear in obvious line items -- scrap and warranty claims are visible; the management time spent resolving complaints, the customer relationships damaged by errors, and the capacity consumed by rework are typically invisible. A thorough COPQ assessment usually surfaces a figure larger than leadership expected, which is exactly what makes it persuasive.
Industry benchmarks suggest that COPQ in organisations without structured quality improvement programmes typically runs between 5 and 20 percent of revenue. Even a conservative assumption of 8 percent of revenue in a $200-million organisation implies $16 million per year in recoverable waste -- a compelling starting point for any executive conversation.
Projecting Programme Savings
Once you have established your COPQ baseline, you can build a credible savings projection. LSS programmes in well-run implementations typically recover 1 to 3 percent of revenue in Year 1, growing as the programme matures and additional projects are completed. The savings attribution should be specific: project by project, with a description of the process addressed, the defect or waste eliminated, and the financial impact of the improvement.
Avoid aggregated or speculative savings projections. Executives who approve LSS programmes and later see vague claims like "improved efficiency across the organisation" lose confidence in the programme and its sponsors. The business case should commit to specific, measurable savings that can be tracked in the financial system.
Implementation Costs
A realistic implementation cost estimate covers four categories. Training and certification includes the cost of Green Belt and Black Belt training for the employees who will lead improvement projects -- typically a significant investment per belt, with the number of belts scaled to programme ambition. Facilitation and consulting covers external support for project selection, DMAIC facilitation, and statistical analysis in the early phases. Tools include any software for process mapping, statistical analysis, or project tracking. Time is often the largest and most overlooked cost -- belts typically spend 25 to 50 percent of their time on LSS projects, and that time has an opportunity cost that must be included in the calculation.
ROI Timeline and Tracking
Most LSS programmes deliver a positive return within 12 to 18 months when properly implemented. Year 1 is typically net-negative as training and setup costs precede savings; Year 2 turns positive as completed projects begin delivering benefits; Year 3 and beyond is where the compounding effect of a maturing programme becomes significant.
The business case should specify how savings will be tracked and verified. The gold standard is savings that flow through the P&L -- either as headcount reductions, reduced material consumption, lower warranty claim volumes, or measurable capacity release that enables revenue growth without proportional cost growth. Savings that cannot be traced to the financial system are contested savings, and contested savings erode executive confidence.
Governance Model
Executives approving an LSS programme want to know that someone is accountable for the results. The governance model should specify a programme sponsor at the senior leadership level, a deployment leader responsible for day-to-day programme management, a project selection mechanism (typically a tollgate review aligned to strategic priorities), and a reporting cadence that keeps leadership informed of project status, savings delivered, and programme health.
Without visible governance, LSS programmes drift -- projects stall, belts get pulled onto other priorities, and savings targets quietly disappear. The governance model in the business case is the commitment structure that prevents this.
What the Business Case Must Answer
What is our current cost of poor quality, and how was it calculated?
What specific savings are we committing to in Year 1, Year 2, and Year 3?
What will the programme cost to implement, fully loaded including staff time?
When do we expect to recover our investment, and how will we measure it?
Who is accountable for the programme, and what is the governance structure?
How will we select projects to maximise return on programme investment?
XNM Consulting supports organisations in building the business case for Lean Six Sigma programmes, selecting high-impact projects, and establishing the governance structures that ensure results are delivered and tracked.