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 Systems Mapping |  Architecture Architecture Decision Record |  Systems Thinking Future Reality Tree |
|---|---|---|---|---|
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. | Systems Mapping arranges elements, relationships, and boundaries so a complex field becomes legible at a glance. The overview stabilizes the overall picture before detail work or steering begins. | 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. | 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. |
Complexitydifferent | Medium | Medium | Low | High |
Timedifferent | 1-3 h | 1-3 h | 15-45 min | 2-4 h |
Participantsdifferent | 3-12 | 3-12 | 1-3 | 3-8 |
Formatdifferent | Workshop | Workshop + async | Async | Workshop |
Outputdifferent | Knowledge Map, Critical Knowledge Areas, Transfer Plan | System Map, Dependencies, Leverage Points | ADR File, Decision Log, Rationale | Future Reality Tree, Negative Branches, Assumption List, Improved Injections |
Tagsno overlap | KnowledgeMappingRisk | Systems thinkingMappingBoundariesChange | ArchitectureRationaleDocumentationGovernance | Theory of ConstraintsSystems thinkingChange |