← ArticlesSelecting Lean, Six Sigma and Constraint-Based ImprovementEngineering · ManufacturingLesson 19/32← PrevNext →
GuidePublished 14 Aug 202614 min readBy Kevin JoginManufacturingOperational ExcellenceSelecting LeanSix Sigma and Constraint-Based Improvement

Engineering · Manufacturing · Operational Excellence

Selecting Lean, Six Sigma and Constraint-Based Improvement

Engineering handbook for selecting lean, six sigma and constraint-based improvement, covering context and scope, technical challenge, key engineering insight.

Executive summary

This handbook section converts the supplied engineering material into a practical, source-controlled reference. It concentrates on the following learning outcomes.

Context and scope
Technical challenge
Key engineering insight
The Framework: Matching Methodology to Culture
Choose Six Sigma If...
Choose Lean Thinking If...

Context and scope

the practitioner stood at the whiteboard, staring at a chart that made no sense.

His team had implemented 43 process improvements over the past eighteen months. They'd trained two dozen Six Sigma black belts. They'd mapped every value stream. They'd installed a drum-buffer-rope system in production.

And yet—throughput was exactly where it had been two years ago.

"We're improving everything," he muttered to himself, "and accomplishing nothing."

If you've ever felt trapped in the improvement treadmill—working harder on getting better while results stay stubbornly flat—this story is for you.



Technical challenge

You know this feeling if you've ever researched process improvement.

Every methodology comes with its own:

  • Vocabulary (DMAIC vs. Value Stream vs. Drum-Buffer-Rope)
  • Metrics (Sigma levels vs. Flow time vs. Throughput)
  • Assumptions (Data-driven vs. Visual change vs. Systems thinking)
  • Champions who insist their way is the only way

the practitioner tried to reconcile the approaches. She created a spreadsheet comparing them side-by-side:

Methodology Core Theory Primary Focus Main Tool
Six Sigma Reduce variation Problem-focused Statistical analysis
Lean Thinking Remove waste Flow-focused Value stream mapping
Theory of Constraints Manage bottlenecks System-focused Constraint identification

The more she researched, the more confused she became.

Six Sigma assumed that if you reduce variation across all processes, the whole system improves. But what if you're perfecting processes that don't matter?

Lean assumed that waste removal automatically improves profitability. But what if you eliminate "waste" that was actually serving a purpose?

TOC assumed that only the constraint matters. But what if you ignore a non-constraint process and it becomes the constraint?

Each methodology seemed to address pieces of the puzzle while dismissing the others.

the practitioner put it bluntly in a leadership meeting: "It feels like we're being asked to choose a religion, not a business strategy."



Key engineering insight

The transformation happened—as transformations often do—during a casual conversation.

the practitioner was at an industry conference, venting to an illustrative engineering practitioner who had implemented all three methodologies over a 30-year career.

"They all claim to be complete solutions," the practitioner complained. "But they contradict each other."

the practitioner smiled. "Do they? Or do they just start from different places and end up in the same neighborhood?"

He grabbed a napkin and drew a simple diagram:

Six Sigma → Uniform output → THEN less waste, faster throughput, better flow Lean → Improved flow → THEN less variation, uniform output, constraints revealed TOC → Faster throughput → THEN less inventory, variation exposed, waste visible

"Look at the secondary effects," the practitioner said. "Every methodology eventually touches the concerns of the others. Six Sigma reduces variation, but that leads to less waste and better flow. Lean removes waste, but that exposes bottlenecks and reduces variation. TOC attacks constraints, but that forces you to eliminate waste and control variation."

The insight hit the practitioner like a thunderbolt.

"They're not competing religions," she said slowly. "They're different entry points into the same transformation."

the practitioner nodded. "The question isn't which methodology is 'right.' The question is which entry point fits your organization's culture and current pain."



The Framework: Matching Methodology to Culture

Here's what the practitioner—and eventually the practitioner and the practitioner—discovered about choosing the right approach:


Choose Six Sigma If...

Your organization values data and analysis.

Six Sigma thrives in environments where:

  • Engineers and scientists make up a significant portion of your team
  • Decisions are expected to be backed by numbers
  • People respect charts, graphs, and statistical proof
  • You have time for rigorous, structured investigation
  • The problem is variation—outcomes are unpredictable even when inputs seem consistent

The assumption: People understand that numbers represent process characteristics, and deeper data analysis leads to improvement.

The risk: You might improve processes that don't actually matter to overall performance. Perfecting a non-bottleneck is polishing deck chairs.

