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 A3 Problem Solving |  Domain Modeling Domain Context Map |
|---|---|---|---|
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 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. | 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. |
Complexitydifferent | Low | Medium | Medium |
Timedifferent | 15-45 min | 45-90 min | 1-3 h |
Participantsdifferent | 1-3 | 2-5 | 3-10 |
Formatdifferent | Async | Workshop + async | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | A3 Report, Action Plan, Root Cause Analysis | Domain Context Map, Boundary Notes, Ownership Map |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | LeanProblem solvingCoachingOperations | Domain-Driven DesignContextBoundaries |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
