View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture arc42 |  Operations 5 Whys |  Operations Barrier Analysis |  Operations 8D Problem Solving |
|---|---|---|---|---|
Purposedifferent | 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. | For a risk that can only be managed through multiple layers of protection, the method examines the effectiveness of each barrier. It shows where safeguards are missing, too weak, or fail under real conditions. | 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. |
Complexitydifferent | Low | Low | Medium | High |
Timedifferent | 1-2 Tage | 15-30 min | 2-4 h | 1-6 Wochen |
Participantsdifferent | 1-4 | 2-6 | 2-6 | 4-10 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Architecture Document, Context View, Runtime View, Deployment View | Root cause notes, Countermeasures | Barrier Inventory, Failure Analysis per Barrier, Action Backlog | 8D Report, Containment Plan, Root Cause Evidence, Corrective Action Plan |
Tagsno overlap | ArchitectureDocumentationCommunication | Root causeIncidentLeanProblem solving | Root causeSafetyIncident | QualityProblem solvingRoot cause |