How to Combine Six Sigma, Lean Thinking, and Theory of Constraints

Here's a realisation that changes how you think about improving a business.

Each of these three frameworks answers a different question.

Theory of Constraints asks: "What's the bottleneck?"
Lean Thinking asks: "What's wasted?"
Six Sigma asks: "Where's the variation?"

Use the wrong one at the wrong moment and you waste effort. Layer them correctly, and the results compound.

Most articles on this topic tell you to pick one and stick with it. That's fine as a starting point. But it's not how a mature business actually improves.

If you've already read the business improvement methods overview, you know the differences between these frameworks. This article picks up where that one ends. Now that you know what they are, here's how to use them together.

Why sequence matters more than methodology

Business owners love to debate which framework is "best." That debate misses the point.

None of them is best. Each is best at something specific.

Here's the problem with picking one and ignoring the others. If you run Six Sigma on a non-bottleneck process, you're polishing a part of the business that isn't holding anything back. You make it more consistent, sure. But nothing flows through the company any faster.

If you apply Lean before you've found your constraint, you just speed up work that ends up piling up somewhere else. A faster start with the same finish line.

Order is everything. Here's the sequence that actually works.

Step 1: Theory of Constraints first

Find the bottleneck. Nothing else matters until you do.

Every business has one thing holding it back. One department, one person, one process step. Find it, and you've found the point of maximum leverage. Every hour you invest there gives you a better return than an hour invested anywhere else.

In SYSTEMology, we start by mapping the Critical Client Flow: the 10 to 15 steps that take someone from first contact to happy, repeat customer. That map makes the bottleneck visible. Often it's obvious the moment you draw it.

For more on this, here's the full piece on Theory of Constraints in a small business context.

Once you've named the constraint, you've earned the right to start improving.

Step 2: Lean Thinking second

Now attack waste at the bottleneck.

Lean asks: what's happening in this process that doesn't add value? Double entry of data. Waiting for approvals. Unnecessary handoffs. Tasks that exist because nobody ever questioned them.

Remove the waste, and the bottleneck opens up. Work flows through faster. Lead time compresses. Capacity expands without hiring anyone.

This is the part most business owners skip. They try to hire their way out of a bottleneck instead of first removing the waste inside it. Adding people to a wasteful process just multiplies the waste.

Step 3: Six Sigma third

Now attack variation in what remains.

After you've removed the non-value-adding steps, you're left with the work that actually matters. That's when consistency becomes the goal. Same input, same output, every time.

In a small business, this rarely means certifications or statistical process control. It means standardised intake forms. Checklists. Templates. Trained responses to common scenarios.

When variation drops, quality climbs. And quality means fewer complaints, fewer rework loops, and more trust from customers.

Step 4: Kaizen always

Run this one in parallel, not after.

Kaizen is the cultural practice of continuous small improvement. Team members spot problems and fix them. Leadership makes it safe to raise issues. Everyone contributes to making things better.

Kaizen sits on top of the three structural methods. It's what stops the business from sliding backwards once you've done the hard work. Without it, your documented processes quietly rot.

Why this order matters

Let me show you what goes wrong if you get the order wrong.

Imagine a business owner decides to "get serious about quality." They kick off a Six Sigma-style project on the invoicing process. Templates get standardised. Variation drops. Invoices go out more consistently.

Meanwhile, the real bottleneck is sales. The company can't close enough deals to keep the team busy. All that effort on invoicing makes zero difference to the bottom line.

Or: a business owner reads about Lean and decides to eliminate waste in onboarding. They cut two steps. Onboarding gets faster. But onboarding was never the problem. Now new clients hit the delivery team faster, and delivery is where the real constraint lives. All they've done is create more pressure on an already strained team.

Theory of Constraints first. Always. It tells you where to point the other tools.

A practical example

Let's walk through this with a real scenario. A service business tells you: "Our customer delivery is slow."

TOC lens: Where's the bottleneck? You map the process end to end. You find that scheduling is where things pile up. Every job gets held there for two to three days while someone manually coordinates the calendar.

Lean lens: Now that you know scheduling is the bottleneck, what's wasted there? You find double entry of client details from the intake form into the scheduling software. Fifteen minutes per job. Across 50 jobs a week, that's 12 hours of pure waste.

Six Sigma lens: When scheduling does fail, why? You discover that inconsistent intake forms cause the failures. Some clients fill them out fully, others skip fields, and the scheduler has to chase the missing info. That's variation.

The fix: Standardise the intake form (remove variation). Connect it directly to the scheduling software (remove the double entry). Scheduling flows smoothly. The bottleneck moves somewhere else.

