methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Paper illustration for TRIZ
Innovation
TRIZ
Paper illustration for Contradiction Analysis.
Innovation
Contradiction Analysis
Paper illustration for Root Cause Analysis.
Operations
Root Cause Analysis
Purposedifferent
For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description.For technical contradictions or trade-offs, the method looks for solutions that resolve opposing requirements at the same time. It translates limits into an explicit picture of conflict that becomes workable. This produces not just compromises but more elegant principles.When a system should improve while another measure suffers as a result, the method makes the underlying conflict precisely formulable. It separates the desired effect from its side effect. This makes solutions possible that address the contradiction deliberately instead of half-heartedly.When a problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another.
Complexitydifferent
LowHighMediumMedium
Timedifferent
15-30 min1-4 h60-120 min1-4 h
Participantsdifferent
2-62-82-83-8
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Root cause notes, CountermeasuresContradiction Statement, Inventive Principles, Solution ConceptsContradiction Statement, Abstraction Notes, Solution Principles, Concept IdeasProblem Statement, Cause Hypotheses, Confirmed Causes, Action Plan
Tags1 shared
Root causeIncidentLeanProblem solving
InnovationProblem solvingContradictionsCreativity
ContradictionsInnovationProblem solving
Root causeProblem solvingQualityIncident
Add more methods