View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Product Strategy Impact Mapping |  Domain Modeling Context Map |  Architecture Architecture Decision Record |
|---|---|---|---|
Purposedifferent | When a goal needs to be connected to several possible paths, it shows chains of impact instead of feature lists. It connects business goal, behavior change, and measures. | 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. | 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. |
Complexitydifferent | Medium | Medium | Low |
Timedifferent | 45-90 min | 1-3 h | 15-45 min |
Participantsdifferent | 3-8 | 2-8 | 1-3 |
Formatdifferent | Workshop | Workshop + async | Async |
Outputdifferent | Impact Map, Outcome Hypotheses, Delivery Options | Context Map, Integration Patterns, Boundary Notes | ADR File, Decision Log, Rationale |
Tagsno overlap | OutcomesStrategyBehaviorPlanning | Domain-Driven DesignBoundariesStrategy | ArchitectureRationaleDocumentationGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