Primary effect: Uniform process output Secondary effects: Less waste, faster throughput, reduced inventory, improved quality


Choose Lean Thinking If...

Your organization values speed and visible change.

Lean thrives in environments where:

  • Operations people are the dominant culture
  • "Just show me results" is the prevailing attitude
  • Visual management appeals to leadership
  • Many small improvements feel more achievable than deep analysis
  • The problem is waste—you can see inefficiency everywhere you look

The assumption: People value the visual effect of flow, and many rapid improvements beat lengthy studies.

The risk: You might eliminate activities that seem wasteful but actually serve hidden purposes. Process interaction effects may surprise you.

Primary effect: Reduced flow time Secondary effects: Less variation, uniform output, reduced inventory, constraints revealed


Choose Theory of Constraints If...

Your organization values systems thinking and top-down direction.

TOC thrives in environments where:

  • Hierarchical structure is established and respected
  • Workforce involvement isn't expected or desired for strategic decisions
  • Speed and volume are primary success measures
  • The product/service design is stable
  • The problem is throughput—you know there's a bottleneck somewhere

The assumption: Total participation isn't necessary. A few people with decision-making power can drive change.

The risk: Minimal worker input means you might miss insights from the front lines. Solutions imposed from above may face resistance.

Primary effect: Fast throughput Secondary effects: Less inventory, new accounting perspectives, improved quality



The Resolution: Three Different Paths, Three Successful Outcomes

Back to our three leaders.

the practitioner chose Six Sigma.

Her medical device company was full of engineers who didn't trust gut feelings. They wanted data. They wanted statistical significance. They wanted to prove that changes worked before committing resources.

The DMAIC process gave them a framework that respected their analytical nature. Within eight months, they had identified three root causes responsible for 70% of defects—causes that would never have emerged from a "just do it faster" Lean approach.

Defect rates dropped 60%. More importantly, the team believed in the results because they'd seen the data.

the practitioner chose Lean.

His distribution center needed visible, immediate change. Morale was low. Workers felt like they were drowning. Analysis paralysis was the last thing they needed.

The Lean approach gave them quick wins. They 5S'd the warehouse in the first month—and employees immediately felt the difference. They mapped the value stream and found that products were being touched 34 times before shipping. They redesigned the flow to reduce it to 12.

Order fulfillment time dropped 55%. The team saw daily improvement, which built momentum for bigger changes.

the practitioner chose Theory of Constraints.

Her software team didn't need statistical analysis (they already tracked everything). They didn't need to eliminate waste (they were already lean). They needed focus.

TOC revealed that the constraint wasn't engineering capacity—it was the approval process for security reviews. Every feature had to pass through one overloaded security engineer. Exploiting that constraint (giving him dedicated support) and subordinating everything else to his capacity (limiting work-in-progress) transformed delivery.

Release predictability jumped from 40% to 85%. The team stopped feeling like they were fighting fires and started feeling like they were building.



Engineering takeaway

If you're facing your own improvement decision, here's what you need to know:

1. The methodologies aren't enemies—they're neighbors.

All three improvement philosophies eventually address the same concerns. They just enter through different doors. After years of implementation, a mature Six Sigma program looks a lot like a mature Lean program looks a lot like a mature TOC program.

2. Culture determines which door to enter.

Don't choose based on which methodology sounds most impressive or which consultant is most persuasive. Choose based on how your organization actually thinks and makes decisions.

Ask yourself:

  • Do we trust data or visible results?
  • Do we value deep analysis or rapid iteration?
  • Do we expect broad participation or directed change?

3. Starting is more important than perfect selection.

The organizations that fail aren't the ones who choose the "wrong" methodology. They're the ones who study all three endlessly, waiting for certainty that never comes.

Pick a door. Walk through it. Adjust as you learn.

4. Secondary effects will teach you what to try next.

As you implement your chosen approach, you'll naturally encounter the concerns of other methodologies. A Six Sigma project will reveal flow problems. A Lean initiative will surface bottlenecks. A TOC implementation will expose variation.

That's not a sign of failure. It's a sign of progress. Let the secondary effects guide your evolution.



Your Next Step

Look at your current improvement efforts.

Are you trying to implement all methodologies simultaneously, spreading resources thin and confusing your team?

Or are you stuck in analysis mode, comparing frameworks when you should be fixing problems?

Here's your action item: Pick one entry point based on your culture. Commit to it for six months. Track both primary and secondary effects.

