View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Delivery RAID Log | ![]() Operations A3 Problem Solving | ![]() Innovation TRIZ | ![]() Operations 5 Whys |
|---|---|---|---|---|
Purposedifferent | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together. | 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. | 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. |
Complexitydifferent | Low | Medium | High | Low |
Timedifferent | 30 min Setup, dann laufend | 45-90 min | 1-4 h | 15-30 min |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 2-5 | 2-8 | 2-6 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | RAID Log, Status Report Source | A3 Report, Action Plan, Root Cause Analysis | Contradiction Statement, Inventive Principles, Solution Concepts | Root cause notes, Countermeasures |
Tagsno overlap | RiskTrackingStakeholdersGovernance | LeanProblem solvingCoachingOperations | InnovationProblem solvingContradictionsCreativity | Root causeIncidentLeanProblem solving |



