What's the best business improvement methodology for small business?

For most small service businesses, Theory of Constraints combined with Kaizen is the strongest combination. Theory of Constraints helps you focus on the one thing holding you back, and Kaizen builds a culture of small, constant improvement. But none of it works without documented systems underneath. Document your Critical Client Flow first. Then apply the methodology.

Do I need Six Sigma for my small business?

Almost certainly not. Six Sigma was built for high-volume manufacturing where tiny error rate reductions save millions. In a small service business, the cost of implementing Six Sigma (training, certification, measurement infrastructure) far outweighs the benefit. The one idea worth stealing: measure error rates on the one or two processes that matter most.

What's the difference between Lean and Kaizen?

Lean is a methodology focused on cutting waste: anything that doesn't add customer value. It's often applied as a project. Kaizen is a cultural practice of small, continuous improvement involving everyone in the business. Lean tells you what to cut. Kaizen tells you how to keep improving after the cut. They work well together.

Can I use multiple improvement methodologies at once?

Yes, but carefully. Most small businesses do better picking one primary framework (usually Theory of Constraints or Kaizen) and borrowing useful ideas from the others. Trying to formally implement all four methodologies at once creates overwhelm and nothing gets done. Start with documentation. Add one methodology. Build the habit. Expand from there.

4 Business Improvement Methods for Small Business

Every few years, a new "business improvement methodology" gets hyped.

Six Sigma. Lean. Agile. Theory of Constraints. Kaizen.

Consultants build careers on them. CEOs of Fortune 500 companies swear by them. Books stack up on the airport bookshop shelf.

Then a small business owner, drowning in the daily grind, picks one up and tries to implement it. Two months later, the binder is on a shelf gathering dust. The team has gone back to doing things the old way. Nothing has changed.

Here's the thing: most of these methodologies weren't built for you.

They were built for factories, tech giants, and companies with thousands of employees and entire departments dedicated to process improvement. When you try to apply them inside a 15-person business, they collapse under their own weight.

But there are ideas worth stealing from each of them. You just need to understand what each one actually does, what it gets right, and where it falls down when you try to plug it into a small business.

Let me walk you through the four you should know about.

Six Sigma: the quality obsessive

Six Sigma came out of Motorola in the 1980s. Jack Welch made it famous at General Electric in the 90s. The goal? Reduce defects and variation in manufacturing to near-zero. Specifically, no more than 3.4 defects per million opportunities.

It works by measuring everything. Every step of every process. You collect data, find where errors happen, and systematically eliminate them. The methodology uses a framework called DMAIC: Define, Measure, Analyse, Improve, Control.

Six Sigma is brilliant for high-volume manufacturing. If you're making a million widgets a month, tiny improvements compound into massive savings.

But in a 15-person service business? It's overkill.

You don't need Six Sigma Black Belt certification to work out why your team keeps forgetting to follow up with leads. You need a documented follow-up system.

One idea to steal: measure your error rates. Pick one process that matters. Track how often it goes wrong. Most small business owners have no idea because they've never counted. Counting is the first step to fixing.

Theory of Constraints: find the bottleneck

Theory of Constraints was developed by Eliyahu Goldratt in his 1984 book The Goal. The idea is simple: every system has a bottleneck. Whatever the bottleneck is, it sets the pace for the entire business. Fix the bottleneck, and the whole system moves faster.

This is my favourite framework for small business.

Why? Because it matches how small business owners actually experience their business. You feel the bottleneck every day. It's the thing that keeps you up at night. It's the one person who can't handle any more, the one process that slows everything down, the one decision that only you can make.

If you want to go deeper on this one, I've written a full article on theory of constraints for small business.

Goldratt's five-step process:

Identify the constraint.
Exploit it. Get the most out of it without adding resources.
Subordinate everything else to the constraint.
Elevate the constraint. Add resources only if steps 2 and 3 aren't enough.
Repeat. The next bottleneck will appear.

Ryan at Stannard Homes was the bottleneck. Every quote went through him. Every client issue landed on his phone. His constraint wasn't staff or equipment or marketing. It was him.

Once he and his daughter Eryn identified that, they knew what to document first. The quoting process. The client handover. The scheduling decisions. The systems that removed Ryan from the critical path.

Result: they doubled headcount from seven to 15 staff. Ryan now takes extended holidays. Eryn runs operations.

Theory of Constraints works in any small business because it forces you to focus. You stop trying to improve 50 things at once. You find the one thing that's holding you back and you go at it.

Lean thinking: remove the waste

Lean grew out of the Toyota Production System. Toyota engineers spent decades refining how they built cars, and the world eventually caught on. The core idea: anything that doesn't add value to the customer is waste. Find it. Cut it.

Lean identifies seven types of waste: overproduction, waiting, transport, over-processing, inventory, motion, and defects. In a factory, these are easy to see. Parts pile up. Workers stand around. Trucks move stuff that nobody needs yet.

In a small service business, waste looks different:

Meetings that should have been emails
Approval steps that don't actually add safety
Duplicate data entry because two systems don't talk
Clients waiting on you because you're the only approver
Re-work because the brief was unclear the first time

Lean asks a simple question of every step: would the customer pay for this? If not, it's waste.

Jeanette Farren at DiggiddyDoggyDaycare ran a business that served over 2,000 dogs. When she started documenting her systems, she found dozens of steps that nobody would miss if they disappeared. Extra forms. Redundant check-ins. Sign-offs that existed because they'd always existed.

