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 Context Map | ![]() Decision Making Delphi Method |
|---|---|---|---|
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 several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries. | When knowledge is distributed and direct dominance should be avoided, groups quickly fall under the sway of their opinion leaders. The Delphi Method gathers assessments iteratively and gradually brings expert judgments closer together. |
Complexitydifferent | Medium | Medium | High |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 1-3 h | 1-4 Wochen |
Participantsdifferent | 3-20 Reviewer | 2-8 | 6-30 Experten |
Formatdifferent | Async | Workshop + async | Async |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Context Map, Integration Patterns, Boundary Notes | Expert Forecast, Consensus Range, Assumption Notes |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | Domain-Driven DesignBoundariesStrategy | ForecastingExpertsDecisionStrategy |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






