View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Operations A3 Problem Solving | ![]() Domain Modeling Context Map | ![]() Architecture arc42 |
|---|---|---|---|
Purposedifferent | 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 several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries. | 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. |
Complexitydifferent | Medium | Medium | Low |
Timedifferent | 45-90 min | 1-3 h | 1-2 Tage |
Participantsdifferent | 2-5 | 2-8 | 1-4 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | A3 Report, Action Plan, Root Cause Analysis | Context Map, Integration Patterns, Boundary Notes | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | LeanProblem solvingCoachingOperations | Domain-Driven DesignBoundariesStrategy | ArchitectureDocumentationCommunication |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






