The 16 questions
Distributed across five phases.
Each phase has its own answerable questions, a defined set of deliverables, and a tool kit refined over 1,000+ implementations. The framework is sequential but iterative: teams revisit earlier questions as understanding deepens.D
Phase 1 of 5
Questions 1-3
Define
Define exists to scope a high-payback project, identify the metrics that will measure success, and align senior leadership before the team commits months of effort. Without leadership sponsorship, project leaders typically stall against organizational resistance. The deliverable is an agreed Project Charter.
- Who is this project for, and why does it matter? Customers, business case, deliverables, and the metrics that will tell us we won.
- What is the process, and where does it start and end? Major process steps mapped, scope boundaries set, potential project spin-offs flagged for the queue.
- Who is involved, what is the priority order, and when is it done? Stakeholders identified, opportunities prioritized, team composition and timeline locked in. Kaizen feasibility assessed.
Deliverables
Project Charter / Contract. Primary and secondary metrics. VOC / VOB. Macro process flow. Stakeholder analysis. Kaizen plan if applicable.
Recommended Tools
IPO. SIPOC. Customer Interview. QFD. Cascading IPO. Flowchart. Pareto Charts. FMEA. Brainstorming. Gantt Chart. Stakeholder Analysis matrix.
M
Phase 2 of 5
Questions 4-7
Measure
Measure exists to characterize the current state of the process honestly. Most projects fail here, not for lack of statistical sophistication, but because the team did not validate that the measurement system itself was trustworthy before drawing baseline conclusions.
- What is the current state of the process? Is it constrained? A Current State Map of the work as it actually flows today, not as the procedure manual claims.
- How is the process measured, and is the measurement precise and accurate? Measurement System Analysis to expose gauge variation before it pollutes downstream analysis.
- What is the baseline, and is the process capable? Baseline metrics, specification limits, capability indices.
- What is the Cost of Poor Quality? COPQ in dollars. The number that converts process behavior into language finance can defend.
Deliverables
Current State Map. Measurement System Analysis. Process baseline. Capability study. COPQ.
Recommended Tools
Process Flow Diagram. Value Stream Map. Spaghetti Diagram. Constraint Map. OEE. Kaizen. MSA / Gauge R&R. Histogram. Run Charts. Control Charts. Box Plot. Sampling. Cpk study. dpm calculations.
A
Phase 3 of 5
Questions 8-10
Analyze
Analyze exists to find the actual root causes, not the convenient ones, not the politically acceptable ones. Often there is one primary cause driving most of the unwanted variation, and controlling or eliminating that one cause is all the project needs.
- Where is waste apparent, and where is the metric off-target or over-varying? Prioritized list of the 9 classic Lean wastes. Factors that move the mean. Factors that drive variation.
- What are the root causes? Causes verified statistically when the data permits, traced through cause-and-effect logic when it does not.
- What would benchmark or world-class performance look like? The aspirational state the team is moving toward, anchored to external reference points.
Deliverables
Prioritized waste list. Verified root causes. Benchmark target. Defined project goals.
Recommended Tools
5 Whys. FMEA. Cause and Effect Diagram. Affinity Diagrams. Pareto Analysis. Reality Tree. Regression. ANOVA. Correlation. DOE. T-tests. F-tests. Chi-Square tests. VSM. Waste Walk. Layout Design. Takt Time. 5S.
I
Phase 4 of 5
Questions 11-13
Improve
Improve exists to redesign the process to achieve improved capability. Brainstorm potential solutions, narrow to the ones worth testing, and prove they work in the real environment, not just in theory.
- How do we remove the cause? How do the inputs interact? Solutions that target the verified root cause. Input/output relationships understood, not assumed.
- Which improvements get implemented, are tests required, and what is the risk? Selected solutions, future state process, implementation plan with risk mitigation.
- Did the improved process meet the goal? Re-assessed capability against baseline. If the goal was not met, the team returns to Analyze.
Deliverables
Proposed solutions. Selected solutions. Future State process. Implementation plan. Re-assessed capability.
Recommended Tools
Brainstorming. Solution Grid. Pugh Matrix. Prioritization Matrix. DOE. Scatter Plots. Modeling. 5S. Visual Controls. Line Balancing. Single-Piece Flow. Pull / Kanban. Quick Changeover. TPM. Poka Yoke. Standard Work. FMEA. VSM. Hypothesis Testing. Confidence Intervals.
C
Phase 5 of 5
Questions 14-16
Control
Control exists to make the gain stick. Without an executable Control Plan and post-implementation monitoring, the process drifts back. The team finalizes documentation, hands off ownership, and signs off the project.
- How will the improvement be sustained? Control Plan with specific monitoring rules, escalation paths, and ownership.
- What is the validated benefit, and is it documented? Financial benefit verified by finance. Documented results. Scalable elements identified for replication.
- Has the team been recognized? Closure is a leadership behavior. Teams that are recognized for delivered improvement come back to the next project.
Deliverables
Control Plan. Validated financial benefits. Final report / A3. Project database entry. Recognition delivered.
Recommended Tools
Control Charts. Control Plans. Poka Yoke. RACI / Accountability Matrix. 5S Audit. COPQ Tracking. Financial Verification. A3. Communication Plan. Reward and Recognition Policies.