A manufacturer decides it needs a structured approach to improvement. One adviser recommends Lean: map the value stream, remove waste, create flow. Another recommends Six Sigma: train some people in statistical problem solving and run data-driven projects. A third recommends the theory of constraints: find the bottleneck and manage the whole operation around it. Each comes with its own vocabulary, measures and enthusiasts, and each claims to be a complete system. The owner is left wondering which one is right.
The honest answer is that all three are useful, they address different kinds of problems, and they lead to many of the same places. Lean starts from waste and flow, Six Sigma from variation and defects, and the theory of constraints from the one resource that limits the output of the whole system. A business can waste a great deal of effort by applying the wrong method to its problem: running careful statistical projects on processes that do not limit output, or tidying every workstation while the real bottleneck sits starved of work.
This article explains the core idea of each approach, how to diagnose which problem you mostly have, how the methods complement each other, and what it takes to make any improvement programme deliver lasting results. It is general information for owners and managers of manufacturing, fabrication and service operations.
Three starting points
| Lean | Six Sigma | Theory of constraints | |
|---|---|---|---|
| Core idea | Remove waste and make value flow to the customer | Reduce variation so output is consistent and defects rare | Find and manage the constraint that limits the whole system |
| Typical symptom it addresses | Long lead times, visible waste, excess stock, lots of handling | Unpredictable quality, recurring defects with unclear causes | Late deliveries and backlogs while many people are busy |
| Main tools | Value stream maps, 5S, standard work, cells, pull systems, set-up reduction | DMAIC projects, measurement studies, statistical analysis, designed experiments, control charts | Five focusing steps, drum-buffer-rope scheduling, buffer management, throughput accounting |
| Main measures | Lead time, work in progress, first-time-through quality | Defect rates, process capability, cost of poor quality | Throughput, inventory, operating expense, constraint utilisation |
| Typical style | Many small, fast, visible improvements involving everyone | Fewer, deeper, data-driven projects led by trained specialists | Focused decisions about a few points in the system |
| Main risk | Removing activities that served a hidden purpose; improving everywhere except where it matters | Perfecting processes that do not limit performance; slow projects | Neglecting the front-line knowledge and variation that feed the constraint |
Lean: waste and flow
Lean thinking, which grew out of the Toyota Production System, asks what the customer values and removes everything else. It classifies waste into familiar categories: overproduction, waiting, transport, motion, excess inventory, over-processing, defects and unused skills. It aims for work that flows continuously in small quantities, pulled by customer demand rather than pushed by forecasts, with problems surfaced and solved quickly by the people doing the work.
Lean’s strengths are speed, visibility and involvement. Results such as shorter lead times, freed floor space and less searching are visible within weeks, which builds momentum. Its weakness is that it can spread effort evenly across a business when the binding problem is in one place, and its simple tools can be applied without understanding why the waste exists.
Six Sigma: variation and defects
Six Sigma starts from the observation that variation causes defects, rework, unpredictable delivery and cost. It uses a structured project method, usually DMAIC (define, measure, analyse, improve, control), with an emphasis on trustworthy data, verified causes and statistical tools. Trained practitioners, often graded as green belts and black belts, lead projects on specific problems.
Six Sigma’s strengths are rigour and credibility: it is good at chronic problems with unclear causes, where opinion has failed, and it produces evidence that engineers and customers trust. Its weaknesses are pace and focus. A project can take months, and a well-run project on a process that does not limit the business improves a local measure without improving the business. The fixing a recurring problem with DMAIC article sets out the DMAIC method in detail.
The theory of constraints: the bottleneck governs the system
The theory of constraints, developed by Eliyahu Goldratt, starts from the observation that every system has at least one constraint, a resource or rule that limits its output, and that improving anything else does not improve the system’s output at all. An hour gained at a non-constraint is an hour of extra idle time; an hour lost at the constraint is an hour lost for the whole business.
Its central method is the five focusing steps:
- Identify the constraint: the resource with the largest queue in front of it, the one that is always behind, the one that sets the pace of deliveries.
- Exploit the constraint: get the most out of it without spending money. Never let it wait for work, materials, people or decisions. Stagger breaks so it keeps running. Do set-up preparation while it is running. Check quality before the constraint so it does not process parts that will be scrapped.
- Subordinate everything else: run the rest of the system at the pace of the constraint. Release work at the rate the constraint can process it, and keep a protective buffer of work in front of it. This is the logic of drum-buffer-rope scheduling: the constraint is the drum that sets the beat, the buffer protects it from upstream disruptions, and the rope ties the release of new work to its pace.
- Elevate the constraint: only after exploiting and subordinating, add capacity, such as another machine, another shift or outsourcing.
- Repeat: when the constraint moves, as it will, start again, and do not let old rules become the new constraint.
The theory of constraints also offers throughput accounting, which judges decisions by their effect on throughput (sales revenue less truly variable costs), inventory and operating expense, rather than by unit costs that spread overheads across every hour. It explains why saving labour at a non-constraint may save nothing, while adding capacity at the constraint may be worth far more than its cost suggests.
Its strengths are focus and impact. Its risk is treating improvement as a matter for a few decision-makers, missing the front-line knowledge and the variation that cause the constraint to lose time. The before adding capacity, change the control logic article explores how rules and scheduling, rather than equipment, often govern output.
Diagnose the problem before choosing the method
The best guide to which method to start with is the nature of the problem.
| What you observe | Likely primary problem | Natural starting point |
|---|---|---|
| Jobs spend most of their lead time waiting; stock everywhere; lots of walking and handling | Waste and poor flow | Lean |
| Quality varies unpredictably; defects recur despite fixes; nobody agrees on the cause | Variation with unknown causes | Six Sigma (DMAIC) |
| Output is capped by one area; deliveries late; most areas have spare time while one is always behind | A constraint | Theory of constraints |
| The cause and fix are obvious and low risk | None that needs a method | Just fix it, then check it worked |
Many businesses have all three problems at once. The sequence still matters. If output is constrained, start by finding the constraint, because it tells you where Lean and Six Sigma effort will pay. If there is no clear constraint but lead times are long, start with flow. If a specific chronic defect is costing money, a focused DMAIC project may be the most valuable first step.
The methods converge
Each method, applied well, ends up touching the concerns of the others:
- Six Sigma reduces variation, which makes flow smoother, reduces the buffers needed and stops a constraint losing time to defects.
- Lean improves flow, which reveals the constraint and exposes sources of variation that large batches and stock used to hide.
- The theory of constraints focuses attention on the bottleneck, where waste removal and variation reduction then pay off most.
A practical combined approach is to use the theory of constraints to decide where to work, Lean to remove waste and create flow at and around that point, and Six Sigma to tackle the variation and defects that steal capacity from it. Over time, the business develops a shared improvement language that draws on all three, rather than an allegiance to one.
Culture matters, but it is not destiny
Some organisations take naturally to one approach. Engineering-heavy businesses that trust data may find Six Sigma’s rigour persuasive. Operations-led businesses that value visible action may find Lean’s quick wins more motivating. Businesses with clear top-down decision-making may find the focus of the theory of constraints easier to adopt.
Fit with culture makes adoption easier, but it should not override diagnosis. A data-loving business with a bottleneck problem still needs to manage the bottleneck. Choose the method the problem needs, and adapt how it is introduced to the culture.
What makes an improvement programme work
Whichever method you choose, the same organisational factors decide whether it delivers. Programmes commonly falter for predictable reasons:
- No protected time. Improvement leaders are expected to run projects on top of their normal jobs, so projects slip. Allocate real time, even if only a few hours a week, and protect it.
- Absent sponsors. Managers approve projects but do not attend reviews or remove obstacles. Every project needs a sponsor who owns the result and turns up.
- Poor project selection. Projects are chosen because someone is enthusiastic, not because they address a business priority. Select projects that link to strategy, customer pain or the constraint.
- Method confusion. Teams run full statistical projects on problems that needed a quick fix, or quick fixes on problems that needed analysis. Give people a simple rule for choosing.
- No coaching. Newly trained people are left alone with their first project. Pair them with experienced coaches, internal or external.
- Outside experts who do not know the business. External specialists can bring method, but they need people who know the process and its history.
- Results that are not sustained. Projects close without standard work, control plans or process owners, and performance drifts back.
- No learning between projects. Each project starts from scratch. Keep short, consistent records and share them.
For a small business, the structure can be light. There is no need for formal belts or a programme office. What matters is a clear way of choosing problems, a habit of verifying causes, a routine for small daily improvements, protected time for a few bigger projects each year and a leadership team that reviews progress.
Measures that keep the programme honest
Measure the programme by its effect on the business, not by activity:
- Throughput, lead time and on-time delivery.
- Quality: defects, rework, first-time-through and customer complaints.
- Cost of poor quality: scrap, rework, warranty and sorting.
- Inventory and working capital.
- Sustained results: whether improvements still hold six and twelve months later.
Counting projects completed, people trained or kaizen events held says little about whether the business has improved.
A worked example
This is an illustrative example. A 50-person cabinet and joinery manufacturer makes kitchen and office fit-out components. Panels are cut on a CNC router, edged on an edgebander, drilled, assembled and packed. Deliveries are often late and the backlog is growing, though most areas seem to have spare time at some point in the day. The owner is considering a Lean programme across the whole factory.
Diagnosis. A week of observation shows panels queuing in front of the edgebander, while drilling and assembly frequently wait for work. The edgebander processes about 40 panels an hour and runs about 7 productive hours a day, so it can edge about 280 panels a day. About 6% of edged panels are rejected for chipped edges, leaving about 263 good panels. Customer demand requires about 300 good panels a day. The edgebander is the constraint.
Exploit. Breaks are staggered so the edgebander runs through them, adding about 40 minutes a day. Edge tape and the next jobs are prepared while it is running, cutting changeover losses by about half an hour a day. Panels are now checked for router defects before edging, so the constraint no longer processes panels that will be scrapped anyway. Productive time rises to about 8.2 hours, or about 327 panels a day. At the same 6% reject rate, good output is about 307 panels, just above demand.
Subordinate. The router, which had been cutting as much as possible to keep busy, now releases panels at the edgebander’s pace, keeping a buffer of about half a day of work in front of it. Work in progress between the router and edgebander falls sharply, and the floor space it occupied is recovered.
Six Sigma on the constraint. Because every rejected panel at the edgebander now costs output for the whole business, the owner sponsors a focused DMAIC project on edge chipping. The team verifies that most chipping comes from worn pre-milling cutters and inconsistent panel feed, introduces a cutter change schedule based on metres edged and a feed guide, and reduces rejects to about 1.5%. Good output rises to about 322 panels a day, giving spare capacity to start clearing the backlog.
Lean where it now matters. With the edgebander protected, a value stream map shows that the next biggest delay is at packing, where labels and hardware kits are prepared in batches. A small Lean improvement project moves kit preparation to a line-side supermarket.
Elevate later. A second edgebander, which had been in the budget, is deferred. The owner will review it once the backlog is cleared and demand has been tracked for six months.
Applying this in an Australian business
- Diagnose before choosing: waste, variation or a constraint.
- Find the constraint first if output is limited, and focus improvement there.
- Use Lean to shorten lead times and remove waste, especially around the constraint.
- Use Six Sigma for chronic problems with unclear causes, especially those that cost constraint time.
- Exploit and subordinate before buying capacity.
- Protect time for improvement and give every project an active sponsor.
- Select projects that link to business priorities.
- Coach new practitioners and sustain results with standard work and process owners.
- Measure business results, not programme activity.
Where improvement programmes go wrong
- Choosing a method by fashion or the adviser’s preference.
- Improving non-constraints and wondering why output does not rise.
- Buying capacity before exploiting the constraint.
- Running long statistical projects on problems with obvious fixes.
- Treating Lean as tidying rather than flow.
- Training people without giving them time or coaching.
- Declaring success before results have held.
Questions to ask before starting
- What limits our output today, and how do we know?
- Is our main problem waste and slow flow, unpredictable quality or a bottleneck?
- Where would an hour saved actually increase what we deliver?
- Which chronic problems have resisted simple fixes?
- Who will sponsor each improvement, and how much time will the improvers have?
- How will we know the improvements have held a year from now?
Bringing it together
Lean, Six Sigma and the theory of constraints are not competing beliefs but different entry points into the same goal: a business that delivers more value, more reliably, with less waste. Lean starts with flow, Six Sigma with variation and the theory of constraints with the bottleneck. Diagnose which problem dominates, start there, and let each method draw on the others: use the constraint to decide where to focus, Lean to make work flow and Six Sigma to remove the variation that steals capacity. Then give improvement the conditions it needs, with protected time, active sponsors, sensible project selection, coaching and measures that track real business results.
Source: KEVOS editorial notes, drawing on earlier KEVOS operational excellence handbooks on selecting Lean, Six Sigma and constraint-based improvement and on Lean Six Sigma cost and quality improvement. The worked example is illustrative. This article is general information.