Now repeat.

A real business doing all of this

Doug and Andrea Glanville run The Sydney String Centre. It's a family-owned string instrument business, around 40 staff, selling, repairing, and renting violins, cellos, and other string instruments. Over 30 years in operation.

When they came to SYSTEMology, the business was at a complexity ceiling. Processes were inconsistent across departments. Retail did things one way, the workshop did things another way, and the e-commerce team did things a third way. Key knowledge lived in the heads of long-term staff. Doug and Andrea wanted to step back and take a more strategic view of the business, but they couldn't. Operational chaos kept pulling them in.

Andrea stepped up as their Systems Champion. Her background was in design and innovation consulting, and she applied a layered approach.

First, they found the bottlenecks. Mapping the Critical Client Flow made it obvious where the business was getting stuck. Certain handoffs between departments were breaking down. Certain customer touchpoints had no clear owner.

Second, they removed waste. As Andrea worked through the documentation, old workflows became visible as workflows for the first time. Steps that existed "because we've always done it that way" got questioned. Plenty of them got cut.

Third, they standardised. Once the remaining steps were clear, they got documented. Templates. Checklists. Procedures. A single source of truth the whole team could use instead of chasing long-term staff for answers.

Fourth, they built Kaizen into the culture. Team members started proactively identifying and suggesting systems. The documentation habit spread beyond Andrea. Continuous improvement became part of the way they worked.

The result? A single source of truth across the business. Silos broken down. Doug and Andrea transitioning from hands-on managers to strategic leaders. And a team that's actively making the business better every week.

They didn't run this as a formal Six Sigma program. There are no black belts at The Sydney String Centre. What they did was apply the thinking in the right order.

A second example from a very different industry

Gary McMahon runs Ecosystem Solutions. He's an ecologist with a consultancy that handles scientific assessments, data collection, and compliance reporting for environmental projects. Different world entirely. Same pattern.

Gary's firm faced three pressures at once. Work had to be consistent across consultants. New consultants had to get up to speed quickly. And the reports had to meet strict compliance standards.

That's one project that needs all three lenses.

Consistency across projects is a Six Sigma question. Specialist onboarding is a Lean question (how do you shorten the path from hire to productive?). Compliance reporting is a bit of both: standardised formats (Six Sigma) applied to the most important processes (TOC).

Gary's team used systemHUB to centralise their operational knowledge. Methodologies documented. Standard operating procedures in one place. Templates for reports. The result was better consistency across all client projects, faster onboarding for new consultants, and reduced risk of errors in compliance reporting.

Again, no formal program. Just the right thinking applied in the right order.

 

The small business caveat

You're not implementing these as formal corporate programs. Let me be really clear about that.

No certifications. No black belts. No consultants in suits running workshops on statistical process control.

You're using these methodologies as lenses. Questions you apply to your business in sequence. A bottleneck lens. A waste lens. A variation lens. A continuous improvement lens.

This is how it works in practice for a business doing $1-15 million with 10 to 50 staff. You don't need to become an expert in any one framework. You just need to know which question to ask when.

Most small business owners already have the instinct. They've just never had the order. Now you do.

Where SYSTEMology fits

If you're wondering where SYSTEMology sits in all this, it's the sequence for implementing these methodologies inside a real small business.

Step one in SYSTEMology: document what you do. That gives you the Critical Client Flow, which is the map you need for TOC. You can't find a bottleneck in a process you can't see.

Step two onwards: you layer the lenses on top of your documented systems. Find the bottleneck. Remove waste at it. Standardise what's left. Keep improving.

The right combination for most small businesses is: SYSTEMology + TOC + Lean + Six Sigma, with Kaizen as the ongoing cultural habit.

Each framework adds something the others don't. SYSTEMology provides the structure and the sequence. TOC shows you where to focus. Lean tells you what to cut. Six Sigma tells you what to standardise. Kaizen keeps you moving forward.

If you want the foundational piece, what is a business system lays it out.

The bottom line

You don't need to master each methodology. You need to apply them in the right order to the right problem.

Theory of Constraints first. Find the bottleneck.
Lean second. Remove the waste at it.
Six Sigma third. Standardise what's left.
Kaizen always. Keep improving.

And underneath all of it, SYSTEMology. Document what you do so you can see it, improve it, and hand it over.

Systemise first. Then layer.

Simple beats perfect. Always.

Ready to put the sequence to work? systemHUB gives you a single place to document your systems, find the bottleneck, and keep improving. It comes loaded with 100+ templates to get you started. Try it free.