View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Facilitation Decision Jam |  Domain Modeling EventStorming |  Architecture arc42 |  Decision Making Assumption Surfacing |
|---|---|---|---|---|
Purposedifferent | When a decision is stuck, Decision Jam loosens the knot through structured separation of problem, idea, and selection. The format creates movement without jumping prematurely at the first seemingly elegant answer. | When a domain consists of many events, rules, and states, it creates a shared modeling space for the team. It bundles language, flows, and boundaries before domain knowledge fragments into siloed views. | 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. | Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 60-90 min | 2-8 h | 1-2 Tage | 45-90 min |
Participantsdifferent | 4-10 | 5-12 | 1-4 | 2-8 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Problem Cluster, Prioritized Challenge, Experiment | Event Timeline, Ubiquitous Language, Boundaries, Open Questions | Architecture Document, Context View, Runtime View, Deployment View | Assumption List, Critical Assumptions, Learning Plan |
Tagsno overlap | FacilitationDecisionProblem solvingWorkshop | Domain-Driven DesignEventsDiscoveryWorkshop | ArchitectureDocumentationCommunication | AssumptionsRiskDecisionDiscovery |