View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Decision Making Assumption Surfacing | ![]() Knowledge Modeling Concept Mapping | ![]() Architecture arc42 | ![]() Knowledge Modeling Knowledge Mapping |
|---|---|---|---|---|
Purposedifferent | Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it. | 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. | 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. | 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. |
Complexitydifferent | Low | Medium | Low | Medium |
Timedifferent | 45-90 min | 1-2 h | 1-2 Tage | 1-3 h |
Participantsdifferent | 2-8 | 1-8 | 1-4 | 3-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Assumption List, Critical Assumptions, Learning Plan | Concept Map, Relationship Labels, Knowledge Gaps | Architecture Document, Context View, Runtime View, Deployment View | Knowledge Map, Critical Knowledge Areas, Transfer Plan |
Tagsno overlap | AssumptionsRiskDecisionDiscovery | KnowledgeConceptsMappingSensemaking | ArchitectureDocumentationCommunication | KnowledgeMappingRisk |