Then come back and tell me what you learned.

Because the secret the practitioner finally discovered—standing at that whiteboard two years into his improvement journey—wasn't that he'd chosen the wrong methodology.

It was that he'd never really chosen at all.

He'd been so busy improving everything that he'd committed to nothing.

Don't make that mistake.

Choose your door. Walk through it. The transformation is waiting on the other side.


What improvement methodology fits your organization's culture? Drop a comment below—I'd love to hear which door you're walking through.


Context and scope

A factory floor in chaos. Equipment being sold. Entire production lines ripped up and relocated. Workers watching their familiar workstations disappear overnight.

This wasn't a company failing—this was a company transforming.

And the lessons from the source manufacturing plant' lean journey from 2001 to 2005 might just change how you think about operational excellence forever.



Understanding the Enemy

Before you can eliminate waste, you have to see it. the source manufacturing plant identified seven deadly wastes hiding in plain sight—what they called DOTWIMP:

  • Defects — Products that need rework or scrap
  • Overproduction — Making more than customers need
  • Transportation — Unnecessary movement of materials
  • Waiting — Idle time between process steps
  • Inventory — Excess materials sitting unused
  • Motion — Wasted movement of people
  • Processing — Doing more work than required

But the source manufacturing plant added an eighth waste that most companies miss: Human Intellect—failing to tap into the ideas and expertise of the people actually doing the work.


The Eight-Tool Arsenal

To combat these wastes, the team deployed eight interconnected lean tools:

1. 5S (Sort, Set in Order, Shine, Standardize, Sustain) The foundation of everything. You can't improve what you can't see, and you can't see anything in a cluttered, disorganized workspace.

2. Value Stream Mapping (VSM) Before fixing anything, map the current state. Where does value flow? Where does it stagnate? Draw the picture, then design the future.

3. Standard Work When everyone does the same task differently, quality suffers and training becomes impossible. Standardize the best method, then improve from there.

4. Continuous Flow Products should move steadily through production, not sit in piles between stations. Flow means rhythm. Rhythm means predictability.

5. Error Proofing (Poka-Yoke) Design processes so mistakes become impossible—not just unlikely, but actually impossible.

6. Setup Reduction Long changeovers kill flexibility. The faster you can switch between products, the smaller batches you can run, the more responsive you become.

7. Total Productive Maintenance (TPM) Machines break down when you ignore them. TPM means everyone takes ownership of equipment health—operators, not just maintenance crews.

8. Pull Systems Stop pushing products based on forecasts. Let actual demand pull materials through production. Kanban cards replace mountains of inventory.


The Real Battle: Resistance, Confusion, and Growing Pains

Here's what the textbooks don't tell you about lean transformation:

It's messy.

The the source manufacturing plant team warned visitors: "Be prepared for chaos. Without chaos, there is no change."

They weren't being dramatic. During the transformation:

  • Entire production lines were relocated multiple times
  • Equipment was sold off—including a robotic welding cell that had once been the pride of the operation
  • Warehouse space was compressed again and again
  • Workers had to learn new layouts, new processes, new ways of thinking

Imagine showing up to work one day and your entire department has moved to the other side of the building. Now imagine that happening repeatedly over 18 months.

That's what transformation looks like in real life.

The team didn't just complete isolated improvement events. They executed 65 kaizen events across the plant—rapid improvement projects targeting specific problems. Value stream mapping alone accounted for 27 events. 5S projects totaled 22. Pull system implementations, error-proofing initiatives, setup reductions, TPM rollouts—the pace was relentless.



Physical Results You Can See

Before 5S in the backyard storage: A wasteland of random equipment, unused materials, and forgotten inventory.

After 5S: Clean, organized space that actually serves a purpose.

Before 5S in tool storage: Technicians wasting time hunting for equipment, tools scattered across multiple locations.

After 5S: Shadow boards showing exactly where every tool belongs. Nothing missing. Nothing misplaced.

Before warehouse compression: Racks everywhere, materials spread across two buildings.

After compression: 180 racks freed up. 2,321 square feet reclaimed. An entire leased building vacated.


Financial Results That Matter

The numbers were staggering:

  • $700,000+ annual savings from vacating the leased building
  • $193,200 purged from finished goods and work-in-process inventory
  • Gross Inventory Days on Hand reduced from 116.8 to 98.8 (target: 87.7)
  • Stock Fill Rate increased from 86% to 93.1% (target: 95%)
  • Critical equipment eliminated — A 60-ton Bliss press, once considered irreplaceable, was removed after setup reduction made the smaller 40-ton press sufficient

