View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Knowledge Modeling IBIS | ![]() Decision Making Decision Tree | ![]() Architecture Request for Comments |
|---|---|---|---|
Purposedifferent | IBIS structures thinking about complex questions as a sequence of issues, ideas, and arguments. The method keeps discussions open without forcing them into premature consensus. | For decisions with follow-on paths and dependencies, a linear comparison is often not enough. A Decision Tree shows how options branch under conditions and which consequences hang on each branch. | 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. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | 1-3 h | 30-90 min | 1-3 Wochen vom Draft bis zur Entscheidung |
Participantsdifferent | 2-8 | 1-6 | 3-20 Reviewer |
Formatdifferent | Workshop + async | Workshop + async | Async |
Outputdifferent | Issue Map, Positions, Argument Notes | Decision Tree, Option Map, Assumption List | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets |
Tags1 shared | RationaleKnowledgeDecision | DecisionTreeOptions | ArchitectureDecisionAsyncGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






