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 Architecture Decision Record |  Operations 8D Problem Solving |  Architecture C4 Model |  Operations 5 Whys |
|---|---|---|---|---|
Purposedifferent | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | 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. | The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. | 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 | High | Low | Low |
Timedifferent | 15-45 min | 1-6 Wochen | 1-4 h | 15-30 min |
Participantsdifferent | 1-3 | 4-10 | 1-5 | 2-6 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | 8D Report, Containment Plan, Root Cause Evidence, Corrective Action Plan | Context Diagram, Container Diagram, Component Diagram | Root cause notes, Countermeasures |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | QualityProblem solvingRoot cause | ArchitectureCommunicationVisualization | Root causeIncidentLeanProblem solving |