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 Example Mapping | ![]() Systems Thinking Intervention Mapping | ![]() Agile Specification by Example |
|---|---|---|---|---|
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 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. | When business rules need to become precise, it ties language, example, and test together. It sorts work by value, risk, and delivery ability. The result is captured as an Example Table and Acceptance Tests. |
Complexitydifferent | Medium | Low | High | Medium |
Timedifferent | 1-3 h | 30-60 min | 1-5 Tage | 60-90 min pro Feature |
Participantsdifferent | 3-12 | 3-7 | 4-12 | 3-6 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | System Map, Dependencies, Leverage Points | Example Map, Acceptance Criteria, Open Questions | Logic Model, Change Objectives, Intervention Components, Evaluation Plan | Example Table, Acceptance Tests |
Tagsno overlap | Systems thinkingMappingBoundariesChange | Behavior-Driven DevelopmentRequirementsExamplesRefinement | ChangeSystems thinkingCapability | AgileRequirementsExamplesBehavior-Driven Development |



