Six Sigma process and why it still matters
Motorola created Six Sigma in 1986 to hit 3.4 defects per million. Most firms run at 3 Sigma with 66,807 defects per million. One shift saves 20% in margins.
Six Sigma is about reducing defects through measurement. Not guessing. Not hoping. Measuring. Here’s how we think about continuous process improvement at Tallyfy - and why this decades-old approach matters more than ever in an AI-driven world.
Tallyfy is Process Improvement Made Easy
Summary
- Six Sigma targets 3.4 defects per million opportunities - Bill Smith at Motorola created this in 1986 using statistical measurements to nearly eliminate manufacturing defects. The approach later spread to every kind of business process, not just factory floors
- DMAIC gives you a five-step system for killing defects - Define, Measure, Analyze, Improve, Control. Each step builds on real data instead of gut feelings, and the Control phase is where most organizations stumble because they can’t enforce consistency
- Most organizations sit at 3 Sigma with 66,807 defects per million - Moving just one level to 4 Sigma (6,210 defects) typically drives about 20% annual profit margin growth. The math on even small shifts is staggering
- AI won’t rescue a broken process - it scales the dysfunction - Process definition and standardization come before any AI adoption. Tallyfy tracks controls so your improvements actually stick. See how Tallyfy enforces process controls
Quality problems show up in over 1,500 combined conversations we track with mid-market teams. In a perfect world, every organization would run with zero waste and zero attrition. No friction. No rework. No lost revenue from sloppy handoffs.
That world doesn’t exist. But serious waste reduction and better retention are absolutely possible. That’s where Six Sigma comes in.
Measurement is the first step that leads to control and eventually to improvement. If you cannot measure something, you cannot understand it. If you cannot understand it, you cannot control it. And if you cannot control it, you cannot improve it.
— H. James Harrington (Author & Management Mentor)
Back in 1986, Motorola engineer Bill Smith proposed something bold to CEO Bob Galvin: reduce product defects to just 3.4 per million. That’s not a typo. Per million. The initiative worked so well that Motorola won the Malcolm Baldrige National Quality Award in 1988 and eventually documented over $16 billion in savings. They expanded it beyond manufacturing into every business process they ran, and branded it Six Sigma.
What Six Sigma actually is
Strip away the jargon and Six Sigma is a quality control program built on measurement. When Smith developed it, the goal was simple - fewer manufacturing defects, faster cycle times. Over the decades, it’s morphed into something broader: improving services, reducing waste in operations, tightening up how organizations meet the needs of the people they serve.
Here’s the core idea. Every business process can be measured. And if you can measure it, you can improve it. Six Sigma uses statistical tools to spot where things go wrong, then systematically eliminates those failure points. A process running at Six Sigma level produces fewer than 3.4 defects per million opportunities. That’s near-perfect.
But most organizations aren’t anywhere close. They’re running at 3 Sigma - roughly 66,807 defects per million. That gap between where you are and where you could be? That’s where the money hides.
How DMAIC works in practice
The engine behind Six Sigma is a five-step process called DMAIC. I’ll be honest - the acronym is ugly. But the thinking behind it is solid.
Define. A team - often led by someone with Six Sigma certification - pins down exactly what’s broken. Not “things feel slow” but “step 4 in our onboarding process takes 72 hours when it should take 8.” You outline the specific problem, your goals, and what success looks like.
Measure. You gather hard data on how the process performs right now. What inputs might be causing the problem? How bad is it, precisely? This baseline matters because without it, you’re just guessing whether your fix worked later.
One measurement that doesn’t get enough attention: figuring out your “beat” - the rhythm at which you need to complete work to keep up with demand. Think of it like a metronome for your process. If people need 100 widgets per day and you have 8 hours of production time, you need to finish one widget every 4.8 minutes to stay in sync. Fall behind that beat, and backlogs pile up. Race ahead, and you’re building inventory nobody asked for yet.
Analyze. You isolate every input that could be causing the defect. Test each one. Find the root cause. This is where gut instinct gets replaced by evidence.
Improve. After identifying the problem input, the team builds a plan, implements it, and measures again. Did it work? By how much?
Control. This is the step that breaks most organizations. You create controls and bake them into the process so the defect doesn’t come back. Sounds simple. It’s not.
Why controls fail and what to do about it
Six Sigma can look like magic. It’s not.
It’s hard work. Really hard work. And the part where most organizations fall apart is the Control phase. Nearly 60% of Six Sigma initiatives fail to meet objectives consistently, and the biggest reason is that controls don’t stick.
After watching hundreds of teams try this with large insurance companies working on workflow standardization, lack of control adherence was the recurring theme. One organization with 10 different business units found that without trackable, enforced processes, their compliance and underwriting teams were reinventing the wheel in each department. Inconsistent quality. Missed approvals. The same mistakes repeated across every unit.
This drives me crazy because the fix isn’t complicated. Controls fail when they live in spreadsheets, PDFs, or someone’s head. They succeed when they’re embedded in software that tracks every step, flags missed deadlines, and makes it impossible to skip the process.
That’s one of the reasons we built Tallyfy the way we did. It moves controls from flimsy documents to interactive workflows that ensure things get done on time, consistently, and accurately. Whether it’s a human-intensive process, an internal support workflow, or something that faces the people you serve - Tallyfy tracks and audits it. You get compliance for free.
The real question isn’t whether Six Sigma works. It does. The question is whether your organization can sustain the improvements. And that comes down to tooling.
Benefits that surprise people
Happier teams, not just fewer defects
Most people think Six Sigma is about catching errors. It is. But one of the most surprising outcomes is improved team satisfaction. When you apply the DMAIC approach to internal operations - how payroll works, how vacation time gets calculated, how contracts get approved - you eliminate confusion that frustrates both employees and HR. People know exactly what to expect. They understand how overtime qualifies, how their pay works, how approvals flow. That clarity reduces stress and boosts morale in ways that are hard to quantify but easy to feel. Payroll disputes drop. Approval bottlenecks shrink. The questions people used to fire at HR every Monday morning just stop showing up.
Productivity gains you didn’t expect
Using your staff well is harder than it sounds. Is the problem that you need more people? Or that they need better training? Or that your supply chain is the bottleneck? Six Sigma’s measurement-first approach gives you clarity on what’s really going on instead of guessing.
Here’s something that surprised me when I first looked at this data: in many business processes, only around 10-15% of the total time spent actually adds value from the perspective of the person receiving the output. The rest? Waiting. Handoffs. Approvals sitting in someone’s inbox. Items queued up in batches because “we’ve always done it that way.” The math is brutal, but honest.
Waste that goes deeper than materials
Resources get drained by any work that adds no value.
Waste goes beyond the obvious. It isn’t just overproduction or wasted materials. It includes untapped skills, ideas sitting in someone’s head, unnecessary movement of products, people, and information. A solid process improvement approach helps you dig into why waste happens, cut the output of services or products that aren’t being used, and build controls that trim unnecessary steps.
Market share growth
For every Sigma shift, organizations typically see about 20% profit margin growth annually. Most companies sit around 3 Sigma - 66,807 defects per million. Even one shift to 4 Sigma drops that to 6,210 defects per million. That’s real money freed up to invest in new products, features, and services. Which drives more market share. Which funds more improvement. The flywheel spins.
Here’s the mega trend I keep coming back to. Everyone’s rushing to throw AI at their operations. And I get it - the potential is massive. But around 80% of AI projects fail, and the reason isn’t the technology. It’s the processes underneath.
AI amplifies whatever it touches.
If your process is clean, measured, and controlled - like a well-run Six Sigma operation - then AI makes it faster, cheaper, and more consistent. But if your process is a mess? AI just breaks things at machine speed. You scale dysfunction across your entire operation.
Think about it. An AI agent following a broken workflow doesn’t stop and say “this doesn’t make sense.” It executes. Faster. At scale. Silent failure is the term that keeps coming up - mistakes spreading before anyone notices.
This is exactly why process definition and standardization matter more now than they did ten years ago. Six Sigma’s DMAIC approach - defining what good looks like, measuring current performance, finding root causes, improving, and controlling - is the prerequisite for any meaningful AI adoption. Fix the process first. Then automate.
The pattern we keep running into is always the same. Organizations that map and standardize their processes before adding automation get dramatically better results than those who try to automate chaos. You can’t shortcut the fundamentals.
Quality control and process improvement templates
Is quality optional?
Are you hearing this at work? That's busywork
Enter between 1 and 150,000
Enter between 0.5 and 40
Enter between $10 and $1,000
Based on $30/hr x 4 hrs/wk
Your loss and waste is:
every week
What you are losing
Cash burned on busywork
per week in wasted wages
What you could have gained
160 extra hours could create:
per week in real and compounding value
Total cumulative impact over time (real cost + missed opportunities)
You are bleeding cash, annoying every employee and killing dreams.
It's a no brainer - improve your workflows
Related questions
What is the Six Sigma concept?
Six Sigma’s a method for improving anything you do by finding and eliminating the causes of mistakes. You try something, measure the results, figure out where it went wrong, and make it better - step by step. The goal is to minimize errors whether you’re making a product or delivering a service.
How does DMAIC break down?
DMAIC stands for Define (figure out what’s broken), Measure (gather data on the problem), Analyze (find the root cause), Improve (fix it), and Control (keep it working). It’s problem-solving with evidence instead of guessing. Each step feeds the next one.
What are the five steps of Six Sigma?
Define what the problem is and what people need. Measure current performance. Analyze data to find root causes. Improve the process by making targeted changes. Control the new process so it doesn’t drift back. Each step builds on the last - skip one and the whole thing wobbles.
What does a Six Sigma level process mean?
A Six Sigma level process is statistically so consistent that it’ll produce no more than 3.4 defects per million opportunities. If you’d made a million sandwiches and only 3 or 4 were bad - that’s Six Sigma. Most organizations run at 3 or 4 Sigma, which means far more errors than they’d expect.
Why is it called Six Sigma?
Sigma’s a statistical measure of variation from the average. Six Sigma means the process average is six standard deviations away from the nearest failure point. It’s essentially a massive safety margin - six layers of buffer between your process and things going seriously wrong.
What is the difference between Six Sigma and Lean Six Sigma?
Six Sigma focuses on reducing errors and variation. Lean Six Sigma combines that with eliminating waste and time. Think of it as keeping your car in great mechanical shape (Six Sigma) while also making sure it uses minimal fuel and takes the shortest route (Lean).
How long does it take to get results?
Full Six Sigma deployment can take six months to a couple of years depending on an organization’s size and process complexity. But individual DMAIC projects often show results within weeks. You don’t need to transform everything at once - start with one process that’s causing the most pain and build from there.
What industries use Six Sigma?
It started in manufacturing but it’s spread everywhere - hospitals, banks, insurance companies, tech firms, consulting practices. Anywhere you’d want to reduce errors and speed up processes. Based on our experience at Tallyfy, we’ve seen teams in financial services, healthcare, and professional services all apply these principles to their workflow improvements.
What are Six Sigma certification levels?
Six Sigma uses a belt system similar to martial arts - White, Yellow, Green, Black, and Master Black Belt. Each level represents deeper problem-solving ability. A Yellow Belt understands the basics. A Master Black Belt can teach others and tackle what’s hardest. The certification structure keeps people accountable to a standard of practice.
Can small businesses use Six Sigma?
Without question. The principles scale down perfectly. You don’t need a massive deployment. Pick one process - maybe how you handle purchase orders or how new team members get onboarded - and run DMAIC on it. Start small, prove it works, then expand. The skills are the same whether you’ve got 10 people or 10,000.
About the Author
Amit is the CEO of Tallyfy. He is a workflow expert and specializes in process automation and the next generation of business process management in the post-flowchart age. He has decades of consulting experience in task and workflow automation, continuous improvement (all the flavors) and AI-driven workflows for small and large companies. Amit did a Computer Science degree at the University of Bath and moved from the UK to St. Louis, MO in 2014. He loves watching American robins and their nesting behaviors!
Follow Amit on his website, LinkedIn, Facebook, Reddit, X (Twitter) or YouTube.
Automate your workflows with Tallyfy
Stop chasing status updates. Track and automate your processes in one place.