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 |  Decision Making Assumption Surfacing |
|---|---|---|---|
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. | 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 | Medium | Medium | Low |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 2-8 h | 45-90 min |
Participantsdifferent | 3-20 Reviewer | 5-12 | 2-8 |
Formatdifferent | Async | Workshop | Workshop + async |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Event Timeline, Ubiquitous Language, Boundaries, Open Questions | Assumption List, Critical Assumptions, Learning Plan |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | Domain-Driven DesignEventsDiscoveryWorkshop | AssumptionsRiskDecisionDiscovery |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
