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 |  Business Strategy Balanced Scorecard |  Domain Modeling Bounded Context Canvas |  Domain Modeling 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. | Balanced Scorecard translates strategy into a few interconnected perspectives and metrics. It holds impact, steering, and learning together in daily work instead of narrowing strategy down to financial figures. | When a business context is still loosely outlined, it shapes language, responsibility, and integration space. It clarifies what belongs together and where a boundary needs to hold. | 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. |
Complexitydifferent | Low | High | Medium | Medium |
Timedifferent | 15-45 min | Halber Tag bis mehrere Wochen | 1-3 h | 1-3 h |
Participantsdifferent | 1-3 | 4-12 | 3-8 | 2-8 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Balanced Scorecard, Strategic Measures, Initiative Map | Context Canvas, Glossary, Integration Notes | Context Map, Integration Patterns, Boundary Notes |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | StrategyMetricsExecution | Domain-Driven DesignBoundariesModeling | Domain-Driven DesignBoundariesStrategy |