Six Sigma for Small Business: What's Actually Worth Stealing

Six Sigma made Motorola and GE famous. It also made small business owners roll their eyes.

Black belts. Green belts. DMAIC project charters. Statistical process control. Process capability indices. Most of it is overkill for a 20-person company trying to get through the week without the owner being pulled into every second decision.

But buried underneath all that corporate machinery are a few techniques that work beautifully in a small business. You just have to know which bits to steal and which to leave behind.

That's what this article is about. The honest, stripped-down version of Six Sigma that actually helps a $1-15 million business reduce errors, tighten up quality, and stop the same mistakes from happening on repeat.

No certifications required.

What Six Sigma actually is (in plain English)

Six Sigma is a structured approach to reducing errors and variation in a process.

That's it.

Forget the statistics for a moment. Forget the belts. The core philosophy is simple: measure what's going wrong, find the cause, fix the process, measure again. Repeat until the result is consistent.

It was developed at Motorola in the 1980s and made famous by Jack Welch at GE in the 90s. Both were massive manufacturing businesses with thousands of repeatable processes. They needed defect rates measured in parts per million.

Your business is not Motorola.

But "measure, find the cause, fix the process, measure again" works at any size. That's the philosophy worth keeping.

What's NOT worth copying for small business

Let me get the "leave it behind" list out of the way first. If you've read about Six Sigma and been put off by the complexity, here's what you can safely ignore.

• Black belt and green belt certifications. Certification programs take weeks or months and cost thousands. For a small business, you don't need the title. You need the thinking.
• Formal DMAIC project charters. DMAIC stands for Define, Measure, Analyse, Improve, Control. It's a great framework. The formal project charter version (signed off by a steering committee, tracked in a stage-gated process) is overkill.
• Statistical software and process capability indices. Cp, Cpk, Six Sigma level calculations. Useful when you're making a million widgets. Mostly irrelevant when you're running 50 client jobs a week.
• Dedicated Six Sigma roles and departments. Large corporates build quality departments around Six Sigma. Small businesses don't have that luxury or that need.

In SYSTEMology, I put it this way. Most small business owners try to apply enterprise frameworks and find "too much bureaucracy and rigidity." The ideas were built for a different size. When you try to bolt them on directly, the team ignores them and the project quietly dies.

So strip it back. Here's what works.

The 4 Six Sigma techniques that ARE worth stealing

These are the bits that translate cleanly to a small business. No certifications. No software. No consultants. Just clearer thinking applied to problems you already have.

1. Define the problem precisely

Most business owners describe problems in vague terms. "Customer satisfaction is down." "Delivery is slow." "We're losing deals."

Vague problems lead to vague fixes.

Six Sigma insists on precision. Instead of "customer satisfaction is low," you write: "35% of support tickets take more than 48 hours to first response, and NPS for those clients drops by 18 points."

Now you have something you can actually fix. You know what's broken, who's affected, and how you'll know when it's better.

This one change, by itself, transforms how your team talks about problems. Try it for one week.

2. Measure before you fix

Most business owners skip the measurement step and go straight to the fix. Then when the fix doesn't work, they can't tell why.

Baseline data matters. If you don't know where you started, you can't tell if you've improved. You can't tell if the fix worked, partially worked, or made things worse.

In a small business, measurement doesn't need to be complicated. Count the occurrences. Track the time. Log the complaints. Whatever it is, get a simple count before you change anything.

Then change one thing. Measure again. Compare.

That's it. That's how you tell if your improvement actually improved.

3. Find root causes with 5 Whys

This is my favourite one. Dead simple, works brilliantly, requires zero training.

When something goes wrong, ask "why" five times. Don't stop at the first answer. Keep going until you hit something structural.

Here's an example:

A client invoice went out late. Why? Because the accounts person couldn't find the billing info. Why? Because the project manager hadn't uploaded it. Why? Because they didn't know it was their job. Why? Because onboarding doesn't cover it. Why? Because we never documented the handover between sales and operations.

Look at that last answer. The real fix isn't "remind the project manager." The real fix is "document the sales-to-ops handover." If you'd stopped at the first "why," you'd have fixed a symptom, not the problem.

5 Whys is Six Sigma thinking at its cleanest. Use it on every recurring problem.

4. Control for variation

Once you've fixed a process, you need it to stay fixed.

