View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Systems Thinking Intervention Mapping |  Engineering Kanban |  Systems Thinking Evaporating Cloud |  Systems Thinking Systems Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | When work sits in too many parallel streams, throughput suffers and no one sees the bottlenecks. Kanban makes the flow of work visible and limits overload so a system becomes calmer and more predictable. | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | 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. |
Complexitydifferent | High | Medium | Medium | Medium |
Timedifferent | 1-5 Tage | Ongoing | 60-120 min | 1-3 h |
Participantsdifferent | 4-12 | 2-12 | 2-8 | 3-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Logic Model, Change Objectives, Intervention Components, Evaluation Plan | Kanban board, WIP policies, Flow metrics | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | System Map, Dependencies, Leverage Points |
Tagsno overlap | ChangeSystems thinkingCapability | FlowVisual managementDelivery | Theory of ConstraintsAssumptionsSystems thinking | Systems thinkingMappingBoundariesChange |