View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations A3 Problem Solving |  Innovation TRIZ |  Architecture arc42 |  Operations 5 Whys |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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 | Medium | High | Low | Low |
Timedifferent | 45-90 min | 1-4 h | 1-2 Tage | 15-30 min |
Participantsdifferent | 2-5 | 2-8 | 1-4 | 2-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | A3 Report, Action Plan, Root Cause Analysis | Contradiction Statement, Inventive Principles, Solution Concepts | Architecture Document, Context View, Runtime View, Deployment View | Root cause notes, Countermeasures |
Tagsno overlap | LeanProblem solvingCoachingOperations | InnovationProblem solvingContradictionsCreativity | ArchitectureDocumentationCommunication | Root causeIncidentLeanProblem solving |