This is the "control" part of DMAIC. In a corporate Six Sigma program, it involves statistical process control charts. In a small business, it's much simpler.

Make the working version the standard. Document it. Train to it. Put it somewhere the whole team can find it. When a new person joins, they learn the standard version, not the old broken one.

This is where systemHUB does its best work. It's the repository where your "this is how we do this" documents live, so the fix sticks.

Without a controlled version, your improvement decays. Six months later you're solving the same problem again. That's exhausting and expensive.

The small business version of DMAIC

Now put it all together. Instead of running a formal Six Sigma project, just ask these five questions whenever a problem hits.

This is Six Sigma thinking, stripped to the essentials. A 20-person business can run this on a whiteboard in 45 minutes. No consultants.

A real business using this thinking

Luke Davies runs Davies Construction, a custom home building company in New Zealand. Custom home building is exactly the kind of work where Six Sigma thinking earns its keep. Huge number of variables per project. Plenty of places for defects to creep in. And a customer base that measures quality in every square inch of the finished product.

When Luke first read SYSTEMology, he was trapped in the business. Every project, every variation, every client issue ran through him. The business couldn't scale because it was entirely dependent on his personal capacity. Classic owner's trap.

Here's what he did. He started documenting every stage of his design-and-build workflow. From the initial client meeting to handing over the keys. Each stage became a documented system. Each system defined what good looked like and what the process was to get there.

This is Six Sigma thinking without the name. Defining the work precisely. Measuring where things were going wrong. Finding root causes. Controlling for variation by making the standard version the only version the team uses.

The result? Luke extracted himself from day-to-day project management. His team delivers projects consistently and efficiently following the documented systems. The business is more scalable and profitable. Luke has his time back to focus on sales and growth.

Rework is the hidden cost in construction. Fix something twice and your margin disappears. Documented systems reduce rework. Reduced rework protects margin. Protected margin lets you grow.

 

Luke didn't run a formal Six Sigma project. He didn't earn a black belt. He applied the thinking in a way that worked for a custom home builder.

That's the point.

Where Six Sigma fits in your overall approach

Six Sigma is one tool in a broader toolkit. It works best when you use it in the right order.

First, find your bottleneck. That's where theory of constraints comes in. Until you know where flow breaks down, every other improvement is aimed at the wrong target.

Second, remove waste at the bottleneck. That's the job of Lean Thinking. Strip out the non-value-adding steps before you try to standardise what remains.

Third, apply Six Sigma. Attack variation in what's left. Get the process consistent so quality stops being a gamble.

Fourth, use Kaizen to keep it all improving. Small daily improvements driven by the team. Culture, not a program.

I wrote a whole piece on how to combine six sigma lean theory of constraints in the right sequence. If you're serious about process improvement, read that one next.

For a broader overview of the different schools of thought, have a look at business improvement methods. It compares Six Sigma, Lean, TOC and a few others at a high level.

The trap to avoid

There's one way Six Sigma can hurt a small business.

It's when you start obsessing over variation in things customers don't notice.

Six Sigma purists can spend weeks tightening the consistency of a process that doesn't affect the customer's experience. Beautifully consistent. Utterly irrelevant.

A quick example. A business I saw once spent months standardising the format of its internal meeting notes. Consistent headers. Consistent font. Consistent structure. The team hated it. The customer never saw any of it. The effort was real. The value was zero.

The small business version of Six Sigma stays ruthlessly focused on customer-impacting quality. Ask one question before you apply the technique: "Does this variation affect what the customer experiences?"

If yes, fix it. If no, leave it.

The test is simple. The discipline is hard.

The bottom line

Six Sigma works in small business when you strip the corporate machinery and keep the philosophy.

Define the problem precisely.
Measure before you fix.
Find the root cause with 5 Whys.
Control for variation by making the fix the standard.

No belts. No certifications. No statistical software. Just clearer thinking applied to problems that are already costing you money.

And remember: Six Sigma is a quality tool. Use it after you've found your bottleneck (TOC) and removed waste (Lean). Pair it with Kaizen as the cultural habit of continuous improvement.

For the foundational piece on what a documented system actually looks like, what is a business system is a good place to start.

Simple beats perfect. Always.

Ready to put Six Sigma thinking to work without the corporate machinery? systemHUB gives you a single place to document your systems so the fix actually sticks. It comes loaded with 100+ templates to get you started. Try it free.