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 | ![]() Decision Making Force Field Analysis | ![]() Systems Thinking Systems Mapping | ![]() Business Strategy Business Model Stress Test |
|---|---|---|---|---|
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. | 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. | 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. | A Business Model Stress Test checks how well a business model holds up under pressure and headwinds. It compares strengths, risks, market logic, and courses of action. The result is captured as a stress-test report and action plan per scenario. |
Complexitydifferent | Medium | Low | Medium | High |
Timedifferent | 1-3 h | 45-90 min | 1-3 h | Half day |
Participantsdifferent | 3-12 | 3-12 | 3-12 | 3-8 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Knowledge Map, Critical Knowledge Areas, Transfer Plan | Force Field Map, Change Levers, Risk Notes | System Map, Dependencies, Leverage Points | Stress Test Report, Action Plan per Scenario |
Tagsno overlap | KnowledgeMappingRisk | ChangeDecisionStrategy | Systems thinkingMappingBoundariesChange | StrategyBusiness modelRiskDiagnosis |



