Feeds

OIL Framework vs Lean Six Sigma: Which Fits Your Operation

Updated May 12, 2026

OIL (Interrogate, Delete, Simplify, Automate) and Lean Six Sigma both target operational waste, but OIL is a fixed-sequence protocol built for $10M–$100M operators who need decisions this week, not a certification cycle. Lean Six Sigma is a data-heavy methodology built for enterprise project teams. OAG runs OIL inside every Operations Architect engagement before any optimization work begins.

Why This Matters Now

Most lower-middle-market operators don't have six months to run a DMAIC project. They have one ops lead, undocumented processes, and a SaaS stack that costs more than it returns. Reaching for Lean Six Sigma in that environment doesn't fix the problem. It adds a methodology on top of the chaos.

At the same time, OIL is not a universal replacement. It's a decision-forcing sequence. Knowing which tool fits which phase is the difference between clearing ground and rearranging it. This page draws that line precisely, using real engagement receipts, not theory.

What the OIL Framework Is and Why the Sequence Is Not Optional

OIL stands for Interrogate, Delete, Simplify, Automate. The order is fixed. You cannot run these steps out of sequence and get the same result, the same way you can't build a wall before pouring the foundation.

  • Interrogate first: Ask whether the work should exist at all before you touch how it's done. Most teams skip this step because it's uncomfortable. That's where the real waste hides.
  • Delete second: Cut every process, tool, or step that can't survive interrogation. This is where the real savings appear, not in optimization.
  • Simplify third: Compress what survives deletion to its minimum viable form. No extra fields, no redundant approvals, no reports nobody reads.
  • Automate last: Only after the first three steps, route simplified work through tools. Automation is the reward for doing the hard work, not the substitute for it.

Automating before deleting is the most common ops mistake I see at $10M–$100M companies. You end up with a fast version of the wrong thing. A client inheriting a 47-step onboarding workflow doesn't need Zapier. They need to ask which of those 47 steps should exist at all. That interrogation usually kills 20 of them before a single line of automation gets written.

Operating principle: We don't install. We don't add. We cut. That's the OIL posture before any improvement work starts.

The StackOS Framework applies this same sequence to SaaS audits: interrogate every subscription, delete what can't justify its seat cost, simplify what remains, then automate billing and access controls. A mobile mechanic business eliminated Jobber Grow plan ($199/mo, $2,388/yr) and recovered approximately $1,500/yr after running OIL against their field ops stack. (OAG receipt: mobile_mechanic.replaced_tool, mobile_mechanic.savings)

What Lean Six Sigma Actually Is

Lean Six Sigma combines Toyota's Lean manufacturing principles (waste elimination) with Motorola's Six Sigma statistical process control (defect reduction). The synthesis was formalized in the late 1990s and became a standard certification track for manufacturing, logistics, and healthcare operations. [1]

  1. Define: Scope the problem and identify what customers care about.
  2. Measure: Establish a statistical baseline using historical process data.
  3. Analyze: Identify root causes of defects and variance.
  4. Improve: Test and implement solutions that reduce defect rates.
  5. Control: Install monitoring systems to hold the gains.

Certification tiers run from White Belt through Master Black Belt. A full DMAIC project typically runs three to six months with a dedicated improvement team. [1] Lean Six Sigma targets the 8 wastes (TIMWOODS: Transport, Inventory, Motion, Waiting, Overproduction, Overprocessing, Defects, Skills) and a defect rate approaching 3.4 per million opportunities at the Six Sigma level. [2] Both require clean historical data and stable, documented processes to measure against.

That last requirement is the point where most lower-middle-market operations fall out of scope. If your processes aren't documented, there's no baseline to measure. You're not ready for DMAIC. You're in OIL territory. See the Lean Six Sigma glossary entry for a deeper breakdown of belt tiers and project types.

Where Lean Six Sigma Breaks for Lower-Middle-Market Companies

I've spent a decade running operations at Amazon, International Paper, Spirit Halloween, Maersk, and Levi Strauss, across roughly $3B+ in operational impact. (OAG receipt: cedric.career_summary) The environments where Lean Six Sigma works best share three traits: documented processes, dedicated improvement staff, and time. Most $10M–$50M companies have none of those three.

  • Most $10M–$50M companies don't have a continuous improvement team. The owner or one ops lead is the improvement team.
  • DMAIC requires statistical baselines. If your processes aren't documented yet, there's nothing to measure against.
  • Belt certification costs and training timelines pull operators away from execution at exactly the wrong moment.
  • Lean Six Sigma assumes the process worth improving should stay. It doesn't answer the delete question.
  • A workforce of approximately 500 associates operating on manual systems (OAG receipt: spirit_halloween.headcount) needs deletion first. A Six Sigma project on a sticky-note system adds overhead without clearing the root problem.

This isn't a criticism of Lean Six Sigma. It's a scope problem. Lean Six Sigma is a precision instrument for stable systems. Using it on an undocumented, over-tooled operation is like calibrating a scale before deciding whether you need a scale at all. The operational waste glossary breaks down where each waste type shows up in lower-middle-market stacks specifically.

