View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Innovation Contradiction Analysis |  Operations 8D Problem Solving |  Architecture arc42 |  Operations Root Cause Analysis |
|---|---|---|---|---|
Purposedifferent | 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. | For an acute quality or delivery problem, the method structures immediate protection and root cause work together. It keeps the situation stable while the actual cause is investigated cleanly. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | 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 | Medium | High | Low | Medium |
Timedifferent | 60-120 min | 1-6 Wochen | 1-2 Tage | 1-4 h |
Participantsdifferent | 2-8 | 4-10 | 1-4 | 3-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Contradiction Statement, Abstraction Notes, Solution Principles, Concept Ideas | 8D Report, Containment Plan, Root Cause Evidence, Corrective Action Plan | Architecture Document, Context View, Runtime View, Deployment View | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan |
Tagsno overlap | ContradictionsInnovationProblem solving | QualityProblem solvingRoot cause | ArchitectureDocumentationCommunication | Root causeProblem solvingQualityIncident |