Asks its way step by step to a controllable cause and stops only once an effective countermeasure is within reach.
Core question: Which controllable cause behind the symptom can the team fix with a concrete countermeasure?
Analysis methodMethod form: Analysis method. Describes how this method is used in practice.LowComplexity: low. Estimates preparation, facilitation effort, and method confidence needed.WorkshopFormat: workshop. Shows whether the method works in a workshop, asynchronously, or both.
15-30 min
2-6
Details
OperationsCategory: Operations. Describes the method's domain of use.
Condenses problem, analysis, countermeasures, and follow-up onto one sheet and forces joint analysis.
Core question: Which gap between current and target condition is evidenced, and which countermeasure will we test first?
Operating practiceMethod form: Operating practice. Describes how this method is used in practice.MediumComplexity: medium. Estimates preparation, facilitation effort, and method confidence needed.Workshop + asyncFormat: workshop or async. Shows whether the method works in a workshop, asynchronously, or both.
45-90 min
2-5
Details
FacilitationCategory: Facilitation. Describes the method's domain of use.
Sorts problems, reframes the top issue, and derives experiments that quickly turn frustration into movement.
Core question: Which most important problem will we address with which solution as the next experiment?
Facilitation methodMethod form: Facilitation method. Describes how this method is used in practice.LowComplexity: low. Estimates preparation, facilitation effort, and method confidence needed.WorkshopFormat: workshop. Shows whether the method works in a workshop, asynchronously, or both.
60-90 min
4-10
Details
OperationsCategory: Operations. Describes the method's domain of use.
Clarifies workflows, data, causes, and improvements by framing the situation, analyzing the problem with is/is not, and planning risks and actions.
Core question: Do we need situation appraisal, cause analysis, a decision or safeguards for a plan?
Analysis methodMethod form: Analysis method. Describes how this method is used in practice.HighComplexity: high. Estimates preparation, facilitation effort, and method confidence needed.Workshop + asyncFormat: workshop or async. Shows whether the method works in a workshop, asynchronously, or both.
2-8 h
2-8
Details
InnovationCategory: Innovation. Describes the method's domain of use.
Clarifies ideas, open questions, and testable next steps by framing the contradiction, identifying improving and worsening factors, and checking feasibility.
Core question: How can we improve one property without sacrificing the other required property?
Analysis methodMethod form: Analysis method. Describes how this method is used in practice.HighComplexity: high. Estimates preparation, facilitation effort, and method confidence needed.Workshop + asyncFormat: workshop or async. Shows whether the method works in a workshop, asynchronously, or both.
1-4 h
2-8
Details
OperationsCategory: Operations. Describes the method's domain of use.
Separates events, evidence, confirmed causes, and fitting actions so analysis does not turn into blame-finding.
Core question: Which evidenced system causes must change so this or a similar event does not recur?
Analysis methodMethod form: Analysis method. Describes how this method is used in practice.MediumComplexity: medium. Estimates preparation, facilitation effort, and method confidence needed.Workshop + asyncFormat: workshop or async. Shows whether the method works in a workshop, asynchronously, or both.
1-4 h
3-8
Details
OperationsCategory: Operations. Describes the method's domain of use.
Coordinates team, immediate actions, root cause analysis, and prevention across eight steps to a verified solution.
Core question: How will we safely contain a material problem, permanently remove verified occurrence and detection causes, and prevent similar cases?
Process modelMethod form: Process model. Describes how this method is used in practice.HighComplexity: high. Estimates preparation, facilitation effort, and method confidence needed.Workshop + asyncFormat: workshop or async. Shows whether the method works in a workshop, asynchronously, or both.
1-6 Wochen
4-10
Details
EngineeringCategory: Engineering. Describes the method's domain of use.
Frames symptoms as hypotheses, prioritizes tests by information value, and records diagnosis and evidence.
Core question: Which competing hypothesis best explains all observed signals, and which safe test discriminates among them most strongly?
Analysis methodMethod form: Analysis method. Describes how this method is used in practice.MediumComplexity: medium. Estimates preparation, facilitation effort, and method confidence needed.Workshop + asyncFormat: workshop or async. Shows whether the method works in a workshop, asynchronously, or both.
30-240 min
1-6
Details
InnovationCategory: Innovation. Describes the method's domain of use.
Makes trade-off conflicts explicit, abstracts them into solution principles, and condenses testable concepts from them.
Core question: Which parameter should improve, which one worsens as a result, and how can the underlying physical demand be separated without compromise?
Analysis methodMethod form: Analysis method. Describes how this method is used in practice.MediumComplexity: medium. Estimates preparation, facilitation effort, and method confidence needed.WorkshopFormat: workshop. Shows whether the method works in a workshop, asynchronously, or both.