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 Risk Storming |  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. | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. | 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. |
Complexitydifferent | Medium | Low | Medium |
Timedifferent | 1-3 h | 60-90 min | 1-3 Wochen vom Draft bis zur Entscheidung |
Participantsdifferent | 2-8 | 4-12 | 3-20 Reviewer |
Formatdifferent | Workshop + async | Workshop | Async |
Outputdifferent | Issue Map, Positions, Argument Notes | Annotated Diagram, Prioritized Risk List, Action Backlog | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets |
Tagsno overlap | RationaleKnowledgeDecision | RiskArchitectureWorkshopValidation | ArchitectureDecisionAsyncGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
