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 | ![]() Architecture Request for Comments | ![]() Decision Making Decision Rights Mapping | ![]() Decision Making Argument Mapping |
|---|---|---|---|---|
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. | 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. | In organizations with many stakeholders, it often blurs who actually decides and who is merely consulted. It separates options, evaluation criteria, and open risks. The result is captured as a Decision Rights matrix and an agreement. | When statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 1-3 h | 1-3 Wochen vom Draft bis zur Entscheidung | 90-180 min | 1-3 h |
Participantsdifferent | 2-8 | 3-20 Reviewer | 4-12 | 1-8 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop + async |
Outputdifferent | Issue Map, Positions, Argument Notes | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Decision Rights Matrix, Agreement | Argument Map, Evidence Gaps, Decision Rationale |
Tags1 shared | RationaleKnowledgeDecision | ArchitectureDecisionAsyncGovernance | DecisionGovernanceAlignmentResponsibility | SensemakingDecisionRationale |



