View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Engineering Kanban |  Domain Modeling Bounded Context Canvas |  Systems Thinking Systems Mapping |  Systems Thinking Intervention Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | When a business context is still loosely outlined, it shapes language, responsibility, and integration space. It clarifies what belongs together and where a boundary needs to hold. | 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. | 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 | Medium | High |
Timedifferent | Ongoing | 1-3 h | 1-3 h | 1-5 Tage |
Participantsdifferent | 2-12 | 3-8 | 3-12 | 4-12 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Kanban board, WIP policies, Flow metrics | Context Canvas, Glossary, Integration Notes | System Map, Dependencies, Leverage Points | Logic Model, Change Objectives, Intervention Components, Evaluation Plan |
Tagsno overlap | FlowVisual managementDelivery | Domain-Driven DesignBoundariesModeling | Systems thinkingMappingBoundariesChange | ChangeSystems thinkingCapability |