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 |  Product Discovery Opportunity Solution Tree |  Knowledge Modeling Event Modeling |
|---|---|---|---|
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. | When discovery keeps swinging between goals, ideas, and learning loops, it creates clear steering logic. It connects the desired outcome, opportunities, and experiments into a legible structure. | Event Modeling connects business workflows with commands, events, and views into one coherent mental model. It helps design behavior, UI, and technical slices from the same underlying logic. |
Complexitydifferent | Low | Medium | Medium |
Timedifferent | 15-45 min | 1-2 h Setup, laufend | 2-6 h |
Participantsdifferent | 1-3 | 2-6 | 2-8 |
Formatdifferent | Async | Workshop + async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Opportunity Solution Tree, Experiment Backlog, Learning Log | Event Model, UI Flow, Commands, Read Models |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | DiscoveryOutcomesExperimentsOpportunity | EventsBlueprintDomain-Driven DesignBehavior |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
