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 | ![]() Agile Example Mapping | ![]() Decision Making Force Field Analysis | ![]() Agile Specification by Example |
|---|---|---|---|---|
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 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. | 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. | 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 | High | Low | Low | Medium |
Timedifferent | 1-5 Tage | 30-60 min | 45-90 min | 60-90 min pro Feature |
Participantsdifferent | 4-12 | 3-7 | 3-12 | 3-6 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Logic Model, Change Objectives, Intervention Components, Evaluation Plan | Example Map, Acceptance Criteria, Open Questions | Force Field Map, Change Levers, Risk Notes | Example Table, Acceptance Tests |
Tagsno overlap | ChangeSystems thinkingCapability | Behavior-Driven DevelopmentRequirementsExamplesRefinement | ChangeDecisionStrategy | AgileRequirementsExamplesBehavior-Driven Development |



