View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Delivery RAID Log |  Domain Modeling EventStorming |  Facilitation Decision Jam |
|---|---|---|---|
Purposedifferent | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | 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. | 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. |
Complexitydifferent | Low | Medium | Low |
Timedifferent | 30 min Setup, dann laufend | 2-8 h | 60-90 min |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 5-12 | 4-10 |
Formatdifferent | Async | Workshop | Workshop |
Outputdifferent | RAID Log, Status Report Source | Event Timeline, Ubiquitous Language, Boundaries, Open Questions | Problem Cluster, Prioritized Challenge, Experiment |
Tagsno overlap | RiskTrackingStakeholdersGovernance | Domain-Driven DesignEventsDiscoveryWorkshop | FacilitationDecisionProblem solvingWorkshop |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