Operating principle: You can't optimize your way out of a process that shouldn't exist.

The Deletion Problem: What Each Framework Handles and What It Skips

This is the core difference between OIL and Lean Six Sigma. Neither Lean nor Six Sigma opens with a hard question about whether the work should exist. Lean targets waste categories inside a process. Six Sigma targets variance within a process. Both assume the process deserves to exist. OIL doesn't make that assumption.

  • Lean targets the 8 TIMWOODS waste categories. It asks how to run the process better.
  • Six Sigma targets variance and defect rates. It asks how to make the process more consistent.
  • OIL's Interrogate step asks whether the process should run at all. OIL's Delete step removes it if the answer is no. No measurement project required.
  • This matters most when operators inherit undocumented or over-automated operations. You can't reduce variance in a workflow that survives only because nobody questioned it.

A sales team running Salesforce Sales Cloud Enterprise at roughly $2,000/yr per seat doesn't need a Six Sigma project on their CRM usage patterns. They need an interrogation of whether that seat cost is justified per rep. After running OIL, one client dropped to a replacement that saved approximately $1,100/yr per seat. (OAG receipt: jps.replaced_tool, jps.savings) That's deletion, not optimization.

For more on where operational excellence frameworks diverge on this question, see the glossary entry. The short version: excellence frameworks disagree on what counts as waste. OIL's answer is blunter than most.

OIL vs Lean Six Sigma: Side-by-Side Comparison

The table below compares the two frameworks across the dimensions that matter most for operators deciding which to apply and when.

Dimension OIL Framework Lean Six Sigma
Core sequence Interrogate, Delete, Simplify, Automate Define, Measure, Analyze, Improve, Control (DMAIC)
Primary question Should this work exist at all? How do we reduce waste and variance in this work?
Prerequisite Willingness to delete; no documentation required Documented, stable processes with measurable baselines
Typical time to first decision Days to weeks Three to six months per DMAIC project [1]
Ideal company size $10M–$100M, lean ops teams Enterprise, 500+ employees, dedicated improvement staff
Certification required? No Yes (White Belt through Master Black Belt)
Handles the delete question? Yes, explicitly No
Handles variance reduction? Indirectly (via Simplify) Yes, statistically
Best phase of company Pre-systemization, cleanup, stack audit Post-systemization, scale optimization
OAG engagement fit Core method in every Axis Method engagement Referenced for post-OIL improvement phases where warranted

When to Use Lean Six Sigma, When to Use OIL, and When to Use Both

The frameworks aren't mutually exclusive. The question is sequencing, and sequencing depends on where your operation actually sits.

  • Use Lean Six Sigma when: You have stable, documented processes and need to reduce variance at scale. Enterprise manufacturing, large logistics networks, and healthcare operations with compliance requirements are the natural fit. If you can answer "what's your current defect rate?" with a number, you're ready for DMAIC.
  • Use OIL when: You're deciding what stays before you decide how to improve it. Early systemization, cleanup before a technology implementation, or any situation where an operator inherits an undocumented stack. If your first question is "what are we even doing here?", start with Interrogate.
  • Use both when: OIL's Delete and Simplify steps clear the ground. A Lean approach to what remains is legitimate and often valuable. The order still matters: OIL first, Lean second.

I've seen operators try to run DMAIC on a process that OIL would have deleted in forty minutes. The result is a well-measured process that shouldn't exist, staffed by people trained to defend it. That's not improvement. That's institutional waste with a certificate attached.

The principles do their work; the labels do not. Pick the tool that fits the phase, not the credential. For a full breakdown of how OAG sequences these decisions inside a multi-month engagement, see the Axis Method page.

How OAG Applies OIL Inside an Operations Architect Engagement

Every Operations Architect engagement (industry term: fractional COO) opens with the Axis Method's Diagnose stage. Diagnose is OIL-driven. We run Interrogate against every documented process before stabilizing anything. That interrogation surfaces the waste that would otherwise get automated, documented, or handed off to a new hire.

  • Diagnose: OIL-driven audit of every process and tool in scope.
  • Stabilize: Fix what remains after deletion so it runs without daily intervention.
  • Document: Write the system down in a form your team can run without us.
  • Hand-off: Transfer the documented, stable system to your ops lead within 90 days.
  • Compound: Build on the cleared ground. This is where Lean principles become relevant for what remains.

Engagement pricing runs $3,000–$7,500 per month, multi-month embedded. We architect the system, document it, and hand it back to your team. The hand-off is the deliverable. If we're still essential at month twelve, we did our job wrong.

The result: clients stop paying to run the wrong processes faster. That's not a phrasing choice. It's the literal outcome when automation precedes interrogation. A workforce-management stack costing between $48,000 and $96,000 per year (UKG, ADP, Dayforce, Kronos) running for approximately 500 employees can be replaced at $75/month after OIL clears the requirement bloat. (OAG receipt: spirit_halloween.system_cost, spirit_halloween.headcount) No Six Sigma project surfaces that. Interrogation does.

