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 Knowledge Mapping |  Architecture Request for Comments |  Knowledge Modeling IBIS |  Knowledge Modeling Concept Mapping |
|---|---|---|---|---|
Purposedifferent | Knowledge Mapping makes knowledge, gaps, and transfer paths visible across a field. It fits when expertise should not just exist but also be findable and transferable. | 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. | 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. | 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. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 1-3 h | 1-3 Wochen vom Draft bis zur Entscheidung | 1-3 h | 1-2 h |
Participantsdifferent | 3-12 | 3-20 Reviewer | 2-8 | 1-8 |
Formatdifferent | Workshop | Async | Workshop + async | Workshop + async |
Outputdifferent | Knowledge Map, Critical Knowledge Areas, Transfer Plan | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Issue Map, Positions, Argument Notes | Concept Map, Relationship Labels, Knowledge Gaps |
Tagsno overlap | KnowledgeMappingRisk | ArchitectureDecisionAsyncGovernance | RationaleKnowledgeDecision | KnowledgeConceptsMappingSensemaking |