Six Sigma — Intermediate

Define phase tools — the Project Charter and SIPOC

Applying Fundamentals' Define-phase introduction to specific tools: the Project Charter formally documents the project's scope, goals, timeline, and team, functioning as the agreed-upon reference point defining what the project is (and isn't) meant to address — preventing scope drift as the project progresses. SIPOC (Suppliers, Inputs, Process, Outputs, Customers) provides a high-level process map used early in Define to establish shared understanding of the process boundaries and key stakeholders before diving into detailed measurement — both tools exist to ensure the entire team shares a clear, common understanding of the problem and process before investing effort in the more detailed phases that follow.

Measure phase tools — data collection and process capability

Building on Fundamentals' Measure-phase introduction: operational definitions (precise, unambiguous definitions of what's being measured and how — ensuring different people measuring the same thing produce consistent results) and a data collection plan (specifying what data, how much, and how it will be gathered) precede actual measurement, since poorly defined measurement undermines everything built on top of it. Process capability analysis (comparing actual process performance against specification limits, often expressed through capability indices) establishes whether a process, as currently operating, can reliably meet requirements — directly connecting to Fundamentals' Six Sigma statistical target, since process capability analysis is how a process's actual sigma level gets calculated.

Analyze phase tools — root cause identification

Extending Fundamentals' Measure-before-Analyze principle: common Analyze-phase tools include the fishbone/Ishikawa diagram (organizing potential causes of a problem into categories — commonly People, Process, Equipment, Materials, Environment, and Measurement — to structure root-cause brainstorming rather than leaving it unstructured) and the 5 Whys (repeatedly asking "why" a problem occurs, typically five times, to move past surface-level symptoms toward genuine root causes). These tools exist specifically to structure root-cause analysis around the Measure phase's actual data, avoiding the assumption-based root-cause guessing Fundamentals warns against.

Improve phase — solution development grounded in analysis

The Improve phase develops and tests solutions specifically targeting the root causes identified in Analyze — genuinely effective Six Sigma practice tests proposed solutions on a small scale (a pilot) before full implementation, verifying the solution actually addresses the measured problem before committing to broader rollout. This pilot-before-scaling discipline connects to the same evidence-based principle running throughout DMAIC: claims of improvement should be substantiated by data, not simply implemented based on confidence that a solution should work.

Control phase — sustaining improvement over time

Building on Fundamentals' Control-phase introduction: control charts (tracking process performance over time against statistically-derived control limits, distinguishing normal common-cause variation from a genuine special-cause signal requiring investigation — directly applying Fundamentals' variation-type distinction) and a Control Plan (documenting the ongoing monitoring, responsibilities, and response procedures needed to sustain the improvement) are the primary Control-phase tools. Without genuine Control-phase discipline, process improvements frequently regress toward prior performance over time as initial attention fades — Control exists specifically to prevent this regression through sustained, structured monitoring rather than a one-time fix followed by disengagement.