View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Systems Thinking Leverage Points |  Architecture Architecture Decision Record |  Domain Modeling Context Map |  Architecture arc42 |
|---|---|---|---|---|
Purposedifferent | Leverage Points show exactly where interventions in a system produce a disproportionate effect. It draws relationships, patterns, and feedback loops. The result is captured as a leverage map and action strategy. | 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 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 | High | Low | Medium | Low |
Timedifferent | Half day | 15-45 min | 1-3 h | 1-2 Tage |
Participantsdifferent | 3-12 | 1-3 | 2-8 | 1-4 |
Formatdifferent | Workshop | Async | Workshop + async | Workshop + async |
Outputdifferent | Leverage Map, Action Strategy | ADR File, Decision Log, Rationale | Context Map, Integration Patterns, Boundary Notes | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | Systems thinkingChangeStrategy | ArchitectureRationaleDocumentationGovernance | Domain-Driven DesignBoundariesStrategy | ArchitectureDocumentationCommunication |