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 Concept Mapping |  Decision Making Red Teaming |
|---|---|---|---|---|
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. | 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. | For strategic decisions with high reach, agreement and gut feeling are often not enough. Red teaming brings deliberate opposition into the situation and tests where a plan breaks under real counterarguments. |
Complexitydifferent | Medium | Medium | Medium | High |
Timedifferent | 1-3 h | 1-3 Wochen vom Draft bis zur Entscheidung | 1-2 h | 1-4 h |
Participantsdifferent | 3-12 | 3-20 Reviewer | 1-8 | 3-8 |
Formatdifferent | Workshop | Async | Workshop + async | Workshop |
Outputdifferent | Knowledge Map, Critical Knowledge Areas, Transfer Plan | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Concept Map, Relationship Labels, Knowledge Gaps | Challenge Findings, Risk Register, Mitigation Plan |
Tagsno overlap | KnowledgeMappingRisk | ArchitectureDecisionAsyncGovernance | KnowledgeConceptsMappingSensemaking | RiskDecisionSensemaking |