Human Results That Transform Culture

One statistic stands out: Continuous flow improvements freed up one entire worker from the Chassis Line.

That person wasn't laid off. They became a Supervisor and Lean Technician—elevated from executing tasks to leading improvement.

This is what respecting human intellect looks like in practice. You don't eliminate people. You elevate them.



Your Takeaway: What This Means for You

Whether you run a factory, lead a team, or manage your own personal productivity, the source manufacturing plant's journey offers three critical lessons:


. Start by Seeing the Waste

You can't improve what you don't measure. The seven wastes exist in every operation—including your email inbox, your morning routine, and your meeting schedule.

Ask yourself: Where am I overproducing? Where am I waiting? Where am I moving without purpose?


. Embrace the Discomfort of Change

the source manufacturing plant's plant looked like chaos during transformation. Equipment was being moved. Layouts were shifting. Routines were disrupted.

But chaos with direction is progress.

If your improvement efforts aren't creating some discomfort, you're probably not changing anything meaningful.


. Respect Human Intellect

The eighth waste is often the deadliest. Every person on your team has ideas for improvement. Every process contains hidden knowledge.

The question isn't whether expertise exists—it's whether you're capturing it.

the source manufacturing plant didn't just train workers in lean tools. They created "Tool Champions" and a Site Lean Coordinator role. They turned front-line employees into improvement leaders.



The Journey Continues

By the time of their presentation, the source manufacturing plant's Australian plant had risen from the bottom of the global rankings to the middle of the pack. Their 2.8 score placed them among 5 plants in the 2.0-2.9 range, with 26 plants above them at 3.0-3.8.

But the journey wasn't over.

Phase 1 (2001-2003) had focused on manufacturing—"wall to wall" improvements within the factory.

Phase 2 (2003-2004) expanded to the Total Product Delivery System—connecting suppliers, customers, and internal processes.

Phase 3 (2005 onward) aimed for the Total Business System—every function, every process, every corner of the organization.

The destination was never a number on a scorecard. The destination was a culture of continuous improvement—a factory where chaos was welcomed, waste was visible, and every person was a problem-solver.



What Chaos Are You Avoiding?

Here's the uncomfortable question this story forces us to ask:

What transformation are you postponing because you're afraid of temporary chaos?

Maybe it's a reorganization that would improve flow but disrupt routines.

Maybe it's eliminating inventory that feels like security but is actually dead weight.

Maybe it's empowering people who have ideas but no platform to share them.

the source manufacturing plant's journey proves that you can take a plant from 1.0 to 2.8 in eighteen months. You can save $700,000 annually. You can purge nearly $200,000 in unnecessary inventory.

But only if you're willing to embrace the chaos that makes change possible.

The floor will look messy for a while. The routines will be disrupted. People will be uncomfortable.

And that's exactly how you know you're doing it right.



Your Next Step

Don't try to transform everything at once. the source manufacturing plant didn't.

Start with one area. Apply 5S. Map the value stream. Ask your team what they see that management doesn't.

Then let the chaos begin.

Because on the other side of temporary disorder is permanent improvement.


What's the biggest waste hiding in your operation right now? Hit reply and tell me—I'd love to hear what you're seeing.

Engineering use and verification

Choose and control a process from the required function, material, geometry, tolerance, surface condition, volume, safety and inspection plan. Confirm the process window with representative trials, identify the variables that move quality, and connect each critical characteristic to an observable control and reaction plan. Do not convert a successful source example into a universal limit; validate capability using the actual machine, tooling, material batch and operating conditions.

  • Confirm scope, assumptions, interfaces and required outcome.
  • Use one controlled unit system and show every conversion.
  • Identify current project, customer and regulatory requirements.
  • Separate source examples from mandatory acceptance criteria.
  • Check calculations, tables and selections by an independent method.
  • Verify safety, maintainability and credible failure modes.
  • Record evidence, revisions, approvals and unresolved limitations.
  • Validate the result under representative operating conditions.

Continue learning

Operational Turnaround without Workforce Reduction: Defect BreakdownGuide · ManufacturingNEXT LESSON →Gemba Observation and Work-Study PracticeGuide · ManufacturingOperational Turnaround without Workforce Reduction: The Calm Before the StormGuide · ManufacturingValue-Stream Mapping and Future-State DesignGuide · Manufacturing