She cut the waste. She systemised what was left. The business became so clean and profitable that PETstock, a major corporate buyer, acquired it.

One idea to steal: walk your Critical Client Flow and ask "would the customer pay for this step?" You'll be surprised how many you can cut.

Kaizen: small, constant improvement

Kaizen is a Japanese word that means "change for better." It's the cultural backbone of Toyota's approach. Unlike Six Sigma or Lean, Kaizen isn't a project you finish. It's a habit you build.

The idea: don't try to fix everything at once. Make small improvements every day. Involve everyone. Over time, those tiny changes compound into enormous gains.

In a Toyota factory, any worker on the assembly line can pull a cord to stop the line if they see a problem. The team gathers. They fix it. They document the fix. The next shift inherits a slightly better process.

For a small business, Kaizen looks like this:

Weekly team huddle: what got in our way this week?
One small improvement per person per week
Document the fix in the system
Repeat next week

Small beats big. Constant beats occasional. One percent better every week compounds to roughly 67 percent better over a year.

Kaizen is cultural. It's not a framework you implement on a Tuesday afternoon. It's a rhythm your team gets into. It's how you stop working in the business and start working on it, together.

One idea to steal: build a weekly systems improvement habit. Ten minutes. One process. Better than last week.

systemHUB — document your systems before applying any methodology — Document your systems first. Then choose the right methodology to improve them.

What's missing from all four

Here's the uncomfortable truth. Six Sigma, Theory of Constraints, Lean, and Kaizen all assume one thing: that your business already has documented processes.

Six Sigma measures errors in existing processes. Theory of Constraints optimises existing flow. Lean cuts waste from existing steps. Kaizen improves existing systems.

If you don't have systems in the first place, you have nothing to improve.

This is where most small business owners get stuck. They read a Lean book, get excited, and try to apply it to their business. But their business doesn't run on documented processes. It runs on the owner's memory, the team's best guesses, and a fair bit of luck.

You can't "cut waste" from a process that exists only in your head. You can't "identify the constraint" when you can't see the system. You can't "reduce variation" when there was never a standard to begin with.

The first improvement method you actually need isn't Six Sigma or Lean. It's documentation.

Before any methodology works, you need to know what a business system is and get yours out of your head and onto paper. Then, and only then, do the methodologies have something to work with.

The SYSTEMology approach: improvement AFTER systemisation

I learned this lesson the hard way.

When I was running Melbourne SEO Services, I was a methodology junkie. I read every business improvement book I could find. I tried to apply Lean. I read The Goal and tried to identify my constraints. I wrote process improvement frameworks on whiteboards.

None of it stuck.

Why? Because my business didn't have documented systems. Everything was in my head, or in the heads of my team. When I tried to "optimise" a process, I was optimising something that didn't actually exist in a stable form. Every week the process drifted. Nothing held.

The breakthrough came when I stopped trying to improve and started trying to document.

We wrote down how we did things. The sales process. The client onboarding. The technical SEO work. The reporting. The handoffs between teams.

Once the systems existed on paper, everything changed. Now when something went wrong, I could point at the system and ask "where did we break from this?" Now when we spotted waste, we could cut it from the documented process and the cut stuck. Now when we found a bottleneck, we could redesign the system around it.

I stepped out of daily operations in 2016. Sold the business. It ran without me because the systems existed, not because I had read the right book.

SYSTEMology book — the 7-step framework for small business — SYSTEMology: the 7-step framework built specifically for small business.

Same principle as process first, then AI. You can't automate a process you haven't documented. You can't improve a process you haven't documented either. Documentation isn't a precursor to the real work. Documentation is the real work.

Which method should you use?

The honest answer: a bit of each, matched to your situation. Here's a simple guide.

If you're a service-based business (agency, consulting, coaching, professional services):

Theory of Constraints to find your bottleneck
Kaizen to keep systems improving week by week
Skip most of Six Sigma and Lean until you're larger

If you're in product or manufacturing:

Add Lean to cut waste from your production flow
Add elements of Six Sigma if you're shipping high volume
Still use Theory of Constraints to focus your attention

If you're in SaaS or digital:

Borrow Agile ideas for your delivery teams
Use Kaizen for continuous product improvement
Theory of Constraints for figuring out what to fix next

For every business, regardless of industry:

Document your critical processes first. Use the SYSTEMology framework: start with your Critical Client Flow, the 10 to 15 steps that take a client from first interaction through to happy customer. Get those documented before you reach for any improvement methodology. For more on what "good" looks like, see the characteristics of good business systems.

The bottom line

Methodologies aren't magic.

They're tools. Each one was built to solve a specific problem in a specific type of business. Pick the right tool for your situation. Ignore the rest.

But before you reach for any tool, make sure you have something to work on. Document your systems. Get them out of your head. Get your team following them.

Then and only then does Theory of Constraints help you find your bottleneck. Then and only then does Lean help you cut waste. Then and only then does Kaizen help you improve week by week.

Systems first. Methodology second.

Simple beats perfect. Always.

Ready to document your systems before choosing a methodology? systemHUB gives you a single place to build, store, and share every system in your business. It comes loaded with 100+ templates to get you started, so you have something real to improve. Try it free.

4 Business Improvement Methods You Should Know About