Practical continuous improvement
Lean Six Sigma tools explained: choose the question first
Lean and Six Sigma offer ways to investigate flow, customer requirements and variation. CI Tools supports practical documentation and analysis across those activities. A tool is useful when its inputs and assumptions fit the question; a collection of completed worksheets is not itself an improvement.
Original CI Tools learning material · Fictional examples · Free to read
Define the need and the boundaries
A CTQ tree translates a customer need into measurable characteristics and operational definitions. For example, a fictional scheduling team turns “a reliable appointment” into a defined confirmation measure, with an explicit population, unit and collection rule. An arbitrary target is not a customer requirement until it has been justified.
A Project Charter records the problem and scope. SIPOC describes the wider process boundary. These answer different questions from a detailed Flowchart, which follows activities and decisions inside that boundary. Use the broader view first when teams disagree about where the work starts or ends.
Measure the process before ranking its problems
Time Study separates observed processing, waiting, interruptions and rework. Value Stream Mapping connects end-to-end flow with demand and queue assumptions. Neither should replace direct observation with an unverified ideal-state estimate.
Pareto Analysis ranks consistently defined categories by a common count or impact unit. It can show where the recorded burden is concentrated, but does not explain why it happens. Keep categories mutually understandable and inspect the underlying cases before treating the largest bar as a proven root cause.
Investigate possible causes with evidence
Fishbone diagrams organize possible explanations. 5 Whys follows a focused line of inquiry. The Root Cause Analysis Builder can retain branching hypotheses, evidence, validation and contradictory findings. Those structures help a team distinguish an idea from a checked explanation.
Suppose fictional orders needing clarification are disproportionately missing a specification field. Review the affected cases and compare an appropriate group without the delay. Test whether the proposed field change alters the outcome. Do not label a person or department the root cause simply because it appears at the end of a chain of “whys.”
Use statistical and risk tools within their limits
Control Charts examine comparable observations in time order against a reviewed baseline. Process Capability compares a supported process model with explicit specifications; it should not manufacture a capability result when stability, sampling or distribution assumptions are unsupported.
FMEA reviews possible failure modes and controls before a changed method is introduced. Its scores support a structured discussion, not a universal probability or an automatic safety decision. Local operational and safety review still matters.
Document the method and the response
Standard Work explains the tested sequence and quality points. A Control Plan states what is measured, who checks it and what response is required. Monitoring, Reaction, Audit and Training checklists add detail when the work needs it. An A3 can connect the overall problem, evidence, countermeasures and follow-up.
Start with one question and follow its evidence to the next tool. The chooser offers explained recommendations, and each guide includes interface-specific steps and fictional examples. Tool access is free during beta after email verification; guides remain available without an account. Keep your editable .citools files on your computer.
Further learning
- ASQ: Quality tools and templates
- ASQ: Cause analysis tools
- NIST: Process monitoring and control
- NIST: Process capability
- Lean Enterprise Institute: Standardized Work
Independent educational resources, not endorsements of CI Tools.