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 |  Architecture Risk Storming |  Architecture Architecture Decision Record |
|---|---|---|---|---|
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. | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. | 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 | Low | Medium | Low | Low |
Timedifferent | 30 min Setup, dann laufend | 2-8 h | 60-90 min | 15-45 min |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 5-12 | 4-12 | 1-3 |
Formatdifferent | Async | Workshop | Workshop | Async |
Outputdifferent | RAID Log, Status Report Source | Event Timeline, Ubiquitous Language, Boundaries, Open Questions | Annotated Diagram, Prioritized Risk List, Action Backlog | ADR File, Decision Log, Rationale |
Tagsno overlap | RiskTrackingStakeholdersGovernance | Domain-Driven DesignEventsDiscoveryWorkshop | RiskArchitectureWorkshopValidation | ArchitectureRationaleDocumentationGovernance |