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 |  Engineering Hypothesis-Driven Troubleshooting |  Systems Thinking Intervention Mapping |
|---|---|---|---|
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. | When systems fail unexpectedly, spontaneous attempts often produce more noise than insight. Hypothesis-driven Troubleshooting translates symptoms into testable assumptions and makes troubleshooting learnable. | Intervention Mapping translates a need for change into a planned, evaluable program. The method connects target group, determinants, actions, and measurement into a traceable chain. |
Complexitydifferent | Medium | Medium | High |
Timedifferent | 1-2 h | 30-240 min | 1-5 Tage |
Participantsdifferent | 1-8 | 1-6 | 4-12 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Concept Map, Relationship Labels, Knowledge Gaps | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Logic Model, Change Objectives, Intervention Components, Evaluation Plan |
Tagsno overlap | KnowledgeConceptsMappingSensemaking | TroubleshootingProblem solvingDiagnosis | ChangeSystems thinkingCapability |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
