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 | ![]() Decision Making Argument Mapping | ![]() Operations Barrier Analysis | ![]() 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. | When statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on. | 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 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 | Medium | Low |
Timedifferent | 15-45 min | 1-3 h | 2-4 h | 15-30 min |
Participantsdifferent | 1-3 | 1-8 | 2-6 | 2-6 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | Argument Map, Evidence Gaps, Decision Rationale | Barrier Inventory, Failure Analysis per Barrier, Action Backlog | Root cause notes, Countermeasures |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | SensemakingDecisionRationale | Root causeSafetyIncident | Root causeIncidentLeanProblem solving |



