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 | ![]() Systems Thinking Future Reality Tree | ![]() Architecture Architecture Decision Record | ![]() 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. | A Future Reality Tree shows how desired actions are meant to lead to a better system state. The method checks whether a path of change holds together logically before time flows into implementation. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | 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. |
Complexitydifferent | Medium | High | Low | Medium |
Timedifferent | 1-3 h | 2-4 h | 15-45 min | 1-2 h |
Participantsdifferent | 3-12 | 3-8 | 1-3 | 1-8 |
Formatdifferent | Workshop | Workshop | Async | Workshop + async |
Outputdifferent | Knowledge Map, Critical Knowledge Areas, Transfer Plan | Future Reality Tree, Negative Branches, Assumption List, Improved Injections | ADR File, Decision Log, Rationale | Concept Map, Relationship Labels, Knowledge Gaps |
Tagsno overlap | KnowledgeMappingRisk | Theory of ConstraintsSystems thinkingChange | ArchitectureRationaleDocumentationGovernance | KnowledgeConceptsMappingSensemaking |



