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 Request for Comments |  Domain Modeling EventStorming |  Facilitation Decision Jam |  Facilitation Consensus Workshop |
|---|---|---|---|---|
Purposedifferent | An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale. | 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. | When a group needs a solid decision without outvoting individual factions, a Consensus Workshop creates a negotiable common ground. It makes agreement, reservations, and open tensions discussable at the same time. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 2-8 h | 60-90 min | 1-3 h |
Participantsdifferent | 3-20 Reviewer | 5-12 | 4-10 | 5-30 |
Formatdifferent | Async | Workshop | Workshop | Workshop |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Event Timeline, Ubiquitous Language, Boundaries, Open Questions | Problem Cluster, Prioritized Challenge, Experiment | Consensus Clusters, Theme Titles, Priority Areas |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | Domain-Driven DesignEventsDiscoveryWorkshop | FacilitationDecisionProblem solvingWorkshop | FacilitationConsensusWorkshopAlignment |