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 Concept Mapping | ![]() Knowledge Modeling IBIS | ![]() Architecture Request for Comments |
|---|---|---|---|
Purposedifferent | Concept Mapping arranges terms and relationships in a network that makes subject-matter connections tangible. It fits when a topic needs to be understood structurally rather than linearly. | 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. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | 1-2 h | 1-3 h | 1-3 Wochen vom Draft bis zur Entscheidung |
Participantsdifferent | 1-8 | 2-8 | 3-20 Reviewer |
Formatdifferent | Workshop + async | Workshop + async | Async |
Outputdifferent | Concept Map, Relationship Labels, Knowledge Gaps | Issue Map, Positions, Argument Notes | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets |
Tagsno overlap | KnowledgeConceptsMappingSensemaking | RationaleKnowledgeDecision | ArchitectureDecisionAsyncGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






