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 IBIS | ![]() Operations Change Analysis | ![]() Decision Making Force Field Analysis |
|---|---|---|---|---|
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. | IBIS structures thinking about complex questions as a sequence of issues, ideas, and arguments. The method keeps discussions open without forcing them into premature consensus. | For a deviation after a change, the method isolates the influence of the altered condition. It narrows down which differences are relevant and which are just accompanying noise. | In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 1-2 h | 1-3 h | 45-120 min | 45-90 min |
Participantsdifferent | 1-8 | 2-8 | 2-6 | 3-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Concept Map, Relationship Labels, Knowledge Gaps | Issue Map, Positions, Argument Notes | Change Matrix, Cause Hypotheses, Validation Questions, Action List | Force Field Map, Change Levers, Risk Notes |
Tagsno overlap | KnowledgeConceptsMappingSensemaking | RationaleKnowledgeDecision | ChangeRoot causeTroubleshootingComparison | ChangeDecisionStrategy |



