View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Agile Specification by Example |  Systems Thinking Intervention Mapping |  Systems Thinking Evaporating Cloud |  Agile Example Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | 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. |
Complexitydifferent | Medium | High | Medium | Low |
Timedifferent | 60-90 min pro Feature | 1-5 Tage | 60-120 min | 30-60 min |
Participantsdifferent | 3-6 | 4-12 | 2-8 | 3-7 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Example Table, Acceptance Tests | Logic Model, Change Objectives, Intervention Components, Evaluation Plan | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Example Map, Acceptance Criteria, Open Questions |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | ChangeSystems thinkingCapability | Theory of ConstraintsAssumptionsSystems thinking | Behavior-Driven DevelopmentRequirementsExamplesRefinement |