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 Systems Mapping |  Agile Acceptance Criteria Workshop |  Agile Example Mapping |  Systems Thinking Intervention Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | When a story needs clear checkpoints before implementation, it sharpens expectation and scope together. It sorts work by value, risk, and delivery ability. The result is captured as Acceptance Criteria and a Story Update. | When a story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound. | 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 | Low | Low | High |
Timedifferent | 1-3 h | 20-40 min pro Story | 30-60 min | 1-5 Tage |
Participantsdifferent | 3-12 | 3-6 | 3-7 | 4-12 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | System Map, Dependencies, Leverage Points | Acceptance Criteria, Story Update | Example Map, Acceptance Criteria, Open Questions | Logic Model, Change Objectives, Intervention Components, Evaluation Plan |
Tagsno overlap | Systems thinkingMappingBoundariesChange | AgileRequirementsRefinementBehavior-Driven Development | Behavior-Driven DevelopmentRequirementsExamplesRefinement | ChangeSystems thinkingCapability |