View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Domain Modeling Domain Context Map |  Architecture Architecture Decision Record |  Operations Root Cause Analysis |  Operations 5 Whys |
|---|---|---|---|---|
Purposedifferent | When a domain model and its associated contexts need to be thought through together, it creates a shared overview. It connects the business view and organizational boundary into a readable whole. | 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 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. | 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 | Low | Medium | Low |
Timedifferent | 1-3 h | 15-45 min | 1-4 h | 15-30 min |
Participantsdifferent | 3-10 | 1-3 | 3-8 | 2-6 |
Formatdifferent | Workshop | Async | Workshop + async | Workshop |
Outputdifferent | Domain Context Map, Boundary Notes, Ownership Map | ADR File, Decision Log, Rationale | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan | Root cause notes, Countermeasures |
Tagsno overlap | Domain-Driven DesignContextBoundaries | ArchitectureRationaleDocumentationGovernance | Root causeProblem solvingQualityIncident | Root causeIncidentLeanProblem solving |