If you want a self-serve starting point before committing to a full engagement, the StackOS Framework PDF ($29) includes an OIL audit template you can run on a Saturday. It won't replace a full Diagnose stage, but it will tell you whether you're ready for one. I run Obsidian Axis Group on $74/month total. (OAG receipt: oag.monthly_run_cost) That number exists because OIL ran on the business before any tool got a subscription.

Sources

  1. American Society for Quality. "What Is Lean Six Sigma?" ASQ, n.d. https://asq.org/quality-resources/lean.
  2. iSixSigma. "Six Sigma DMAIC Roadmap." iSixSigma, n.d. https://www.isixsigma.com/dmaic/.

OAG receipts cited

  • cedric.career_summary
  • oag.monthly_run_cost
  • spirit_halloween.headcount
  • spirit_halloween.system_cost
  • jps.replaced_tool
  • jps.savings
  • mobile_mechanic.replaced_tool
  • mobile_mechanic.savings

Frequently asked

What is the OIL Framework?

OIL stands for Interrogate, Delete, Simplify, Automate. It's a fixed-sequence protocol OAG runs at the start of every Operations Architect engagement. The sequence is non-negotiable: you interrogate each process first to decide whether it should exist, delete what can't justify itself, simplify what survives, and only then automate. The order matters because automating before deleting produces a fast version of the wrong thing. OIL is designed for $10M–$100M operators who need decisions in days, not a certification cycle that runs months.

How is the OIL Framework different from Lean Six Sigma?

Lean Six Sigma improves what exists. OIL decides what should exist at all. Lean targets the 8 TIMWOODS waste categories inside a process. Six Sigma targets variance and defect rates within a process. Neither opens with a hard question about whether the process should run. OIL's Interrogate and Delete steps do exactly that, with no measurement baseline required. Lean Six Sigma also requires documented, stable processes and typically runs three to six months per DMAIC project. OIL can be completed in days on undocumented operations. The two frameworks can work together; OIL clears the ground, Lean optimizes what remains.

What does 'Interrogate' mean in the OIL Framework?

Interrogate is the first step in OIL. Before you touch how a process works, you ask whether it should work at all. That means challenging the reason the process exists, who requested it, what would break if it stopped, and whether the answer to that last question is actually a problem worth solving. Most teams skip interrogation because it's uncomfortable and because the process has been running long enough that people assume it matters. Interrogation is where the most waste gets found, not in the optimization stages that follow. If interrogation can't produce a clear justification, the process is a candidate for deletion.

Is Lean Six Sigma worth it for a company under $50 million in revenue?

In most cases, no, not as a starting framework. Lean Six Sigma requires documented, stable processes, clean historical data, and either a dedicated improvement team or an operator willing to invest months in certification and project execution. Most companies under $50M in revenue don't have those conditions. Their processes aren't fully documented, their improvement team is one person, and they can't absorb a three-to-six month project cycle. That doesn't mean Lean principles are useless at that size. Once OIL clears undocumented or unjustified processes and what remains is stable, applying Lean thinking to what survives is legitimate and often valuable. The sequencing is the issue, not the methodology.

What is DMAIC and how does it compare to OIL?

DMAIC stands for Define, Measure, Analyze, Improve, Control. It's the core execution cycle in Lean Six Sigma. You define the problem scope, measure the current state with statistical baselines, analyze root causes, implement improvements, and install controls to hold the gains. DMAIC assumes the process worth improving should stay and that you have enough historical data to measure against. OIL doesn't make either assumption. OIL's Interrogate step questions existence; DMAIC's Define step scopes improvement. OIL's Delete step removes; DMAIC has no equivalent step. For operators with undocumented or chaotic systems, OIL creates the conditions DMAIC eventually needs.

Can I apply the OIL Framework without hiring a consultant?

Yes. The StackOS Framework PDF ($29) includes an OIL audit template built for self-serve execution. You can run it on a Saturday against one process, one tool category, or your full ops stack. It won't replace the Diagnose stage inside a full Operations Architect engagement, but it gives you a structured sequence to follow without outside help. The main place self-serve OIL breaks down is the Interrogate step. Most operators are too close to their own processes to ask the hard questions without someone pushing back. That's the gap a full engagement fills, not the framework itself.

Does OAG use Lean Six Sigma in its Operations Architect engagements?

OAG doesn't run DMAIC projects as a standard engagement component. Every Operations Architect engagement opens with the Axis Method's Diagnose stage, which is OIL-driven. After OIL clears undocumented or unjustified processes, Lean principles can apply to what remains in the Compound stage, but that's operator-directed, not a packaged deliverable. The Axis Method runs Diagnose, Stabilize, Document, Hand-off, and Compound. The hand-off is the deliverable: a documented, stable system your team can run without OAG present. That's a different outcome than what a Lean Six Sigma project team delivers, which is typically a report and a control plan.

Talk through it.

If any of this is applicable to where you are, book a 30-minute scoping call. No pitch deck.

Book a call →