View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Facilitation Mind Mapping |  Architecture Architecture Decision Record |  Knowledge Modeling IBIS |  Architecture Request for Comments |
|---|---|---|---|---|
Purposedifferent | When a topic is still unclear and too many thoughts surface at once, Mind Mapping creates an open surface for ordering them. It makes connections, subtopics, and starting points visible without fixing them too early. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | 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. |
Complexitydifferent | Low | Low | Medium | Medium |
Timedifferent | 15-45 min | 15-45 min | 1-3 h | 1-3 Wochen vom Draft bis zur Entscheidung |
Participantsdifferent | 1-10 | 1-3 | 2-8 | 3-20 Reviewer |
Formatdifferent | Workshop + async | Async | Workshop + async | Async |
Outputdifferent | Mind Map, Topic Clusters, Open Questions | ADR File, Decision Log, Rationale | Issue Map, Positions, Argument Notes | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets |
Tagsno overlap | BrainstormingIdeasMappingStructureFacilitation | ArchitectureRationaleDocumentationGovernance | RationaleKnowledgeDecision | ArchitectureDecisionAsyncGovernance |