Back to Glossary

Entry · Business

Six Sigma

Six Sigma is a disciplined method for reducing errors and variation in a process until defects become rare. It uses measured data rather than opinion to find the causes of poor quality, and its name comes from a statistical target of no more than about 3.4 defects per million chances to get something wrong.

Businesses apply it to anything repeatable, from a production line to an invoice approval process.

What it means

At its core Six Sigma treats a business process as something measurable: you define what the customer counts as a defect, count how often it happens, and work backwards to the causes. The discipline grew out of manufacturing in the 1980s but is now used just as often in finance, logistics and customer service teams.

The usual project structure is DMAIC, which stands for define, measure, analyse, improve and control. Each stage has a gate, so a team cannot jump to a fix before it has evidence about what is actually driving the problem.

The control stage matters most to finance, because it is what stops the old behaviour creeping back once the project team disbands. The business case is almost always about the cost of poor quality: scrap, rework, refunds, late delivery penalties and the staff time spent firefighting.

Because those costs sit across many different budget lines, they are easy to underestimate until someone adds them up. A single project that removes a recurring defect can pay for itself within a quarter.

Practitioners are graded by belt: green belts run improvement work alongside their day job, black belts lead larger projects full time, and master black belts coach everyone else. Many companies now blend the method with lean, which attacks waste and waiting time rather than variation, and the combined approach is usually called Lean Six Sigma.

The main nuance is that Six Sigma is deliberately narrow, because it improves an existing process rather than inventing a better one. If the process itself is the wrong answer, tightening its variation only makes the company more precisely wrong, which is why the define stage should test whether the process needs to exist at all.

In practice

Real-world examples.

1

Example

A packaging plant finds that 3% of cartons are rejected at the sealing stage. A Six Sigma team measures machine temperature across every shift, discovers that one line runs cold on night shifts, and reduces rejects to 0.4% with a single control change.

2

Example

A finance shared service centre applies DMAIC to supplier payments after discovering that 11% of invoices need manual correction. The analyse stage traces most errors to three suppliers sending non standard purchase order references, and a template change removes the bulk of the rework.

3

Example

A private hospital group uses Six Sigma to cut the variation in theatre turnaround times. Standardising the cleaning and setup sequence takes the average from 41 minutes to 28 minutes and lets the group fit two extra procedures into each operating day.

Think of it

Six Sigma is using data and statistics to make processes nearly perfect-eliminating defects systematically.

Formula

Calculation

Defects per million opportunities (DPMO) = (number of defects / (units processed x opportunities for a defect per unit)) x 1,000,000 A loan processing team handles 20,000 applications in a month, and each application has 5 places where an error can occur, giving 20,000 x 5 = 100,000 opportunities. Quality checks find 400 errors, so DPMO = (400 / 100,000) x 1,000,000 = 4,000 defects per million opportunities. Each error costs an average of $75 in rework and customer contact, so the monthly cost of poor quality is 400 x $75 = $30,000, or $360,000 a year. After a project cuts errors to 100 a month, DPMO falls to (100 / 100,000) x 1,000,000 = 1,000, the monthly cost drops to 100 x $75 = $7,500, and the annual saving is ($30,000 - $7,500) x 12 = $270,000.

Case study

Seen in the real world.

The following is an illustrative and entirely fictional example. Braycourt Instruments, an invented maker of laboratory scales, was losing roughly $1.4 million a year to warranty returns and could not work out why. Its engineers each had a favourite theory, and every meeting ended with a new theory rather than a decision.

The fictional management team ran a Six Sigma project instead of another debate. The measure stage showed that 68% of returns came from one product family, and the analyse stage narrowed the cause to a supplier whose load cells varied outside the tolerance Braycourt had assumed. Tightening the incoming inspection and renegotiating the specification cut returns from that family by three quarters within two quarters.

The point of the illustration is that the finance benefit was visible long before the quality data was: warranty provision fell, gross margin rose by roughly two percentage points, and the improvement stuck because the control stage put a monthly measure in front of the operations director.

Watch out

Common mistakes.

  • Treating Six Sigma as a training exercise and counting the number of belts trained rather than the money saved or the defects removed.
  • Skipping the measure stage and jumping to a solution someone already had in mind, which usually fixes a symptom and leaves the cause in place.
  • Claiming savings that never reach the profit and loss account, such as counting hours freed up as cash when nobody reduced headcount or increased output.

Questions

People also ask.

Does Six Sigma only work in factories?

No, it works anywhere a process repeats often enough to measure, which includes billing, recruitment, claims handling and customer onboarding.

Is the 3.4 defects per million figure a realistic target for every process?

Rarely, and most businesses gain far more from moving a poor process to three or four sigma than from chasing the theoretical limit on a process that is already good.

How should finance track the return on a Six Sigma project?

Agree the baseline cost of poor quality with the project sponsor before work starts, then verify the saving in the budget line where it should appear rather than in the project team's own report.

From the founder's library

Accounting Fundamentals: A Non-Finance Manager's Guide to Finance and Accounting, by Shihan Sheriff

Take it further with the book.

Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.

US$2.24US$2.99

25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.

View the book and save 25%
Last updated · September 8, 2026
Browse all terms →

Disclaimer

The information provided in this finance dictionary is for educational and informational purposes only. It should not be construed as financial, investment, legal, or tax advice. Always consult with a qualified professional before making any financial decisions. Money Master HQ makes no representations or warranties about the accuracy, completeness, or suitability of this information. Use of this content is at your own risk.