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 Knowledge Mapping |  Architecture arc42 |  Decision Making Red Teaming |
|---|---|---|---|---|
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. | 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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | 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 | Low | High |
Timedifferent | 1-2 h | 1-3 h | 1-2 Tage | 1-4 h |
Participantsdifferent | 1-8 | 3-12 | 1-4 | 3-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Concept Map, Relationship Labels, Knowledge Gaps | Knowledge Map, Critical Knowledge Areas, Transfer Plan | Architecture Document, Context View, Runtime View, Deployment View | Challenge Findings, Risk Register, Mitigation Plan |
Tagsno overlap | KnowledgeConceptsMappingSensemaking | KnowledgeMappingRisk | ArchitectureDocumentationCommunication | RiskDecisionSensemaking |